DDraceNetwork - mapping

I really hope that we could get like a massive project involving us mappers trying to manually fix these static (not flexible) entity issues with a new entity set that can be implemented (smth like ddnet 2.0 entities) and map out the entities which need to be replaced with the new one. At least we could do 500 maps as a start and continue from there, till older maps (excluding ddmax) will be also converted into the ddnet 2.0 entity set (edited)

02:28

Good idea no? Way easier to implement, as in with a new entity tileset, we could implement flexible changes without harming the other maps in the process.

02:29

@heinrich5991 I kinda need an expert dev's opinion on this

I didn’t fully understand what you want to do. But doing some search and replace automatically in all ddnet maps should be relatively straightforward thanks to @Patigas map library

Replying to @Cellegen maybe chillerdragon could make a bot which does that tbh

02:36

@Cellegen: pinging Heinrich to ask for breaking backwards compatibility :D He will say no won’t do because old clients do not support it. You have to ping @Jupstar ✪ instead and uninstall ddnet and play his new game

maybe breaking backwards compatibility aint a bad thing

02:37

it just means moving forward from a worse version

xd

02:38

If we break compatibility the first thing we should do is remove 0.6 network code

most versions you guys release have greater compatibility than like... 0.5 vanilla

02:38

(0.5 vanilla was a jk)

chillerdragon

If we break compatibility the first thing we should do is remove 0.6 network code

I mean... ye?

02:39

vanilla is already ahead to 0.7 so

Yep ddnet stuck in the past

who has still 0.6 vanilla? justatest

Only ddnet

well its controversial on how devs want and not want this to change

But you are not getting what I’m saying

02:41

We don’t break compat unless Heinrich is afk for a year

If you say that first we need to settle down on the 0.7 problem before all the other ones I mentioned then ye. You are right (edited)

02:41

didnt realize that is also an issue

chillerdragon

We don’t break compat unless Heinrich is afk for a year

Is he the only one capable or the only one who decides?

I think he is the one with the strongest feelings about backwards compatibility

02:42

The rest of the people who decide do not care as much. But not sure.

so the latter

02:43

well so be it, it he says no to these, who am I to argue

02:43

but if he says yes and needs help with it, Im here to contribute

Yes that’s why I say go to @Jupstar ✪ (edited)

02:43

Pog

Replying to @Cellegen but if he says yes and needs help with it, Im here to contribute

jupstar big sleepy head rn troll

chillerdragon

If we break compatibility the first thing we should do is remove 0.6 network code

the first thing is to remake the whole protocol lmao

Why protocol is okay as it is. It’s just not compatible with teeworlds servers if it’s not 0.7

The way we are doing it is defs unhealthy But 0.7 is also not the future

chillerdragon

Why protocol is okay as it is. It’s just not compatible with teeworlds servers if it’s not 0.7

no since you can't say what protocol it is on connection proceeding/connless state

Yea having protocol version in the very first message sounds cool