The hang had a different cause than I reported. I had said the server read a quit command on stdin. The 1.30 experimental server raises Assertion failed ... Script is leaking! at shutdown and waits for an answer to (A)bort (R)etry (I)gnore on stdin. The vanilla BunkerBroadcastManager leak triggers it - quit only worked because its third letter is i.

https://github.com/bzed/dayz-dev-plugin/blob/dayz-1.30/compatibility/version-130.md - updated.

@lava76 thanks a lot, will update the skill!

For those who want to know what to look for, thats my summary so far:

https://github.com/bzed/dayz-dev-plugin/blob/dayz-1.30/compatibility/version-130.md

(and for the AI users, its part of a skill, mainly tested in linux, but working very well for me.

@lava76 maybe put that into CF so not everybody has to reimplement that?

So you are breaking most community servers? Seriously?

Who needs mods when you have a new map with bikes 🤣🤣🤣🤣🤡

Seriously, a massive amount of mods depend on CF and/or the broken function - and none can be tested. @l909 We need a fix now.

@l909 I do not think this is the same bug, -85 complains about including files, which sounds scary as you can run probably untrusted code.

Finding files to read a set of configs is a thing that is very useful. $ variables should keep working though.....