Spring RTS Engine

Shore to Shore has been completely nuked from the fileuniverse server... Reason being.

WHoever the heck made the original kept posting updates under the same map name.

DO I really have to explain why that causes all kinds of problems? I was willing to let it go until I noticed this... 2 more versions SUPPOSEDLY fixed showed up yesterday.

1 of them was completely fucked, the other game sync errors, and the other had smd issues.

FFS do not reupload that map and I will be nuking it on sight because it has caused TAS users untold amounts of trouble. As we speak I am remaking it. It will have for once a good texture, features and FFS METAL IN THE GODDAMN WATER!

I'm going to personally castrate the next person that makes a WATER MAP WITHOUT METAL IN THE WATER.

Gah, can anyone tell that I'm frustrated? lol

Anyway, shore to shore remake will be uploaded and available tonight.

who is remaking? :)

He is>.>


MAKE IT LOOK TROPICAL.


Or else!*shakes fist*

Kixxe wrote:He is>.>


MAKE IT LOOK TROPICAL.


Or else!*shakes fist*

WORD :D

I made the original map, but it broke with the new parser, and to fix it you just needed to fix one line in the smd. So, I am assuming that half the spring population was fixing that line and then uploading it.

Neuralize wrote:I made the original map, but it broke with the new parser, and to fix it you just needed to fix one line in the smd. So, I am assuming that half the spring population was fixing that line and then uploading it.

HEH NO...

the problem was that that you released new versions under the same map name causing sync errors all over the place.

Next time you decide the update a map... Change the name!

like this

mymap-v01.sdz/sd7

map versions are the way to go, to avoid confusion... map bashing is not..


well as you are on that ForboddingA, i reques 4 skulls to be fixed aswell, no need to remake it, just correct some line in the .. smd?..

later.

oh darnit, I'll get to it when I get a chance.

Ashpen is broken as well, and I'd love to see it fixed, since its a great small map.

and make it slight bigger than the original map

Actually, a working version of Ashpen is on FU, but unlike FA for example I prefer to keep the old filename so that the old version is automatically overwritten. The title for the map on FU does contain the version number and so does the description. Version 0.5 is the latest.
There is one elusive bug in it still though, but I've only encountered it in SWS so I don't know what to make out of it. Still, considering it still contains this bug I didn't think it was worthwhile to announce it.

On a random note though; FA, if he wanted to keep it true to the original map he couldn't place any metal in the water after all.

SecurE wrote:Actually, a working version of Ashpen is on FU, but unlike FA for example I prefer to keep the old filename so that the old version is automatically overwritten. The title for the map on FU does contain the version number and so does the description. Version 0.5 is the latest.
There is one elusive bug in it still though, but I've only encountered it in SWS so I don't know what to make out of it. Still, considering it still contains this bug I didn't think it was worthwhile to announce it.

On a random note though; FA, if he wanted to keep it true to the original map he couldn't place any metal in the water after all.

Ya and cause massive sync errors. Jesus, what a noob. PPl like you piss me off.

You pull this crap again and you're map will be auto deleted.

Forboding Angel wrote:

SecurE wrote:Actually, a working version of Ashpen is on FU, but unlike FA for example I prefer to keep the old filename so that the old version is automatically overwritten. The title for the map on FU does contain the version number and so does the description. Version 0.5 is the latest.
There is one elusive bug in it still though, but I've only encountered it in SWS so I don't know what to make out of it. Still, considering it still contains this bug I didn't think it was worthwhile to announce it.

On a random note though; FA, if he wanted to keep it true to the original map he couldn't place any metal in the water after all.

Ya and cause massive sync errors. Jesus, what a noob. PPl like you piss me off.

You pull this crap again and you're map will be auto deleted.

Arent the mapnames being read from the smf instead of the archive name?

Ah, yes, cause sync errors with a map that doesn't even run on the latest version of Spring, good luck with that. Granted, some people could obviously still have the old version that doesn't work, but I would imagine that the problem would become evident quickly. Especially as the one who got the old version shouldn't even manage to get as far as to start connecting to any host.
Good luck with that auto deleting though. Oh, where did I say I changed the archive name?

yes! and that's the problem. He uploads a new version with the same smf name but different archive name so no one has any idea what version is the latest and people that have the old version don't know there is a new version because tasclient doesn't know the difference.

aka we need the lobby to do a checksum on the map archive too

^ why? e: oh, now i read it, sry, and undestand the why, but, wont that take too much time?

its easier and less resource expensive to use the version number in the file itself.

this is true also for mods.

I uploaded S2S twice, once a long time ago when the new map format was first released and then later I released a revision when I deduced that units couldn't climb slopes correctly. Someone else was uploading the map with the fixed smf for the new parser, and they might have had the old version, and then maybe someone else uploaded a fixed smf from my second release.

Had I uploaded again, it would have been a new revision I was working on, however, I didn't have time to finish it, and now we have your remake which did everything I had planned.

FA, I wouldn't be so hard on SecurE and I, me and him made some of the first maps for the new format for Spring, I'm betting me and him both assumed that the lobby would do a map file checksum and declare the game unsynced if the players had different versions of the maps.

Forboding Angel wrote:yes! and that's the problem. He uploads a new version with the same smf name but different archive name so no one has any idea what version is the latest and people that have the old version don't know there is a new version because tasclient doesn't know the difference.

That sounds to me like a problem with TASClient and not the map makers. TASClient should not even ATTEMPT to load a map that has the same name but is different, do you have any idea what security impliccations this has?

There is no reason to have old versions of maps laying around. I do agree that the whole desyncing issue sucks, but that client should check for map consistancy BEFORE tha map starts.

Also:

Forboding Angel wrote:Ya and cause massive sync errors. Jesus, what a noob. PPl like you piss me off.

You pull this crap again and you're map will be auto deleted.

Quit being such a jerk to people. It's not that big of a deal.

Oh god I'm so sorry it was all me I admit it. I just couldnt resist uploading files with the same name over and over again.