The detathmatch goodies in single player mode move around if we make the same megawad multiple times without closing the ObHack GUI between making megawads.
Steps to reproduce
Enter the ObHack-engine-697 directory
Edit scripts/writer.lua to change if false to if true (enable debug mode)
Remove the file CONFIG.cfg
Open up ObHack (or ObHack.exe in Windows)
Generate a map. ObHack will report an error; this is to be expected (since we altered writer.lua)
The SHA-256 sum of MAP12.txt will be 24cee2c01ca49322cb18795c788374598ebe25a0b26b890211a356ed17ee6954
Generate a map again
Look at the SHA-256 sum of MAP12.txt
Be sure to restore writer.lua to its previous state. This can be verified with git status
Expected results
The SHA-256 sum of MAP12.txt should be 24cee2c01ca49322cb18795c788374598ebe25a0b26b890211a356ed17ee6954 again
Actual results
The SHA-256 sum of MAP12.txt is something different, such as 17300c2079cabc831eb097855cfa1c35c2f85d4d19ad9813a6fceb928eac9016
Description of problem
The detathmatch goodies in single player mode move around if we make the same megawad multiple times without closing the ObHack GUI between making megawads.
Steps to reproduce
ObHack-engine-697
directoryscripts/writer.lua
to changeif false
toif true
(enable debug mode)CONFIG.cfg
ObHack
(orObHack.exe
in Windows)writer.lua
)MAP12.txt
will be24cee2c01ca49322cb18795c788374598ebe25a0b26b890211a356ed17ee6954
writer.lua
to its previous state. This can be verified withgit status
Expected results
The SHA-256 sum of
MAP12.txt
should be24cee2c01ca49322cb18795c788374598ebe25a0b26b890211a356ed17ee6954
againActual results
The SHA-256 sum of
MAP12.txt
is something different, such as17300c2079cabc831eb097855cfa1c35c2f85d4d19ad9813a6fceb928eac9016