Player/Character creation via web [$35]

Player creation via the web admin works but it is not feasible to create a full Player-Character pairing via the admin at this point. This issue concerns the full pipeline of creating Player and Character in the admin and then log in and play normally under any MULTISESSION_MODE.

• Player cannot get permissions. Permissions are Tags with the db_tagtype = "permission", and there is currently no way to create new Tags to go with the Player permission. One can select an existing tag (which has to be pre-created in-game at the moment), but the Tag display does not currently show the different tag types so one could accidentally pick a non-permission Tag here if it happens to be named the same as a permission level. resolved in #1115
• Attributes should be fully modifiable from the admin. resolved in #1115
• Aliases are Tags with db_tagtype="alias", there should be a way to set this (nicks are not needed though). resolved in #1115
• The superuser flag sits in the “web only” section. This is the only setting that does matter in-game in the same way as on the web, so it should probably be described somehow in that header (this is just a documentation issue). -Fixed in develop
• For MULTISESSION_MODE=0,1, one should be able to tie a Character to the Player by setting the Object’s db_player foreignfield. In MULTISESSION_MODE=2, one might instead want to assign the character to the _playable_characters Attribute on the Player. A custom form is probably needed for this linking. -Added with button in develop
• Possibly there should be some sort of list of suggested Object cmdsets so one doesn’t need to remember and write the path every time. This could be a help text or if possible some selector based on settings.CMDSET_*. Maybe one could consider some sort of clickable buttons that fill in some standard presets …? Added with dynamic help entry in develop
• When setting a cmdset on a Character in the admin, the cmdset seems to be set to be visible outside the character. The result is that you get multi-command errors when executing commands in the same room as the new Character. Fixed a long time ago
• Tags-Permissions for Characters are needed in the same way as for Players. resolved in #1115
• There should probably be some help info or preset for how to set the puppet: lock to allow a Player to puppet a given Character, such as puppet:id(<player id>). Handled with button and info-text in develop
• There should probably be a way to connect a Player to a Character in the admin, for MULTISESSION_MODE=0,1 to not need to use @ic to connect. Fixed in develop.

<bountysource-plugin>

---

There is a $35 open bounty on this issue. Add to the bounty at Bountysource. </bountysource-plugin>

[Griatch]

Thanks! Closing now that the bounty is claimed. For backers that need to approve it, @strikaco should be getting the bounty of this one, for their contributions to it over a long time.

[j3b4]

I’m not 100% this belongs here rather than a new issue. But I discovered the following today:
On a server running MULTISESSION_MODE = 0 I was able to use the web admin to delete my only character associated with the account (which had the same name as the account) but the account persisted and I stayed logged in. I was then able to use the web admin to create a new character with a non-matching name. Not the same name as the account. Back in the online client I was able to use ‘ic newname’ and connect to the new character. So now I had non-matching account and character name in a MULTISESSION = 0 environment. This might not be what a server admin would want players to be able to do on such a server.