Came back to this project for some small updates and to more formally open-source it.
- Integrated the Mirror Package to enable PvP functionality.
- Created a ZenHub Board for this project to better organize issues and epics. To see it, just install the ZenHub browser extension, and you should see the "ZenHub" tab listed beside "Pull Requests".
- Code cleanup and asset folder reorganization. This will be an ongoing project, with issues going under this epic
This was a short project I worked on and off for about 4 months, and it simulates the Pokemon battling system for the 8th generation. The focus of the project was solely the battle system, so there is no overworld or exploration component. Furthermore, most of the present game data such as Pokemon, items, moves, abilities, etc. are placeholders used to test the wide range of mechanics. The underlying system is in place for users to add their own game data to the project.
 |
 |
 |
 |
- Single & Double Battles
- P v. P, P v. AI
- Mega Evolution, Z-Moves, Dynamax & Gigantamax
- Most Moves & Abilities
- Status (non-volatile & volatile), weather, terrain conditions
- Entry Hazards
- Some items
- More...
- Audio, will be captured by this epic
- Most graphics (Trainers, Moves, etc.), captured by this epic
- Animations
Make sure you select the scene 'BWBattleScene' in Assets/Scenes, and click the Play button at the top of the Editor.
The scene can also be played by building the project.
- Arrow Keys: Navigate battle menus
- Spacebar: Confirm selection
- X: Cancel selection
- Z: Trigger special command (Mega Evolution, Dynamax, or Z-Move)
- On the Scene Hierarchy, go to PBS -> Network Manager
- There should be an expandable Battle Settings attribute
- Required Players are the amount of human players needed to start a battle
- Total Players are the amount of players in the battle. The amount of AI Players = Total - Required
- Currently only tested with P v. P, and P v. AI
Game data entails Pokemon, types, moves, abilities, items, statuses, environmental conditions (weather, terrain), and each of these has its own class and associated database where their properties are meant to be stored. MOST GAME DATA ARE PLACEHOLDERS. They are not fully implemented and not meant to be used in a release. The databases are in-memory dictionaries for quick testing, but in the future these should be formal databases (SQL most likely).
All the game data classes are designed to be customizable and allow for easy plug-and-play of new features (moves, abilities, items, status conditions, weather, etc.). It is even possible to build new features using old ones as a base. For example, I was able to create the following features without much battle code editing:
- 'Heavy Rain' extends from 'Rain' (simply adding new effects on top of Rain)
- 'Toxic' extends from 'Poison' (1 additional damage stacking effect)
- 'Blaze' and 'Overgrow' differ by one property value (the type affected)
- 'Parental Bond' can have more hits, and scale damage differently
- ... many, many more
You can contribute by:
- Opening issues for missing features
- Working on open issues
- Reporting bugs
- Suggestions for improvement and optimization
- Any other way you can think of
Any small contribution helps! Here are some smaller issues I've noted that anyone can help out with.