@Faraday This is my initial, immediate reaction, so I have not really sat down and thoroughly thought this through.
tour
lets you create a (temporary) character flagged as a guest, with a hardcoded-Guest
— or equivalent, maybe(Guest)
? — tacked on to the name for communications purposes. The flag and moniker/suffix indicating a guest character would poof if that player applies and is approved.- Players “could” have the option to specify a name when touring (admin setting?) or use a predetermined one chosen from a list (also admin setting?). This is one point I haven’t thought all the way through, because of the potential abuse factors (such as harassing and/or impersonating players with similar names, even with the clear “GUEST” designation that would be appended).
- Should guest/temporary characters have their own database table? That would largely deal with the need to track them as far as data goes (e.g., preserving communications), but I did not dig into the database part of the Ares codebase to see how you handled characters in general, or if this would be an absurd refactor. It would be a much easier process to purge (all of) them when they’re in their own table, though, if the need arises. Name collisions would have to be a special check, though, not to preach to the choir.
On a less technical side:
- I’ve wondered why I’ve seen some games have their Guest characters get into the teens for numbering, because I had thought Guest chars were recycled on disconnect, so I always wondered how this was happening.
- I was never really a fan of the “anonymous” guest nomenclature, tbh. Thank the creepers and other memorable folks (hi Jill!) for that.
- Being able to preserve guest communications would be useful insofar as potential players is concerned. This is partly why I mention the possibility of conditionally allowing “real” character names for guest characters. Certainly, they should be able to rename (once?) during chargen when they want to be serious about playing. (The rename would be part of the actual application. This does put an onus on staff for name vetting.)