Guild icon
DDraceNetwork
Development / bugs
Report client & server bugs, especially but not limited to release candidates.
Between 2024-03-20 00:00:00Z and 2024-03-21 00:00:00Z
Avatar
Nakimurr 2024-03-20 08:47:49Z
after rebooting I couldn’t repeat it, it’s very strange, not only I spawned crookedly, but others too.
Castle_2024-03-20_15-35-01.demo
361.6 KB
Avatar
lomi 2024-03-20 19:14:58Z
Hi, After some testing, I found out that NoDefaultRule does nothing if the position 0 0 is tested with a NOTINDEX (whereas it works "as expected" with INDEX or if the position 0 0 is not tested). For example, test 1 and test 2 give exactly the same result (I tried with empty and full tiles, including some with index 84 and some without) but they should not. However, if the position 0 0 is not tested with NOTINDEX as in test 3 and test 4, NoDefaultRule gives the expected result (~ the result I expect ^^). test 3 fills with index 1, if 0 0 is a full tile and 0 1 (position above) is not index 84. "test 4" fills with index 1 if 0 1 is not index 84 independently of 0 0. [test 1] Index 1 Pos 0 0 NOTINDEX 84 [test 2] Index 1 NoDefaultRule Pos 0 0 NOTINDEX 84 [test 3] Index 1 Pos 0 1 NOTINDEX 84 [test 4] Index 1 NoDefaultRule Pos 0 1 NOTINDEX 84 Is this behavior expected or is it a bug ? Did I misunderstand something ?
Avatar
Ewan 2024-03-20 21:51:24Z
what am i looking at
Avatar
Kero 2024-03-20 23:10:28Z
Map Editor: When using Deep Unfreeze (Select Layer -> Game tiles -> Deep Unfreeze) it simply crashes. I dont know why. Im on 18.1 windows 10 I have some crash log dumps.
Avatar
Avatar
Ewan
what am i looking at
Ewan 2024-03-20 23:19:49Z
oh it's automapper
Avatar
Avatar
lomi
Hi, After some testing, I found out that NoDefaultRule does nothing if the position 0 0 is tested with a NOTINDEX (whereas it works "as expected" with INDEX or if the position 0 0 is not tested). For example, test 1 and test 2 give exactly the same result (I tried with empty and full tiles, including some with index 84 and some without) but they should not. However, if the position 0 0 is not tested with NOTINDEX as in test 3 and test 4, NoDefaultRule gives the expected result (~ the result I expect ^^). test 3 fills with index 1, if 0 0 is a full tile and 0 1 (position above) is not index 84. "test 4" fills with index 1 if 0 1 is not index 84 independently of 0 0. [test 1] Index 1 Pos 0 0 NOTINDEX 84 [test 2] Index 1 NoDefaultRule Pos 0 0 NOTINDEX 84 [test 3] Index 1 Pos 0 1 NOTINDEX 84 [test 4] Index 1 NoDefaultRule Pos 0 1 NOTINDEX 84 Is this behavior expected or is it a bug ? Did I misunderstand something ?
heinrich5991 2024-03-20 23:27:08Z
I suggest you create an issue on github: https://github.com/ddnet/ddnet/issues
Exported 6 message(s)