View Issue Details

IDProjectCategoryView StatusLast Update
0002615Spring engineGeneralpublic2011-08-18 13:13
Reporterdjmad Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionno change required 
Product Version0.82.7+git 
Summary0002615: FeatureRequest "March Tempo for Units"
DescriptionIs there a possibility to define a actual tempo for units

as i can see, all units are always moving with maximum tempo, so its not possible to do a widget which moves units synchronos

it should be a unit property to set speed factor from 0-100%, so u can move complete defence lines to the front without splitting them up

also support with repair units would work much better

would be interesting for most mods i think,
im trying now to build a widged which starts and stops units to maintain speed, with the wait-command units are not firing, and btw it uses hell of CPU and Networktraffic :-)
TagsNo tags attached.
Checked infolog.txt for Errors

Activities

Google_Frog

2011-08-18 07:13

reporter   ~0007256

CMD.SET_WANTED_MAX_SPEED

This widget uses it to control unit speed: http://code.google.com/p/zero-k/source/browse/trunk/mods/zk/LuaUI/Widgets/unit_cloaker_guard.lua

Imo CMD.SET_WANTED_MAX_SPEED is part of the engine that is implemented poorly in terms of an intuitive lua interface. It has caused me great annoyance in command queue reading and manipulation.

Basically this command appears in a command queue alongside movement commands. I can't quite remember how it works but you can easily deduce it for yourself. Make a test widget that prints out the command queue IDs and look for CMD.SET_WANTED_MAX_SPEED (iirc it has a value of 80). Then you will know how to interleave this command with move command.

djmad

2011-08-18 07:56

reporter   ~0007257

thx, must have overread this part @ the luadescription

close please

Issue History

Date Modified Username Field Change
2011-08-17 10:49 djmad New Issue
2011-08-18 07:13 Google_Frog Note Added: 0007256
2011-08-18 07:56 djmad Note Added: 0007257
2011-08-18 13:13 Kloot Status new => closed
2011-08-18 13:13 Kloot Resolution open => no change required