-
Notifications
You must be signed in to change notification settings - Fork 13
Battle ~ Test ~ Moves ~ Items ~ Equipment ~ Design Document
There have been a lot file changes and ways that battles have changed. We need to implement a couple more tests to allow for all of our code base to be tested.
We want to make sure critical damage occurs at the proper chances.
We would like to ensure magical damage is calculated correctly
We would like to ensure physical damage is calculated correctly
We would like to ensure critical damage is calculated correctly.
We would like to test to make sure a weapons stats are applied correctly
We would like to test to make sure a accessory stats are applied correctly
We would like to test to make sure a armor stats are applied correctly
We would like to test to make sure that different equipment sets are applied correctly
We would like to test offensive items to make sure they debut correctly.
Needs to be changed to test for battle equipment.
Needs to be changed to test for battle equipment.
Needs to be changed to test for battle equipment for both player and NPC
Need to test a physical damaging move is executed properly.
Need to test a magical damaging move is executed properly.
Need to test a single stat_changing move is executed properly.
Need to test a both stat_changing move is executed properly.
Need to test a damaging and stat_changing move is executed properly.
Need to test a single stat_changing move is executed properly.
Need to test a both stat_changing move is executed properly.
Need to test a damaging and stat_changing move is executed properly.
Need to test accuracy and how it is calculated.
None
Need to ensure that new stat changes calculated correctly.
Need to ensure that new stat changes calculated correctly.
Need to ensure that new stat changes calculated correctly.
Need to ensure that new stat changes calculated correctly.
None
All tests need to be updated to accommodate new fields
Needs to test the printing of the damage.
Needs to test the printing of stat changes.
Needs to test the printing of stat changes of applied to a user.
Needs to test the printing of stat changes of applied to a target.
Needs to test the printing of stat changes of applied to both combatants.
Needs to test print the use of items
The is a new function and how it prints needs to be tested.
This test needs to test for equipment
This test needs to test for equipment
Needs to be updated for new fields
Needs to be updated for new fields
-
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