Topics created by Melpomene

@faraday My Atlantis beeps all the livelong day. I think you just need to turn it on as it defaults to off.

And thank you! Beep beep!

@melpomene This is awesome. Plushelp if it's of any use:

& messages Messaging is vital to roleplay, whether through text, phone, or IM. Messages are sent whether or not the recipient is online. When they next log in, they will see an alert notifying them that they have messages in their queue. Syntax: msg <player>=<text> - Send a message to the specified player. msg/<type> <player>=<text> - Send <type> message, for example, phone. msg <text> - Send a message with the same settings as the last one. &msg-send-ra me=%%cw%%cR%%[RED ALERT%%]%%xn - Example of custom colorcoding. msg/off - Turn off messages, putting up to 50 into your queue. msg/on - Turns messages back on and displays message queue. msg/block <name>[=<reason>] - Openly block target from sending messages. msg/unblock <name> - Unblock a person who was blocked. msg/hide <name> - Secretly blocks target from messaging, queue disabled. msg/unhide <name> - Removes a secret/quiet block from the target. msg/view - Display any queued messages. msg/summary - View a summary of your message status. After a message is sent, the system remembers the last person (or group of people) you messaged, and the last type of message you sent. Messages display special behaviors when they start with :, ;, or |. :tests <-- Gallifrey tests ;'s test <-- Gallifrey's test |A test happens. <-- A test happens. Testing! <-- Gallifrey says, "Testing!" Custom colorcoding can be set with variables on your character object. Using the example under the syntax list, anyone who receives a message from you with the 'ra' switch (msg/ra <player>=<message>) will see a bright RED ALERT tag. Messages System by Melpomene@MUSoapbox.

While testing I noticed that the built-in switches don't seem to work. For example, MSG/VIEW seems to think I'm trying to send a custom messaging type rather than checking the message queue:

msg/view <ALERT> [VIEW] CodeWiz sends, "/view" Or msg/summary <ALERT> [SUMMARY] CodeWiz sends, "/summary"

Updated the +help sample to actually use MVC structure (sort of). Added proper help files for it (ha!). I would now consider the +help thing a full-fledged piece of code and no longer "basic". It's ready to be repurposed for whatever data storage needs to happen.

https://gist.github.com/ADHdev/0f16992826cac3bcd00266f33dbceb87#file-plushelp-txt

There have been some minor updates to Cheapass Clusters as I discovered it wasn't storing raw code, and fixed a few other bugs.

https://gist.github.com/ADHdev/66ccc9ac4a520da760045a456e3a301d#file-cheapassclusters-txt

Not sure anyone's using these, but if you are, you probably ought to update.

And for my next trick: anvils. ...or rather, a generic stat system. 😄 (Yes, so you non-WoDers can have a chargen that isn't locked to that system.) This will probably take some time, though. I'll start a new topic when ready.

@Melpomene
That's why I suggested @create'd objects. You, as staff, can wander around and nuke them, force them to go home (which puts them in peoples' inventory) and such thing as stopgap measures.

@Thenomain. Really. You need docs!

Yes; an interface will need to be made available for accessing the archives. (how it was tested without one I'm not sure, but?)

This can be web-based (please not php) or-- well, you could just do it inside the mush. This would be another set of commands to run queries to retrieve archived job info-- and likely do various types of searches.

I very strongly recommend using the @query interface for async db queries-- that way you can run them without hanging the game, which is handy for very large/complex queries. It also has the nice result of returning a row at a time with a @trigger-like interface.

So, I tried all that and it didn't do the trick. I ended up just putting up a @readcache cron job every 30 minutes. All you who follow in my footsteps: skip the troubleshooting and just use the cron. @Sponge is wise.

@Melpomene, I can't really extend it because I know about as much about code as a llama knows about pasteurization. But it's good that you're opening it up for other coders to expand upon. It's a good idea.