benjamin-allen / nuctex Goto Github PK

• Add a base item structure
• Allow items to be in a location
• Define some basic things items do

Add a system to allow items to have flags, which are properties that dictate their behavior in certain situations

As it stands, there is no RNG system for combat. Everything is predetermined by stats and is easy to predict and control.

Needs

• There needs to be an RNG capable of generating numbers between a range, preferably in an efficient manner. If given an upper end and a lower end of a range, the RNG should be able to return a number between those two.
• There needs to be an RNG capable of generating a number up to the one desired, if given a number.
• RNG functions should return integers

Wants

• Preferably, both RNG functions should have a theoretically even distribution. This is a minor goal after the main implementation is complete.

Currently the output is minimalistic and ugly to look at. That needs to be changed. At present, the array of ideas includes:

Frontend

• A prompt for the user that is both unobtrusive and graceful
• A print-out system of the player's stats, so that they can get vital information about their character at a glance
• Colored output, with a definite color-coding scheme to convey information

Backend

• The most important part of the backend changes will be including the ability for the printMessage function to split the string it's given apart at the 80-character mark, so that printMessage can be used in a way that is not redundant to simply calling printf

• Items need to be able to be stored on players and monsters
• Items need to be equippable

Need to find a way to re-index the inventory so that iterators have an easier time reading through it. With thorough enough re-indexing code, one could end an inventory with a null terminator, similar to a C-string.

To ease programming in the future, include guards should be used in the header files. This will cause much less time spent on solving the mental tree of headers.

Currently, the game has no actual command parser, just a large if/elseif statement running multiple string comparisons on the player input.

Needs

• A parser that can understand two-word phrases in a verb-noun combination, understanding statements such as "kill slime"
• The parser needs to be able to understand when a command is invalid and report that invalidity to the player

Wants

• Naturally, the faster the parser is, the better.

Exactly what it says up there. Probably has something to do with the variables used to flee.

For combat AI, as needed in #4, it would be beneficial to have an RNG function that is passed a decimal value that represents a percentage chance. Another function that works with integers in a similar would be useful.

This is one of the main requirements for going into alpha, and I'd like to have somewhat functional combat utilizing an RNG ( #2 ) and some amount of player monster interaction. Combat must also be initiated in the style of a classical MUD, utilizing a parser ( #3 )

Needs

• A parser
  • The ability to engage monsters in the room one is in
  • The inability to engage monsters not in the room one is in
• RNG
• Monster reaction
  • Player death

Before the program goes into alpha, a sweep should be made through the source files and functions should be documented for future reference.

• Have a generic error reporting system for printing error messages (becoming more and more important with the numerous if calls)
• Redirect error messages to a debug file