-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Approaching Goti removes already existing opponent goti, even at Safe Spots #37
Comments
It maybe fixed by us if it remains stale for many days, you can chose to take up the issue if you like 😁 |
i want to work on this. Please assign me and as I am new to this repo please guide me through |
Hello @0shreyajha0, you can look at the web/src directory, specially at App.js. (No need to see all code in repo, the website code is inside First try to replicate this issue (for eg. by setting initial positions of two gotis, then fix dice to return 4(etc) always), eg. Blue Goti is at some stop, and a Red Goti moves to that stop, see what happens. Then, for eg. if the code removes the Blue goti, then try to look what lines remove a goti, for eg. looking for functions that remove gotis from an array, for eg. splice function etc., but sometimes you may have to look an uncommented code. And please comment code that you add, so next person that sees understands. Take as much time as you want, try and experiment in free time : ), the issue is not that important else. (That said, please tell if and when should unassign if so) |
Thank you for this |
Sir, the header file game.hpp is not running in vs code can you pls guide |
@0shreyajha0 Thanks, you are still trying, the issue itself does not hold much importance elsewise : ). That file is not needed actually for the issue, and is part of the C++ code. But, just in case, If it still does not work, let me know, i will create a more detailed documentation for this, so anyone else also can see it 👍 |
@adi-g15 Hey bro! So do we intend to keep all gotis safe at those places? Or only the ones which belong to their respective starting points? |
In this case, originally there was a blue at the starting point in blue, then the Red goti moved a distance of 4 units, reaching the same spot, and the blue goti went back in locked positions.
Though safe spot logic works for other cases, this is a condition were it is unexpected behaviour, happened twice in the gameplay.
Expected Behaviour:
When the final position has a goti, THEN before attacking & removing, first check if it is one of the safe spots on the board, if it is, then just add this goti to list of gotis on the final box, if not then proceed to attack.
The text was updated successfully, but these errors were encountered: