Activity log for bug #1407367

Date Who What changed Old value New value Message
2015-01-04 00:48:29 mevitar bug added bug
2015-01-04 00:49:46 mevitar description The crush command (alt + click on infantry) doesn't work anymore. When issued the command, nothing happens. Units can still crush other units if they just move on them while going somewhere, but you can't issue the specific order to move on them anymore. This problem was introduced in 0.8 Ares. The alex08.14.242.999 build doesn't have this problem, while alex08.14.253.253 (and all further builds) has it. The crush command (alt + click on a unit/infantry) doesn't work anymore. When issued the command, nothing happens, while normally the unit would move to the target, and the target would even try to move away. Units can still crush other units/infantry if they just move on them while going somewhere, but you can't issue the specific order to move on them anymore. This problem was introduced in 0.8 Ares. The alex08.14.242.999 build doesn't have this problem, while alex08.14.253.253 (and all further builds) has it.
2015-01-04 00:50:02 mevitar description The crush command (alt + click on a unit/infantry) doesn't work anymore. When issued the command, nothing happens, while normally the unit would move to the target, and the target would even try to move away. Units can still crush other units/infantry if they just move on them while going somewhere, but you can't issue the specific order to move on them anymore. This problem was introduced in 0.8 Ares. The alex08.14.242.999 build doesn't have this problem, while alex08.14.253.253 (and all further builds) has it. The crush command (alt + click on a unit/infantry) doesn't work anymore. When issued the command, nothing happens, while normally the unit would move to the target, and the target would even try to move away. Units can still crush other units/infantry if they just move on them while going somewhere, but you can't issue the specific order to move on them anymore. This problem was introduced in 0.8 Ares. The alex08.14.242.999 build doesn't have this problem, while alex08.14.253.253 (and all further builds) does.
2015-01-04 02:49:07 AlexB ares: assignee AlexB (alexander-b)
2015-01-04 02:49:09 AlexB ares: milestone 0.9
2015-01-04 02:49:10 AlexB ares: importance Undecided Critical
2015-01-04 02:49:14 AlexB ares: status New Fix Committed
2015-01-13 13:16:27 mevitar ares: status Fix Committed Fix Released