-
Notifications
You must be signed in to change notification settings - Fork 12
Enhanced CLI ~ High Level Code Overview
z # CLI Documentation
The cli (command-line interface) is the way in which the player interacts with the chiventure program. By typing things into the command line the user is able to perform a multitude of actions inside of chiventure. At a high level the cli takes in a string that is inputted by the user, parses it using the cli parser, and then, depending on what the user has inputted, performs different actions.
The cli module consists of several parts
The shell
shell.c and shell.h
- The shell file contains mostly system internal functions that do things like print a list of supported commands, print a greeting when the game starts, prints a history of commands that have been used so far, or prints a message.
The parser
parser.c and parser.h
- The parser files work to parse the input from the user. The way this is currently implemented is by turning the users input into a linked list of 'tokens' and then passing this linked list along so that the user's inputs can be performed (if valid).
The operations
operations.c and operations.h
- The operations files contain all of the operations that can be used in chiventure, everything from picking up an item to loading a new wdl file.
The command list
cmdlist.c and cmdlist.h
- The cmdlist files serve the purpose of allowing the user to be able to list the commands that they have inputted during any game.
The commands
cmd.c and cmd.h
- The cmd files defines the command datatype, the lookup entry for a hastable, and many functions that realte to interacting with these datatypes.
As of the creation of this document, things that have been implemented by the cli team in 2021:
- The use of linked lists as the datatype that the parser uses so that the user can input multiple commands at once using the connecting word 'and'
- Suggestions for when the user incorrectly spells an input, previously the cli would just say that this feature was not supported but now, for example, if the user inputs 'tak' the cli will recommend that the user meant 'take'
- The load_wdl commmand has been fixed, previously this function was completely broken and would cause seg faults, but now the user can load wdl files and an error will be printed if the path is incorrect
- The history command was added, so now the user can see what commands they have previously typed
- The indentation on the cli would be off-center until the user typed something, now the indentation is correct
- The user can type 'items' and a list of items that are in the room a player currently is in will be printed
- The user can now type 'credits' to see credits of a list of users who have previously worked on chiventure
- The number of objects in a command is now validated
- The user can now type 'QUIT' in order to quit chiventure along with pressing CTRL+D
-
Action Management
-
Battles
- Design Document
- Text Based Combat in Other Games
- User Stories
- Wishlist
- Battle Planning 2022
- Battle User Stories Review 2022
- Structs in Other Modules Related to Battles 2022
- Stat Changes Design Document
- Run Function Design Document
- CLI Integration Design Document
- Move Changes Design Document
- Unstubbing Stubs Design Document
- Battle Items and Equipment Design Document
- Battle Item Stats
- Battles Demo Design Document
- Battles Testing Moves, Items, and Equipment Design Document
- Sound integration with battle (design document)
-
Custom Actions
-
Custom Scripts
-
DSL
-
CLI
-
Enhanced CLI
-
Game-State
-
Graphics
- Design Plan
- Design document for integrating split screen graphics with chiventure
- GDL (Graphical Description Language)
- Graphics Sandbox
- Design Document for NPC Graphics and Dialogue
- Feature Wishlist (Spring 2021)
- Installing and Building raylib on a VM
- LibSDL Research
- Module Interactions
- Working with Raylib and SSH
- raylib
- GDL
-
Linking the Libzip and Json C to chiventure on CSIL machines
-
Lua
-
NPC
- Dependencies: Player class, Open world, Battle
- Action Documentation
- Design Document for NPC Generation in Openworld
- Design and Planning
- Establishing Dependencies
- Implementation of Custom Scripts
- Independent Feature: NPC Movement Design Document
- Player Interaction Design and Planning
- Dialogue
- Design Document for NPC Dialogue and Action Implementation
- Loading NPCs from WDL Files
- NPC Battle Integration Design Document
- NPC Battle Integration Changes Design Document
-
Open World
- Autogeneration and Game State
- Deciding an integration approach
- Designing approach for static integration into chiventure
- Feature Wishlist
- Generation Module Design layout
- Potential connections to the rest of chiventure
- Single Room Generation Module Design
- Source Document
- User Stories
- World Generation Algorithm Plan
- Loading OpenWorld Attribute from WDL
-
Player Class
-
Player
-
Quests
-
Rooms
-
Skill Trees
- Avoiding soft locks in skill tree integration
- Components of Exemplary Skill Trees
- Design Document and Interface Guide
- Environment interactions based on skill characteristics
- Integrating complex skill (combined, random, sequential, etc.) implementation
- Integration of a Leveling System
- Potential Integration with existing WDL
- Research on game balancing in regards to skill trees
- Research on skill tree support in modern day game engines
- SkillTree Wiki Summary
- Skilltree "effect" implementation and roadmap
- Summary of md doc file for skilltrees
- Design ideas in connection to other features
- Summary of Skill Tree Integration 2022
- The Difficulty of the Reading the World
- Complex Skills Summary
-
Sound
-
Stats
-
WDL