chocolatemelt / fe-cli Goto Github PK

self-explanatory

quite a bit lost, not sure where (likely ncurses stuff)

note: still reachable isn't a problem (see http://invisible-island.net/ncurses/ncurses.faq.html#config_leaks)

see tests/ folder

https://github.com/philsquared/Catch/blob/master/docs/build-systems.md#automatic-test-registration

might be helpful for cmake stuff

We have some existing JSON example schemas, so we just need to implement the methods to read/write them.

Basically:

importObject(Object o) { return someJson; }
exportObject(Json j) { return someObject; }

Default to ~/.config/fe-cli/

Should initialize on startup and read from config file @ ~/.config/fe-cli/config for default save location to read/write

menu items need to actually -do- something!

ideally encrypted/decrypted but not necessary. store locally (perhaps ~/.fe?) and make sure it's easily handled after reading

fe-test and fe-cli compile source files twice, which is a bit much

currently floating in the top left hand side, put it below the splash logo
you can use the row integer for vertical positioning since it's already pointing at the bottom of the logo

Implement an easy class structure for the all classes in the game

not a whole lot of options really, but stuff like configuring controls and where to save files are a good start

Character can't handle feWeaponRank initializations

Might be a problem with feWeaponRank

Setup a utility class for all algorithms necessary in the game

• Battles
  • Hit Rate
  • Dodge Rate
  • Crit Rate
  • Damage
• Leveling up
  • Random level ups
• Weapon skills

I'm just a visitor for now, however, glancing over the code I notice several points of interest:

• Tabs vs Spaces. A very contested issue the world over. Basically, choose one and stick with it.
• It is good that there are multiple files for different parts, but make sure that most of the files have some sort of description at the top saying what they do/where they fit in. (either in the cpp or h).
• Perhaps include a file of to do action items or some record of what is being worked on currently and what is in the pipeline for later on. (Quite possibly just a list of projects for large ideas and issues for small things leading up to the projects).

saving should be handled as a JSON file and have a default path of ~/.fecli/

decide on JSON structure

currently only works when running the program from the repository root because it uses a relative path; possible to get absolute path?

should be a function of two characters. characters should have an "equipped" item already, so all you have to do is call some member functions and do some math

classes have skills attached to them which will complicate this but thats a good start