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

Read game state from files #6

Open
dcki opened this issue Jun 13, 2014 · 1 comment
Open

Read game state from files #6

dcki opened this issue Jun 13, 2014 · 1 comment

Comments

@dcki
Copy link
Owner

dcki commented Jun 13, 2014

  1. Every number that dictates size, speed, time interval, etc. of ships, stars, projectiles, timeouts, etc. should be read from configuration files. That way it's easier to play with the numbers and play test. This will also force fixing brittle parts of code, which is good for quality and reducing potential bugs.
  2. All data for levels or star systems should be read from configuration files.
@dcki
Copy link
Owner Author

dcki commented Jun 13, 2014

If the configuration files are written in a custom plaintext format, or maybe YAML or XML, then people will be able to modify the game even if they don't have the source code or even if they don't recompile.

But if the configuration files are written in Java, code won't need to be added to explicitly read and parse files.

Since this game is open source, it's probably fine to use Java configuration files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant