-
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
Protoss War Council rebalance checklist #152
Comments
Basically I managed to do the entire zealot line so far, supplicant was the last one I completed. |
small correction: it looks like the changes i made to supplicant were undone |
Creating a checklist for the war council rebalance sheet here: https://docs.google.com/spreadsheets/d/1hObgY0_T7O94AOJ6wVCElEex-sE6JKQmIMsQO2oshpA/edit
Some upgrades are already implemented as default tech in the
AP_Triggers_giveProtossDefaultTech()
action, I'll try and capture them here. @MadiMadsen would be nice if you could confirm what you implemented already, I see Zealot, Centurion, Sentinel, Void Ray, Phoenix, etc. I also notice some Supplicant and Slayer upgrades that seem unrelated. I am also unsure what the recommended testing configuration is, I'm hoping to shift things over to a client option soon.The text was updated successfully, but these errors were encountered: