Skip to content
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

Coop conflict: ScienceVessel and TechReactor on C #31

Open
ZeroRin opened this issue Nov 16, 2018 · 6 comments
Open

Coop conflict: ScienceVessel and TechReactor on C #31

ZeroRin opened this issue Nov 16, 2018 · 6 comments
Labels
blizz:( regression after SC2 patch releases bug

Comments

@ZeroRin
Copy link

ZeroRin commented Nov 16, 2018

In Swann's starport both are set on C
This should not be a conflict as ScienceVessel can only be built after TechReactor, but when playing, I cannot press C to build TechReactor in Starport

@bobo38
Copy link
Owner

bobo38 commented Nov 16, 2018

thanks for the report

@bobo38 bobo38 added bug blizz:( regression after SC2 patch releases labels Nov 16, 2018
@bobo38
Copy link
Owner

bobo38 commented Nov 17, 2018

would you have a suggestion where to move the ScienceVessel? probably you fixed it in your local copy…
(I have some reactor/techlab/liftoff/land big update for TheCore Lite v2.4 that may interact with this bug)

@ZeroRin
Copy link
Author

ZeroRin commented Nov 17, 2018

seems that the nearest key which does not conflict with others will be Y, but I guess it's ok to bind it to Space since Swann does not have Raven anyway. Also Raven and ScienceVessel are subtitution to each other in WoL campaign. so I believe Space is a good option

@bobo38
Copy link
Owner

bobo38 commented Nov 17, 2018

I do remember that there is a Science Vessel+Raven conflict that poped out recently… prior to that Science Vessel was same as Raven

@bobo38
Copy link
Owner

bobo38 commented Nov 17, 2018

yep it was bug #12

@bobo38
Copy link
Owner

bobo38 commented Nov 17, 2018

it's still valid bug as per GUI setting… modifying terran unit production keys is super painful due to all the campaign, it will be fixed for TheCore Lite v2.4 (i've already found a solution to use 4 and E for reactor and techlab, so that science vessel on C won't break)
If you play coop only and you are not playing campaign you can map it on 4 temporarily

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blizz:( regression after SC2 patch releases bug
Projects
None yet
Development

No branches or pull requests

2 participants