0.75b1

[Tired]

[9:36:14 AM] Server says your Spring version (0.75b1) is outdated (server only supports 0.74b3+svn3950)

Cool.

So, this is what I get after unistalling Spring, deleting my old folder save for maps and mods, and trying to log on. The update fails, of course. Funny thing is that before this I'd installed the update patch only, and could log into the lobby just fine, although I'd get disconnected every 30 minutes or so for no apparent reason. I decided that a clean install was necessary after trying to play 5 games and having all crash on the host end (different hosts) after at most 24 minutes. This isn't counting the restarts for people who had custom (useful) widgets, of course, and thusly couldn't load to begin with. Still don't know why we get half of the lobby updates that we do.

So, first impressions of the update would include:

Likes

The new Search tab for UF, although I'd probably like it more if it were located somewhere else.

Dislikes

Flashing chat cursors for text ingame - those're really annoying.
Being told that full installs aren't current when by version number they are.
The frequent crashes that always occur right after updates.

Uncertain

Lineage Mode. Presuming that it works, if an ally gives you a builder, are the buildings built then tagged as his or yours for the purpose of kabooms?

Anyone else care to add to these?

[lurker]

[9:36:14 AM] Server says your Spring version (0.75b1) is outdated (server only supports 0.74b3+svn3950)

ctrl+shift+F6 Ignore server version incompatability.

I'd get disconnected every 30 minutes or so for no apparent reason.

Yeah, me too, and usually can't reconnect or access the website for a couple minutes, all while my connnection to osrts stays stable.

I decided that a clean install was necessary after trying to play 5 games and having all crash on the host end (different hosts) after at most 24 minutes.

Ouch. Probably the buffer bug. Maybe telling people to not give large orders until 75b2 in a few days?

[MelTraX]

That wrong version stuff happens if your client can't connect to the normal official server.. As it moves down the list, it gets to the osrts.info test server which is limited to a specific SVN version.. Overwriting that version incompatability won't help you because you would be pretty alone on that server and even if there are prople, you'd be the only one with the wrong version..

So just wait until you can connect to the real server..

[lurker]

Hmm, apparently Tired is already connected to the main server. meh. still might be usefull to others.

Edit: nvm the rest, I guess I remembered something wrong

[Tired]

I'm just persistent - it can boot me 30 times in a row and I'll switch windows to try again periodically while web browsing. =P

Possible that that problem's been fixed. For the rest, timeouts every 20 minutes ftw.

*Make that every 10. I love it when updates designed to fix certain issues end up causing them.

[Peet]

[9:36:14 AM] Server says your Spring version (0.75b1) is outdated (server only supports 0.74b3+svn3950)

You're connecting to the wrong server.

[manored]

As far as I know, lineage mode is something like this: Each commander gets a lineage number from start that doesnt changes with giving and everthing he builds/ressurects/captures gets that lineage number too, and those guys pass their lineage number down too. Then a commander dies everthing with a equal lineage number dies too. Im not sure about what happens then 2 commanders have the same lineage number tough, but I THINK that the second commander gains a diferent lineage number but keeps linked to the first commander, so if the second commander dies only stuff built by him dies but if the first one dies then everthing dies.

[Tired]

That's the gist of how Lineage works, yes, but my question specifically involved structures built by shared builders. Whose Lineage number do they get?

[det]

If an ally gives you a builder in Lineage mode, anything it builds will die when his commander dies. You can only change the lineage of a unit by capturing it. So if you want to share constructor units, it must be captured first. There is nothing special about commander units in general. If they are resurrected or gained with .give, they will behave like any other unit. The only special thing is that that the commander you are given at the start is the parent for his lineage. It is that one specific unit only which will kill everything if it dies. The rules are surprisingly simple.

See http://spring.clan-sy.com/wiki/Lineage

[Zydox]

Dislikes

Flashing chat cursors for text ingame - those're really annoying.

Is there a way to revert this to the previous state?
Or is it hardcoded somewhere?

[manored]

That means if the son commander builds a base and then dies (outside the base :) ) his base is not destroyed?

[det]

If by son, you mean, commnader that was ressurected/captured (although capturing a commander is almost impossible to happen in a real game), then yes. Only your original commander counts as special.

[1v0ry_k1ng]

WHERES MA ENDGAME STATS?

[Tired]

For end game stats, everyone on the winning team has to Ctrl D. Once no one's left, the stats'll pop up.

Other known issues are that Rapiers and Blades (which no one else's probably noticed, as no one builds the worthless things) try to Guard whatever they're told to attack, and there are frequent ingame error message crashes (at least involving XTA).