Recruitment Queue Bug

[antisocialmunky]

Anyone else run into the queue not acting right if you build more than the recruitment slots? If you order up more units than your city can build at one time, the next turn, any unrecruited units that were left over from the previous turn are built at a rate of 1 per turn.

[lugh]

Can't say that I have, then again there seems to be as many unique bugs as there are players!

Not exactly satisfactory, but does it rectify the problem to clear the queue and restack it?

[a-e]

How many recruitment slots did the settlement have?

[Fisherking]

Anyone else run into the queue not acting right if you build more than the recruitment slots? If you order up more units than your city can build at one time, the next turn, any unrecruited units that were left over from the previous turn are built at a rate of 1 per turn.

Well, sorry but over building the queue is asking for trouble.

It is hard to call something a bug when you are exceeding the intended limits.

If you are not to tac your car’s engine past 40,000 RPM but you do and blow a piston at 60,000 RPM are you going to blame the manufacturer?

[Susanna]

Well, sorry but over building the queue is asking for trouble.

It is hard to call something a bug when you are exceeding the intended limits.

If you are not to tac your car’s engine past 40,000 RPM but you do and blow a piston at 60,000 RPM are you going to blame the manufacturer?

I don't think he is doing anything un-intended.
Queuing units to build them in a row has been a feature even in Rome:TW. You queue up four units, the towns builds them after 1,2,3 and 4 turns respectively. Nothing special or fancy.

Susanna/Calapine

Disclaimer: English isn't my first language, so sorry if you meant something else than I thought you do.

[Beskar]

antisocialmunky, that isn't the case at all.

Out of the 10 slots, lets say the city can do it at a rate of 3 per turn. That would be 4 turns for all 10 units, the first 3 producing 3.

So unless you are confusing a town where it works at a rate of 1 per turn and not understanding why it is doing it, that is the default if they can only do one per turn.

[Fisherking]

I don't think he is doing anything un-intended.
Queuing units to build them in a row has been a feature even in Rome:TW. You queue up four units, the towns builds them after 1,2,3 and 4 turns respectively. Nothing special or fancy.

Susanna/Calapine

Disclaimer: English isn't my first language, so sorry if you meant something else than I thought you do.

No!

This is what he said:

Anyone else run into the queue not acting right if you build more than the recruitment slots?

So if you recrute 15 units but only have 10 slots, what he is saying is the other five units build at one per turn.

[lugh]

If you order up more units than your city can build at one time, the next turn, any unrecruited units that were left over from the previous turn are built at a rate of 1 per turn.

Yes, but right after that he elaborates. He means that when he "orders" 5 units, and the city can make three per turn, the first three get made, but the last two are reduced to one per turn etc.

[Beskar]

I definitely not had that.

[antisocialmunky]

I had it happen once again and it seems clearing the queue + ordering the units again/ordering random units and clearing them fixes it. I've only seen it happen when I was building 8, 4 inch mortars but that's it.

[a-e]

It could be population related?

[lugh]

Hmm, should be popping up for other units than 8 inch mortars then I think? At least it's a rectifiable bug...