changing yardmaps (possibly backward compatibility breaking)
Moderator: Moderators
Re: changing yardmaps (possibly backward compatibility breaking)
+1 for new tag (ground)blockingMap (or the like).
more obvious then yardmap (to me).
that would even make sense to me if you would not change letters.
more obvious then yardmap (to me).
that would even make sense to me if you would not change letters.
Re: changing yardmaps (possibly backward compatibility breaking)
I like the term yardmap.
o = a circle, it sympolises a closed surface.
c = a semicircle, a semi-open surface.
What could be more logical?
o = a circle, it sympolises a closed surface.
c = a semicircle, a semi-open surface.
What could be more logical?
Re: changing yardmaps (possibly backward compatibility breaking)
how about making the yardmaps not chars, but strings?
freefreefreefree
blocfreeblocfree
blocyardblocfree
freefreefreefree
blocfreeblocfree
blocyardblocfree
Re: changing yardmaps (possibly backward compatibility breaking)
you can find meaning in any letters...
o can either be open or occupied or obstacle.
None is really better or easier to remember than the other, so switching meanings has no advantage. If you have to look them up now, you will have to do so in future.
yardmap = {
[1][1] = {requireGeo = false, blockMovement = false, blockBuilding=true, openClose=true},
[1][2] = {requireGeo = false, blockMovement = true, blockBuilding=true, openClose=false},
...
}

o can either be open or occupied or obstacle.
None is really better or easier to remember than the other, so switching meanings has no advantage. If you have to look them up now, you will have to do so in future.
or tabes!how about making the yardmaps not chars, but strings?
yardmap = {
[1][1] = {requireGeo = false, blockMovement = false, blockBuilding=true, openClose=true},
[1][2] = {requireGeo = false, blockMovement = true, blockBuilding=true, openClose=false},
...
}

Re: changing yardmaps (possibly backward compatibility breaking)
I cannot wait until I leave these yards behind.
- Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
Re: changing yardmaps (possibly backward compatibility breaking)
Hey guys, it's not often that the engine devs ask our opinions on stuff. The least we could do is not turn the thread into a sarcastic circus.
Once again, jk, I say go for it (your original proposed changes). Changing yardmaps into something that makes sense is excellent.
Once again, jk, I say go for it (your original proposed changes). Changing yardmaps into something that makes sense is excellent.
Re: changing yardmaps (possibly backward compatibility breaking)
They make sense and there is zero reason for changing the existing chars!
- Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
Re: changing yardmaps (possibly backward compatibility breaking)
At any rate the 'intuitiveness' of the codes is entirely subjective - why break backwards compatibility (and existing documentation) for that?FLOZi wrote:o - obstacle
y - yard
c - construction
- Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
Re: changing yardmaps (possibly backward compatibility breaking)
You didn't explain anything. Please explain how the current makes any sense at all.
With zero descriptions. You see a yardmap tag. You understand that yardmaps are blocking maps. You know nothing of what the letters mean.
yardmap = "
ooocccooo
ooocccooo
ooocccooo
ooocccooo
ooocccooo
ooocccooo
ooocccooo
ooocccooo
ooocccooo
",
What does that mean?
Now, compare with the new:
yardmap = "
xxxoooxxx
xxxoooxxx
xxxoooxxx
xxxoooxxx
xxxoooxxx
xxxoooxxx
xxxoooxxx
xxxoooxxx
xxxoooxxx
",
Considering that this is a factory shaped like || ||, Which one makes more sense?
With zero descriptions. You see a yardmap tag. You understand that yardmaps are blocking maps. You know nothing of what the letters mean.
yardmap = "
ooocccooo
ooocccooo
ooocccooo
ooocccooo
ooocccooo
ooocccooo
ooocccooo
ooocccooo
ooocccooo
",
What does that mean?
Now, compare with the new:
yardmap = "
xxxoooxxx
xxxoooxxx
xxxoooxxx
xxxoooxxx
xxxoooxxx
xxxoooxxx
xxxoooxxx
xxxoooxxx
xxxoooxxx
",
Considering that this is a factory shaped like || ||, Which one makes more sense?
Re: changing yardmaps (possibly backward compatibility breaking)
Except as jk pointed out, newlines are read as o (This naturally should be fixed, all whitespace chars should be ignored) so your examples are somewhat moot. And personally I see basically zero difference - especially as you could already replace your o with x but maintain c:
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
xxxcccxxx
Re: changing yardmaps (possibly backward compatibility breaking)
well if its all about viusals.. why not go nuts completely:
BB+++BB
BB___BB
BB___BB
BB___BB
BB+++BB
PS: Im pretty sure the devs by now have a moddev contact procedure.
Equipment: StunGun, heavy BodyArmor, Taser, Raw Meat, tranquillizer (mostly for you) Those of you who enter...
BB+++BB
BB___BB
BB___BB
BB___BB
BB+++BB
PS: Im pretty sure the devs by now have a moddev contact procedure.
Equipment: StunGun, heavy BodyArmor, Taser, Raw Meat, tranquillizer (mostly for you) Those of you who enter...

-
- Moderator
- Posts: 2464
- Joined: 12 Oct 2007, 09:24
Re: changing yardmaps (possibly backward compatibility breaking)
I see no reason to change the characters because the proposed system is not many times better than the current one. While we're at it why not change the meaning of fire arc to something that makes more sense?
Re: changing yardmaps (possibly backward compatibility breaking)
While we are at it, could we have a Excellsheet that is autotransfered into unitdefs?
Also.. why does spring not have a pron folder? It doesent have to contain anything, just makes me feel uneasy..
Also.. why does spring not have a pron folder? It doesent have to contain anything, just makes me feel uneasy..
Re: changing yardmaps (possibly backward compatibility breaking)
space already is ignored, so you can format a bit for easier reading:FLOZi wrote:all whitespace chars should be ignored
yardMap = "oooo occo occo occo occo yyyy yyyy yyyy",
http://springrts.com/wiki/Units-UnitDef ... _PlacementWith zero descriptions.
Re: changing yardmaps (possibly backward compatibility breaking)
I know - but tabs and newlines should be ignored also.
Re: changing yardmaps (possibly backward compatibility breaking)
They are not letters. You see a yardmap code, if you raytrace it you see what's blocking and what's not. Simple.Forboding Angel wrote:With zero descriptions. You see a yardmap tag. You understand that yardmaps are blocking maps. You know nothing of what the letters mean.
Re: changing yardmaps (possibly backward compatibility breaking)
Sure they are not letters, but then you assume they correspondent to all pen & paper games!Jools wrote:They are not letters. You see a yardmap code, if you raytrace it you see what's blocking and what's not. Simple.Forboding Angel wrote:With zero descriptions. You see a yardmap tag. You understand that yardmaps are blocking maps. You know nothing of what the letters mean.
Re: changing yardmaps (possibly backward compatibility breaking)
▓▓▓▓▓▓
▓▒▒▒▒▓
▓▒▒▒▒▓
▓▒▒▒▒▓
▓▓░░▓▓
No extended Ascii code i presume?
▓▒▒▒▒▓
▓▒▒▒▒▓
▓▒▒▒▒▓
▓▓░░▓▓
No extended Ascii code i presume?