- Joined
- Mar 27, 2012
- Messages
- 3,232
Over time I've found ObjectMerger has problems with several fields, mainly bitflags. It interprets them as strings or sometimes even something I have no idea what it is.
Example:
This line treats both the 1 with and without " as strings. It would be logical for there to be some way of overriding that stupidity, since "1" is 49 as a string and 1 as a bitflag. I'd use the ASCII code for 1, except that it's not even printable!
Similar bugs exist with other fields too. For instance, death type likes to produce gibberish whatever you input there from objectmerger.
Is there any possibility of a patch?
Example:
//! external ObjectMerger w3a ACvs A0Z1 Poi4 1 1 Poi4 2 "1"
This line treats both the 1 with and without " as strings. It would be logical for there to be some way of overriding that stupidity, since "1" is 49 as a string and 1 as a bitflag. I'd use the ASCII code for 1, except that it's not even printable!
Similar bugs exist with other fields too. For instance, death type likes to produce gibberish whatever you input there from objectmerger.
Is there any possibility of a patch?