Spring RTS Engine

Changelog 7.14 --> 7.15 wrote:- Fixed reclaim bug for negative/zero resource features.
- Start resources and storage now belong to the commander not the team.
- Fixed coop mode not spawning units for non coop players.
- Moved start resources into mod options.

Small patch for 'urgent' issues with the new Spring release, another release will come soon with more content!

Download Balanced Annihilation V7.15



*Hotfix for the commander icon not showing up, download and extract to your spring folder: http://consternationstation.com/custom_icons_fix.zip

Nice quick fix, glad to know you're around again at this crucial time

runs smoothly, good work :)

Yup, just played my first game of BA without it crashing or me d/cing in 3 days.

dunno if someone mentioned it but players receive error spam every time spec try to fps unit

I got some visual shit report.
In spec mode it sometimes shows the projection of LOS models. It has been confirmed by other players.

Screens will explain:
def, llt, mex
llt

Some mexs re not rotating although they are properly placed and switched to on...

Wombat wrote:dunno if someone mentioned it but players receive error spam every time spec try to fps unit

Part of the engine now i'm afraid!

Super sized start pos markers here :)

Yuri wrote:I got some visual shit report.
In spec mode it sometimes shows the projection of LOS models. It has been confirmed by other players.

Screens will explain:
def, llt, mex
llt

Some mexs re not rotating although they are properly placed and switched to on...

Can't recreate this, are you using a custom ghost site widget or the one bundled with BA? and also if you got the replay of this that might help if it also occurs there.

Yeah, if you use the ghost building widget, when a worker builds its last building in a queue, the ghost will remain, even though the building is finished, until that builder is given a new command. Maybe not what you're talking about, but just throwing that out there.

Thanks for the Custom Icons fix <3

Question for the masses:
It's been ages and i'm not 100% sure I remember - since i've fixed the com wrecks flying across the map in a test build now what happens when 1 com dguns another is that one's blast destroys the others wreck so only 1 wreck is left - is this what used to happen before the flying change or did both survive in this situation?

TheFatController wrote:Question for the masses:
It's been ages and i'm not 100% sure I remember - since i've fixed the com wrecks flying across the map in a test build now what happens when 1 com dguns another is that one's blast destroys the others wreck so only 1 wreck is left - is this what used to happen before the flying change or did both survive in this situation?

I don't remember how it used to be, but imo com-blast shouldn't destroy another wreck - but dgun probably should prevent a wreck from being made.

So if one com dies in range of another, there's 2 wrecks, but if one dguns the other, there's only 1 wreck.

bugz, very often when someone start at front, his start pos moves back after start

The D-Gunned com would usually only leave 1250 wreckage. It wouldn't be the usual com wreck shape either, instead being flat.

Bomber exploit needs serious fixing. It didn't used to be very bad bug now everyone is learning how to do it and it's getting out of hand.

Hobo Joe wrote:Bomber exploit needs serious fixing. It didn't used to be very bad bug now everyone is learning how to do it and it's getting out of hand.

What is this exploit? You mean bomber micro?

JohannesH wrote:

Hobo Joe wrote:Bomber exploit needs serious fixing. It didn't used to be very bad bug now everyone is learning how to do it and it's getting out of hand.

What is this exploit? You mean bomber micro?

Attack a spot, press wait just as bombs are released, wait for reload, press wait again to release 2nd load.

=Bomber micro

Nothing wrong with it

I'm just clarifying, never having seen this bug... it means a bomber can release more than one load, and is effectively breaking the "one bomb per flyby" behaviour that is rather rigidly enforced for aircraft?

Because if so, this phrase below:

JohannesH wrote:=Bomber micro

Nothing wrong with it

is spectacularly, amazingly, stunningly wrong.