Latest Commit Breaks Paired Techs

[Imarok]

3 hours ago, wowgetoffyourcellphone said:

Sorry, I do not read every single Trac commit with tooth and comb.

No Problem ;D

[wowgetoffyourcellphone]

 

Imarok's file here does fixes this!

selection_panels.js

However, it does not include the fix from 18788 

http://trac.wildfiregames.com/changeset/18788 probably only fixes the cost of upgrades for multiple selections, which is a good fix for sure.

 

Regarding costs of multiple selections. Take a look if you will to the buildtime cost of units in multiple selected barracks (for instance). It assumes they are a single batch and calculate the buildtime accordingly (when they are actually separate batches with their own buildtimes). 

Edited September 29, 2016 by wowgetoffyourcellphone

[fatherbushido]

@wowgetoffyourcellphone:

Indeed, r18787 only fixes the cost of multiselection, the other fix is not yet commited.

Thanks for recalling the cost time bug of mutliple selections (you have yet pointed out that).

[wowgetoffyourcellphone]

1 minute ago, fatherbushido said:

Thanks for recalling the cost time bug of mutliple selections (you have yet pointed out that).

I am not sure what the program team wants to get done by Sunday, so I only mention it because the current trend seem to be to fix multiple selection bugs and related things.

[wowgetoffyourcellphone]

You will hate me, but I think this bugged the upgrade feature. If tower have 10 limit, then upgrade the tower to stone (or whatever), it counts it twice toward limit. Probably not intended behavior.

 

http://trac.wildfiregames.com/changeset/18791

[fatherbushido]

thanks for noticing, we will change that.

It sould be fixed by r18796.

[Imarok]

On 29.9.2016 at 8:23 AM, fatherbushido said:

Thanks for recalling the cost time bug of mutliple selections (you have yet pointed out that).

Is there already a ticket for this bug?

[elexis]

Apparently not

[Imarok]

3 hours ago, elexis said:

Apparently not

Now there is one: #4264