sinipelto
New update of the general init.c made scripts not working anymore? Please help
https://steamcommunity.com/sharedfiles/filedetails/?id=3154795336 i am trying to get this to work for my groups server (deathmatch server) here are a few screenshots to show the config and location etc
that mod got retired since it didnt work anymore, quoting the dev here in theyr discord server: "ok so fallout wont even try to boot, puls up script errors accross the board, safezone appears to be booting but looks like the godmode refernce is now invalid that safezone script has never broken before and has been in use for over 6 years 🙌 it was a gift to me from one of dayz's oldest modders, it should NEVER break unless you alter the players core script regarding there ability to die or not ..... serverside safezone is RETIRED i simply cant fix it Somethings altering the actual launch script , they changed that in the last update, its why our safezone doesn't work Also renaming any pbo now causes a fail to read error , all pbos must be depacked and repacked at there core in order for it to read" if somebody knows a fix please help me out :D
Hello, I do not understand why you are asking this here, there is no link between the safezone mod and https://github.com/sinipelto/dayz-scripts project.
Did you go asking on the mod discord ?
Hum, i've tested the safezone.c script on my namalsk 1.27 server and be able to make it work by fixing some things thanks to server crash logs.
I create a repo to share the fixed version here: https://github.com/jcaspes/dayz-safezone-script
I add a message on offical discord https://steamcommunity.com/linkfilter/?u=http%3A%2F%2Fdiscord.gg%2FXfA7hRXF7S
Hum, i've tested the safezone.c script on my namalsk 1.27 server and be able to make it work by fixing some things thanks to server crash logs.
I create a repo to share the fixed version here: jcaspes/dayz-safezone-script
oh nice thanks will check it out soonish
and i asked here since u seemed to know what ur doing xD
Thank you a lot @jcaspes for assisting solving this issue. I proceed to close this as it appears to be mainly not related to this repo currently.
