Spring RTS Engine

Oh, well that's something that the maker(s) need to add/fix then.

local widgetPosX = vsx-200
local widgetPosY = 0

Those are the defaults for when there is no config file. So for you you want to raise widgetPosY. (0, 0) is bottom left. (vsx, vsy) is upper right. I assume 200 is the width of panel.

Caydr wrote:Hi, I'm trying to integrate this into AA but I would like it to automatically dock to the right side of the screen, offset from the bottom of the screen by a given number of pixels.

Control + F11
Drag around with left click

Lets user put it where they want, better than any automatic placing.

One thing: I assume the callin "UnitCommand" is also called when a teammate gives a command? The "Hot"-unit stuff wont work if thats not true. Maybe someone who knows for sure about it can tell. Yes, it will. It gets called for every command that is successfully issued. Includin...

If you changed it to face to where your mouse is relative to the building, that would be perfect, and faster to get to the direction you want (Only 1 move)

Basically the FARK just feels lame, especially for a t2 unit. It might be a lot more fun and balanced if it had some advantage, like much cheaper in cost than the Freaker and stealth ability. Or keep your t1 lab and use rezers.. Arm and core are not meant to have identical units. Just like arm veh ...

You can deselect units via Lua, by doing a GetSelection() type call, removing items from the result, then calling a SetSelection() type call with the new table. Hm, can't find any references to those functions in the wiki and not in the spring sources. Calling them fails too. You actually used them...

Great job, but did u think about lock selected stuff? i mean that when u select units others teammates cant use it. coop mod is really interesting. Thanks! I tried to implement but it seems to be impossible to deselect units by Lua or to make it impossible for the player to select certain units, at...

I hate you.

Um, a bit hard to do really.

Really you should just order them how you want, and theyll stay that way

v2.2 released, fixes a very annoying bug with v2.1 when using a single unit.

Note that the single-unit path thing works with fight/attack/patrol/etc, handy to use if you have a single transport carrying a few units, as it also works with unload (So you have a line of evenly spaced unloads)

Spring.GetUnitLastAttacker(unitID) -> attackerID

Call this on :UnitDamaged, and there you go, the missing piece.

Note that it will only return the attackers ID if it can see the attacker (Los or radar), so you should nil check it.

One Widget could easily destroy that gameplay, by simply highlighting all enemy units using gl.Unit calls, making them clearly visible through the game's foliage that would normally make them hard to observe. That's the thing about this issue- when you look outside BA, it's easier to see why it's a...

Are there widgets which give a large advantage to players with them, over players that don't have them? No. Will there be any widgets like that in the immediate future? No. (Widgets have been around for how long now?) Can a widget do anything a skilled player couldn't? No. Because of the above, woul...

Spring.GetTeamUnitStats
( number teamID ) ->
nil | number killed,
number died,
number capturedBy,
number capturedFrom,
number received,
number sent

Version 2.1 released. Get from SpringDownloader or the widget database Implemented TFCs idea. With a single unit selected it will follow the line starting immediately. Works with shift, but cannot be inserted. Waypoints are spaced a minimum distance apart (Configurable at top of file). Shouldn't be ...

For solo units may I suggest adding some functionality like this since clicking and dragging with 1 unit currently doesn't have a function in spring: <image> I've already hacked this into my copy but it was a quick job and not very neat so i'll keep it to myself for now, however it is a useful skir...

Two minor bugs: core t2 radar kbot is still in vehicle moveclass. crashers can only be built on perfectly flat terrain (by freaker) +1 to both. The same need-perfectly-flat-ground applies to jethros built by consuls as well, while other units such as cans/raiders/pyros etc don't have any issues.

I see all this talk about banning/restricting widgets, when there are really no major examples out there of widgets that give a significant advantage and are not readily available.

Arm dragonflies (T2 trans) jam radar, generally works to jam both them and passengers, but when turning it can fail, due to radius being so small. Should be buffed so it actually works.