DDraceNetwork - developer

ddnet-maps

[ddnet-maps:master] 1 new commit

8790f5c A TeeInvader, A Glitchhold - ddnet-maps

def-

[ddnet-web:master] 1 new commit

7409483 Remove chl - def-

So I have this old fork of ddnet but when i started developing it i started with a new git history. Any ideas how to get ddnet git history in there? I thought about taking ddnet repo resetting it to my fork starting points commit then copy in all content from the initial commit. commit. And then cherry pick all my history on top. Any better ideas? Or any idea on how to find out which ddnet commit a given modified ddnet src has

@deen are there any map scripts you would like to have right now? with my python bindings I would happily write some :)

fstd, maybe pstd should be using longer random strings for the urls

chillerdragon: i'd first find the commit your fork is based on, then just pull the master branch from the commit and put your changes ontop

13:49

and instead of cherry-picking you can also rebase interactive and put all at once, but there are probably many ways anyway

13:51

git merge --allow-unrelated-histories no idea if that triggers merge conflicts xd

Patiga

@deen are there any map scripts you would like to have right now? with my python bindings I would happily write some :)

Hm, can't really think of anything. For fixing stuff in map testing you mean? Could you automatically detect common map problems?

true that reminds me that I still had stuff I wanted to do in that area

Could even ask testers for some things they are looking for, not sure how much is automatable

I found https://github.com/heinrich5991/libtw2/issues/18, but it don't know yet how complex that output format is

def-

[ddnet-web:master] 1 new commit

959da57 Knuski retired from mods - def-

trml

[ddnet/ddnet] Pull request opened: #4176 Entity switch prediction

Adds the prediction for pickups and projectiles (based on #4108) For blinking entities (deactivated by switch) I also used the extended info to make the blinking effect happen client-side. So instead of the server omitting the projectile/pickup from the snapshot every N ticks (which prevented some things like explosive bullets from being predicted correctly), the server will keep sending the item and let the client decide how to show it. Added doors as well, and changed how they are sen...

@Patiga check the binary in libtw2, it outputs msgpack. it's quite easy

and any idea on how i find the commit my fork is based on? (@Deleted User)

Jupstar ✪

chillerdragon: i'd first find the commit your fork is based on, then just pull the master branch from the commit and put your changes ontop

look at last change dates i guess

does that really work? :D

why not, i mean you atleast have the version dont u?

u mean like with ls?

so cant be that many commits

21:07

to check

21:08

mhh i'd look into your github repo

?

or rebase against the first commit from that version and slowly add more commits until the diff is small

image.png

21:09

im not sure if those dates are from me creating the project or from actual ddnet edits

21:09

wait wat

yeah look in github, or where your fork is from

sep jan

21:10

is that this year?

its today bro

21:10

lmao

yea wtf

21:10

so the dates do not help

is it on github?

https://github.com/DDNetPP/DDNetPP

GitHub - DDNetPP/DDNetPP: Based on DDraceNetwork by deen & contribu...

Based on DDraceNetwork by deen & contributors (www.ddnet.tw) which is based on the great game teeworlds (www.teeworlds.com). - GitHub - DDNetPP/DDNetPP: Based on DDraceNetwork by deen &...

there you have the dates

21:11

just go to the first commit

https://github.com/DDNetPP/DDNetPP/blob/master/storage.cfg

DDNetPP/storage.cfg at master · DDNetPP/DDNetPP

Based on DDraceNetwork by deen & contributors (www.ddnet.tw) which is based on the great game teeworlds (www.teeworlds.com). - DDNetPP/storage.cfg at master · DDNetPP/DDNetPP