Player's drone sync + labor division #145
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
branch update
…nebula into building-drones-sync
|
I will resolve conflicts + two bug fixes are needed... please do not merge yet |
|
It should be ready for the merge now :) all issues solved. |
hubastard
reviewed
Apr 15, 2021
hubastard
approved these changes
Apr 16, 2021
|
ready for merge |
Mushroom
suggested changes
Apr 16, 2021
Mushroom
approved these changes
Apr 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the implementation of #126
I am basically sending 3 events using transpilers:
The labor division (each drone will build something else) is achieved by leveraging the original approach of marking which prebuild is under build from the drone. In case of collision (client and host will send drone at the same time), a random number is generated as a priority for the drone order.
For example:
178361.2781.In this case, the Client lost and his drone has to go back to mecha. In the case of more players, the higher number will always win.
In the GIF below, I have build 8 buildings and each player has only 3 drones. That is why the first 6 buildings are built quickly and the last two later.