-
Notifications
You must be signed in to change notification settings - Fork 39
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
Comments
thanks for the report |
would you have a suggestion where to move the ScienceVessel? probably you fixed it in your local copy… |
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 |
I do remember that there is a Science Vessel+Raven conflict that poped out recently… prior to that Science Vessel was same as Raven |
yep it was bug #12 |
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) |
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
The text was updated successfully, but these errors were encountered: