This is a large release containing some major restructuring. And support for puppets!
Features
Puppets
A puppet is a character, similar to all the others, with the exception that it may be controlled by more than just the owner.
Identifying a puppet
Puppets are identified by a blue badge. Hovering over the badge will show the puppeteer within (parenthesis):
Hovering a message in the chat log also shows the puppeteer:
Using a puppet
To use a puppet, you must register it first. To register a puppet, go to the same room and type:
register puppet Tom Greyback
This will send a request to the owner of the puppet. Once that request is accepted, the puppet will be available in the Character Select page, under a new Puppets section:
If another puppeteer is using the puppet, it is is possible to request to take over control:
Once they grant the request, or if they do not respond within 5 minutes, you get a toaster notification allowing you to take over control:
If they deny the request, you will have to wait at least 5 minutes before making a new request to the same puppeteer.
Puppet restrictions
When controlled by the owner, a puppet can do anything a normal character can (except registering other puppets). But while controlled by a puppeteer, it cannot do things like:
- Send mail
- Create/edit/delete rooms or exits
- Create/edit/delete character profiles
- Register teleport nodes
- etc.
Note
Any mail sent to a puppet character will be received by the puppet owner, not the puppeteer.
Creating a puppet
Turning a character into a puppet is currently restricted to admins and builders only.
Mail Accipiter Nisus in game if you wish to create a new puppet.
This information, a bit watered down, is available in the help:
help puppets
Improvements
Command renaming
Some commands has been renamed:
| Old command | New command | Comment |
|---|---|---|
set status |
status |
Old command is still available as an alias |
add teleport |
register teleport |
Fixes
Unicode name breaks console
The command console couldn’t parse names containing unicode character (eg. “Pålle Häst”). This bug is now fixed.
Error when renaming to similar name
When a character name was changed to a similar name with different markers (e.g. “Pålle” → “Palle”), we got an error that the name already existed. This bug is now fixed.
In Room list inconsistency
Occasionally, when following/leading someone, the In Room list would get inconsistent, not showing the follower after arriving, or not removing the follower when leaving. This bug is now fixed.
Link in description shows $2$3
When using a formatted link in a room or character description, the text “$2$3” also showed up. This was fixed silently prior to this release.
Dash in name breaks client
When using a character name containing dash (eg. “Puddle-of-sky”), the client stopped responding receiving the first chat log message. This was fixed silently prior to this release.