Pros: Almost totally eliminates map merge conflicts
Cons: Increases the size of the mapfiles by probably somewhere around 20% (by my estimate, based on assumptions that may or may not be correct) and the number of lines in the mapfiles by some absolutely absurd degree
vote yes
What effects would larger mapfiles have?
Nothing, really.
The extra size is almost entirely whitespace, so it shouldn't have much effect on loading time
Can't say for sure because... well, BYOND always has surprises
Nah it's not exclusively whitespace, it seperates the map chunks a ton more.
Well yeah
I did say _almost_ entirely
Also, if we do do this, our map files will be astronomically long
/tg/'s are pretty fucking long and they only have one Z-level per file
It wouldn't really be a problem under any circumstances I can think of, though
@PJB3005, so less merge conflicts and less pain in the ass?
2016-04-14 22:18 GMT+02:00 PJB3005 [email protected]:
Nah it's not exclusively whitespace, it seperates the map chunks a ton
more.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/d3athrow/vgstation13/issues/9447#issuecomment-210131719
If we go as far as /tg/ did, zero merge conflicts unless two people edit the same individual tile (or the map cleaner rearranges some tiles like it sometimes just decides to do), and even then possibly not
Abso
hecking
lutely
We don't have merge conflicts unless people edit the same individual tile.
Well at least we wouldn't if people would read the directions in install.txt.
be aware that at least for us it made asteroid unuseable in the byond map editor since it just broke on large map files, so you had to convert to dmm, edit, then back to tgm
crap
Wait, is the issue with large files or long files?
I'm not actually sure, I think it was the length of the file
http://www.byond.com/forum/?post=2044362 bug report
If it's length, we probably shouldn't even bother with this idea until that gets fixed, considering we store all our Z-levels on one file, so all of our mapfiles would be quite a lot longer than any of yours
Yeah I was pretty crushed to read that because man, this sounds great.
And Lummox will never respond.
you can still use it, it just requires an extra conversion step from tgm -> dmm for the actual server compilation/running.
again, it may not be size exactly, my memory is hazy as to the actual reason and asteroid is not iirc our largest map, so I reckon at least give it a whirl locally
edit:plus I was wrong in my original description - it dies in the compilation step, not the editor step.
Even worse.
Last I checked, we handle lag pretty well. We can take the extra 20%.
Yes, if compiling works then the extra 20% or so size isn't a big deal
I guess I'll test it out when I get the chance and see if we have the same issue they do
No, we shouldn't
Most helpful comment
If it's length, we probably shouldn't even bother with this idea until that gets fixed, considering we store all our Z-levels on one file, so all of our mapfiles would be quite a lot longer than any of yours