- Status Closed
- Percent Complete
- Task Type Feature Request
- Category
- Assigned To No-one
- Operating System
- Severity Low
- Priority
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#1910 - In-Game Access to Name Change Logs
It would be useful for GMs to know if a name has been changed in the past as well as if a name was deemed safe to use despite being borderline. This prevents another GM from coming and overruling a fellow team member’s decision. Ideally this wouldn’t happen but sometimes players can be sneaky and try to have a GM undo what another GM did, and some other times we just can’t get a hold of each other.
The History command could work in two ways:
- By entering /changename <target|player|me> history (or /changename <target|player|me> list), in which case all names ever used would pop up in a list. For example:
/changename Dajoji history
Dajoji
Dajoji Noob
Dajoji Chillpill
and
- If /changename is used on a player whose name was changed previously, a warning message would appear. For example:
/namechange Dajoji no Ijojad no
This player’s name has been changed before by <GM Name>. Do you still wish to change the name? Yes/No.
Likewise, the Approved Name command would flag a borderline name that was deemed appropriate so that if a GM wants to change it they get a similar message as the one above, except that there wouldn’t be any chance to change the name. For example:
/nameapprove Dajoji
‘Dajoji’ has been set as an approved name by <GM>
/changename Dajoji no Ijojad no
Name change denied. The name ‘Dajoji’ was approved by <GM>
A command to disallow approved names would be necessary just in case. It could be available for GM3’s or GM4’s.
With these commands there we would give GMs access to the information they need to police the game without having to check or update GM websites (the approved names page is rather out of date and keeping an eye on it and adding content to it is impractical).
The syntax and mechanics of these commands may need some polishing but that’s the overall idea: to have in-game access to name change information.
| ID | Project | Summary | Priority | Severity | Assigned To | Progress | |
|---|---|---|---|---|---|---|---|
| 1985 | PlaneShift | FS#1985 - List of all GM feature requests [or dev lvl requests] | Low | Aresilek Besolez |
"Likewise, the Approved Name command would flag a borderline name that was deemed appropriate so that if a GM wants to change it they get a similar message as the one above, except that there wouldn't be any chance to change the name."
I don't agree with this. There might be a situation for which a namechange is needed for whatever reason in future. Such a hart coded deadlock is a misconception.
The general approach is good and a needed improvement of the current situation.
For the list command I would prefer to have the syntax as
/changename_list [target|name]
The warnings for approved/previously changed names when attempting to change the name are good.
For approval I would say the syntax should be
/approve_name [target|name]
like /ban_name.
Making new.
there is a big issue with this: the db doesn't contain such a thing and obtaining that data would require a like query which would block the server and kick everyone out (the gm command table is one of the biggest ones maybe surpassed only by item instances, although I'm not 100% positive on this).
it would need at least to make a table just to store name changes
For messages like "player name was approved by GM <xyz>", all you need is a new name_approved_by field in the player table.
A history of name changes would indeed require a new table.
Maybe a more general log of GM actions would be in order. Together with GM notes, possibly chat log (in case the GM instructed the player to, say, /petition for a better name within two weeks or so, so the /petition taker can review what exactly the instructions were), maybe TODO notes that can be made to pop up after a given time (to track player compliance).
This could make the field for the original name in the player database obsolete, too
name changes aren't stored in the db elvors