Ex: Default range for Kaiser Blades is 25 pixels, but DatEdit changes this to 16 (displayed as 1 when editing) when saving the DAT file.
I discovered this while writing a custom compiler/decompiler for DAT files
None.
DatEdit bug with weapons.dat
I just noticed that DatEdit coerces weapon ranges to multiples of 16.
Ex: Default range for Kaiser Blades is 25 pixels, but DatEdit changes this to 16 (displayed as 1 when editing) when saving the DAT file.
I discovered this while writing a custom compiler/decompiler for DAT files
Ex: Default range for Kaiser Blades is 25 pixels, but DatEdit changes this to 16 (displayed as 1 when editing) when saving the DAT file.
I discovered this while writing a custom compiler/decompiler for DAT files
Options
Pages: 1
Back to forum
Please log in to reply to this topic or to report it.
Members in this topic: None.
[2026-9-23. : 5:21 pm]
NudeRaider -- Oh_ManOh_Man shouted: NudeRaider yeh thts straight up cheating
the mutas yes, the wraiths probably not. Have you even watched the video? 
[2026-9-23. : 12:56 pm]
Oh_Man -- NudeRaiderNudeRaider shouted: Oh_Man Artosis hasn't caught on how devastating the perfect focus fire is. With the mutas he was like "the Mutas always seem to have less hp than against a human". But he didn't notice that the flock he had selected always just had one muta that was hurt. Same with the wraiths here. He's talking about how valks+wraith is gonna destroy Pluto's valks, then 5s later he's dumbfounded the human player's air is just gone and he never figured out why. And for some reason didn't even think to go back and look at the battle.
yeh thts straight up cheating[2026-9-23. : 12:24 pm]
Oh_Man -- arty's done another vid. he's also announced he's going to organise showmatches with pro, with NO maphacks, so we can see its actual capabilities
Members Online: 
O)FaRTy1billion[MM]
O)FaRTy1billion[MM]