Praxisprojekt Real Time MSD
Table of Contents
Architecture
Events
Changed Event
RobotsRevealedEvent: Reveals all robots on the planet to the player.
- contains the robotRevealed data of all robots on the planet
- is sent when a robot spawns or moves
- is only sent to the player of the robot who triggered the event
New Event
ActivityDetectedEvent: Informs players with robots on a planet when activity was executed by another robot.
- contains the open data (robotRevealed) of a single robot (for more information check out the Asyncapi)
- is sent after following robot actions:
move,fight,regenerate,upgrade,restoration - is sent to every player that has a robot standing on the planet where the activity happened. For
movethat means players from both the source and target planet.
Action Duration
In order to keep a balanced game experience we introduce action times. Those times determine how long it takes until the action is completed.
| Action | Time |
|---|---|
| Fighting | 3 Sek |
| Mining | 3 Sek |
| Movement | 3 Sek |
| Regenerate | 3 Sek |
| Upgrade | 3 Sek |
Timings are currently only temporary and are subject to change in order to improve the game balance.
Robot Locking
A robot can only execute 1 command at a time. This is insured by the robot command locker. It uses a local Redis server with a distributed lock pattern to save (lock) the IDs of robots that are currently performing an action. When the action duration is over, the robotID is released (unlock) again. In case of errors the robotIDs are automatically released after a certain time to avoid deadlocks.
Robot Upgrades
New Upgrades
- Movement Speed: reduces travel time between planets
- Regeneration Speed: reduces regeneration time
- Mining Efficiency: replaces the old mining speed upgrade
- Attack Speed: reduces attack time
Upgrade Changes
- Mining Speed: reduces mining time
Upgrade Values
| Upgrade | Effect | Level 0 | Level 1 | Level 2 | Level 3 | Level 4 | Level 5 |
|---|---|---|---|---|---|---|---|
| Attack Speed | Percentage of action time | 100 % | 80 % | 65 % | 50 % | 35 % | 20 % |
| Mining Speed | Percentage of action time | 100 % | 80 % | 65 % | 50 % | 35 % | 20 % |
| Movement Speed | Percentage of action time | 100 % | 80 % | 65 % | 50 % | 35 % | 20 % |
| Regeneration Speed | Percentage of action time | 100 % | 80 % | 65 % | 50 % | 35 % | 20 % |
| Mining Efficiency | Mining Amount | 2 | 5 | 10 | 15 | 20 | 40 |
Note: While the effect improvement per level of the speed upgrades is on paper not as high as the existing upgrades, it allows for more flexibility and better reaction time.
MSD Dashboard
The controlpanel and the map with the sidebar are fully functional. The map is updated every 0.5 seconds. The statistics are not working with the Real Time MSD.
MONTE and Skeletons
Player MONTE and the Java Skeleton have been modified to be compatible with the Real Time MSD.
TODO
The following things still need implementation or some changes:
- PriceChangedEvent (needs trading economics)
- Change other skeletons to work in the realtime msd
- Tests are outdated
- Add the new capabilities in msd-dashboard-backend
- Websockets in dashboard
- Kubernetes
How to use the Local-Dev-Environment of the Real Time MSD
Clone the local_dev_env Repository
Clone the DevOps-Team/local-dev-environment Gitlab repository
to your local machine and switch to branch PP-RealTime-MSD-Robin.
# HTTP
git clone https://gitlab.com/the-microservice-dungeon/devops-team/local-dev-environment.git
# SSH
git@gitlab.com:the-microservice-dungeon/devops-team/local-dev-environment.git
# Switch Branch (if branch does not exist locally yet)
git checkout -b PP-RealTime-MSD-Robin origin/PP-RealTime-MSD-Robin
Next Steps
Follow the README of the local-dev-environement repository (Branch: PP-RealTime-MSD-Robin).