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

only one command turret? #327

Closed
spikebike opened this issue Apr 16, 2019 · 3 comments

Comments

@spikebike
Copy link
Contributor

commented Apr 16, 2019

I git cloned git@github.com:Warzone2100/warzone2100.git a week ago and have been playing though. So far everything seems improved. One weird this is I was playing gamma-2 and had to hide my units from the nuke explosion by hiding in the canyon. One of the units that I hid was a command turret.

Now in gamma-3 my units were "lost", which I expected. But if I try to build a new command turret it says there's a limit on command units. Is this expected? A bug? I tried search on google and searching the github issues without finding anything.

I'm did a git pull today and it didn't change anything, I still can't build a command turret.

@KJeff01

This comment has been minimized.

Copy link
Contributor

commented Apr 16, 2019

Did you build a Command Relay? Some people said it was useless (it really was) so I made it mandatory to own one to research the command turret(s) and produce commanders.

@spikebike

This comment has been minimized.

Copy link
Contributor Author

commented Apr 18, 2019

Ah, perfect. I wasn't aware of the change, and verified that building a command relay fixed it.

One suggestion would be to change the "Max Command unit reached" error to say "Command Unit requires a command relay" or similar.

Forgon2100 added a commit to Forgon2100/warzone2100 that referenced this issue Apr 18, 2019
Change console messages for commander limits
Commander units cannot be produced
* without a Command Relay Center
* when owning no less than 10 commanders

More precise console messages distinguish between these causes.

Refs ticket:1661
Fixes Warzone2100#327
Fixes Warzone2100#329

Co-authored-by: spikebike <spikebike@users.noreply.github.com>
Forgon2100 added a commit to Forgon2100/warzone2100 that referenced this issue Apr 18, 2019
Fix production limit console message throttling
The first console message informing users about manufacturing limits,
familiar from its ending "Production Halted", was shown 40 seconds late
(the amount of MAX_UNIT_MESSAGE_PAUSE in human-readable time).

Refs ticket:4446
Refs Warzone2100#327
Fixes Warzone2100#329
@Forgon2100

This comment has been minimized.

Copy link
Contributor

commented Apr 18, 2019

Ah, perfect. I wasn't aware of the change, and verified that building a command relay fixed it.

One suggestion would be to change the "Max Command unit reached" error to say "Command Unit requires a command relay" or similar.

I have implemented this in #329.

Forgon2100 added a commit to Forgon2100/warzone2100 that referenced this issue Apr 18, 2019
Fix production limit console message throttling
The first console message informing users about manufacturing limits,
familiar from its ending "Production Halted", was shown 40 seconds late
(the amount of MAX_UNIT_MESSAGE_PAUSE in human-readable time).

Refs ticket:4446
Refs Warzone2100#327
Fixes Warzone2100#329
Forgon2100 added a commit to Forgon2100/warzone2100 that referenced this issue Apr 18, 2019
Fix production limit console message throttling
The first console message informing users about manufacturing limits,
familiar from its ending "Production Halted", was shown 40 seconds late
(the amount of MAX_UNIT_MESSAGE_PAUSE in human-readable time).

Refs ticket:4446
Refs Warzone2100#327
Fixes Warzone2100#329

@KJeff01 KJeff01 closed this in c165d8c Apr 25, 2019

KJeff01 added a commit that referenced this issue Apr 25, 2019
Fix production limit console message throttling
The first console message informing users about manufacturing limits,
familiar from its ending "Production Halted", was shown 40 seconds late
(the amount of MAX_UNIT_MESSAGE_PAUSE in human-readable time).

Refs ticket:4446
Refs #327
Fixes #329
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.