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.
[09:16 am]
NimoStar -- ever wanted to play melee in installation tileset? Now you can https://staredit.net/topic/18929/[06:02 pm]
Zoan -- of course it isn't full understanding. You could ask "is the mechanism by which this counterexample blows up the ONLY mechanism possible for an initial configuration to blow up?"[05:47 pm]
Zoan -- HeinermannHeinermann shouted: it also didn't solve that problem but hey as long as the investors are pleased
Constructing a counterexample is answering the question: "Is Navier Stokes well posed?" in the negative[05:43 pm]
Heinermann -- it also didn't solve that problem but hey as long as the investors are pleased[05:39 pm]
NudeRaider -- I have no idea tbh. All I know no human was ever able to solve it, but there's at least a few that beat portal 
Members Online: RIVE
RIVE