matthewjwhite/crystal-skull

:skull: Highly-configurable, telnet-compatible, text-based RPG

crystal-skull's Issues

Fix up CI

Acceptance Criteria

• Uses alpine as the base image.
• Passes.

Add unit tests

This project desperately needs some unit tests, especially given the additional complexity added by navigation.

Implement initial user stats

What?

A user stat in this case is strength, for example.

These stats will be used to calculate things like damage against monsters.

To Close

• Basic stats implemented.
• Can be extended to incorporate additional stats at a later point.
• Passing Pylint.
  • duplicate-code ignore removed.

Consider mongoengine

MongoEngine is neat little ORM for Python, w/ Mongo.

See the description in #14 for more context, could help to clean up the linkage b/w DB/YAML field names and Python variable names.

To Close

• Determine whether it's worth integrating into this project.

Implement initial exploration system

What?

Exploration in this case refers to the navigation of land masses in the overall world,

A way to represent these land masses (cities, towns, dungeons, etc.) is required.

The goal here is to implement (at least) the initial exploration design/map system.

To Close

• As lightweight as possible.
• Highly-configurable.
• Easy to link together individual maps/regions.
• Easy to enhance at a later point.
• Passing Pylint.

Implement initial battle system

What?

#5 covers battle from a very high-level and undeveloped standpoint.

Battling should be further fleshed out to incorporate user statistics (see #7).

Blockers

This will likely need #7 before it can be started.

To Close

• Initial battle loop is created using user statistics to determine damage.
• Passing Pylint.

General enhancements

This is a dumping ground for general enhancement ideas.

Implement initial game loop

What?

The game loop will drive the basic flow of the game.

At the moment, this game does not contain a loop of any sort. Once authenticated, the connection is killed.

Acceptance Criteria

• Contains at least the following stages:
  • Battle
  • Exploration
• Passing Pylint.

Add YAML validation

As the configuration grows, some sort of validation is needed to ensure that all required fields are present before starting the game. Careful attention to the configuration can't always be depended on. Right now, there is a lack of validation to ensure all required fields are present - a YAML schema would solve this problem.

https://github.com/23andMe/Yamale/ seems like a really neat project for this purpose. I'd prefer to avoid updating both the schema and associated config. loader (example) every time a new attribute is added to a configuration object, though.