Fix unit placement for a different team in map editor #28
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.
Closes #27
The root cause of this issue was the
Array.slice()
operation below:So when
vectors
is of length 1 (i.e., no mirroring / single player placement), the remainder operation (%
) below always produces an index 0 (anything is divisible by 1, so n % 1 = 0 for any n):By removing the
slice()
operation above and keepingplayers
as[1,2,3,4,5,6,7]
all the time, multiple-player selection logic is much simpler as well.For example,
vectors.length === 2
andcurrentPlayerIndex === 3
, player 4 and player 5 will be selected.vectors.length === 4
andcurrentPlayerIndex === 5
, player 6, player7, player 1, player2 will be selected.Single player placement
Screen.Recording.2024-05-22.at.10.35.49.PM.mov
Multiple player (4) placement
Screen.Recording.2024-05-22.at.10.38.15.PM.mov