Blizzard / Blizzard/s2client-api
"Select all larvae" game setting screws up calls over API
Open
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 280
- PR merge metrics
- No merged PRs in 30d
Description
My co-developer found the following issue:
If you have the "select all larvae" gameplay setting enabled in SC2, then sending commands to a specific larva using a direct Unit pointer/ID can still cause another larva to receive the command instead.
This breaks trying to keep track of the build cycle and such. I believe the gameplay setting shouldn't affect API commands.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.