Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with determining whether a player is new for the purposes of character generation #24

Open
jnharton opened this issue Jul 31, 2013 · 3 comments
Assignees
Labels

Comments

@jnharton
Copy link
Owner

The current system uses the text "NEW" in the status space to figure this out. Turns out this is really pointless, since chargen (like all editors) sets the status to EDT to indicate that the player is editing something. This occurs right before the check that expects to "NEW" and will otherwise deny use of chargen. So, it will never work, an alternate mechanism will be required.

@ghost ghost assigned jnharton Jul 31, 2013
@jnharton
Copy link
Owner Author

Note to self: I will probably have to either create some field on a player that is persisted that indicates this, determine it by some other persisted state/measure or overhaul chargen to use a different system. The latter should be a last resort as using the same system potentially avoids some code duplication.

@jnharton
Copy link
Owner Author

jnharton commented Sep 3, 2013

Added a boolean variable 'isNew' to help distinguish new players from existing players primarily for the purposes of only allowing character generation once. This is probably a stopgap measure and a few things will need to be tweaked to ensure that existing characters get this toggled false.

--- 9/15/2013

If I set only newly created players isNew value to 'true' and all else to 'false' and don't save any characters who haven't done chargen that might work.

@jnharton
Copy link
Owner Author

current status

As noted above, newly created players have 'isNew' set to TRUE and players loaded from the database have 'isNew' set to false. At the moment they are all saved, which needs to be changed (and warnings added).

@jnharton jnharton added the review label Mar 4, 2021
@jnharton jnharton added this to the Clean Up Current Issues milestone Mar 4, 2021
@jnharton jnharton removed the review label May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant