figured that class CraftBolt does not exist anymore, but its still in the GitHub... rest still applies though

@l909 that is a shame. It is demotivating to have little to no feedback on reports or suggestions. My brain needs a little feedback to evaluate if reports or suggestions are worth my time that it takes to make them. But i am not blaming you.
But please, forward the new information that i provided aswell.

I found some more issues.
class CraftFeathers has InsertIngredient(1,"Akinaka"); which is incorrect, it should be 0, not 1

DonerKnife & Scimitar are missing from the class CraftArmbandRaincoat aswell
class CraftBolt is also missing all new classes as ingredient

@l909 A bit unhappy that this just got marked as resolved as "user feedback"...
would be nice to know if it is usefull feedback, which you consider implementing at some point. Or if it gets dismissed entirely.

Of course i consider my feedback as a pretty good suggestion because it solves also a bunch of querks in the vanilla CLE as i recently noticed. for example, you currently have set the AK_Suppressor like this in Chernarus

    <type name="AK_Suppressor">
        <nominal>2</nominal>
        <lifetime>9800</lifetime>
        <restock>1800</restock>
        <min>1</min>
        <quantmin>-1</quantmin>
        <quantmax>-1</quantmax>
        <cost>100</cost>
        <flags count_in_cargo="0" count_in_hoarder="0" count_in_map="1" count_in_player="0" crafted="0" deloot="0"/>
        <category name="weapons"/>
        <tag name="shelves"/>
        <usage name="ContaminatedArea"/>
    </type>

this setup makes it so that there is always 2 suppressors spawned. Sure, you have a restock timer defined, but it ALWAYS gets skipped. Because the moment a player picks one of those 2 entities up, the count hits min and the server spawns in a new one. The restock timer in this case might aswell just be 0, no difference.

you can close the ticket.
I had all paths in class CfgMods of my config.cpp files with \ which as someone made me aware of not a legal format anymore.
i replaced them now all with /

i added the complete folder of the TackleBox in the Private attachments as .zip file.
So you can investigate.

I did do some modding recently expanding/refining the list of things that kill a player on log out.
Thats when i learned that players getting kicked is not a restart for the script. I tried to make the game recognize the reason that a player gets kicked for. Players get a window that display the reason for the kick so i thought it should be possible. But as it turns out that that part is not open to the script engine for modding. So i just added all RCON kicks to the list that does not kill players.

Okay so this is not a satisfying reply.
Although i have to admit that i never looked into that messages.xml file. But i will still take the automated system by CF.
The reason is simple:
- when players get kicked directly at restart, they can time certain actions and easily duplicate equipment.
By using CF, i can
- kick players 2 minutes before the restart to make sure that exploid can't be used
- lock the server to prevent players from joining within those 2 minutes or even more.
- add several things that might be relevant before or after a shutdown/restart

for the messages.xml to be a half decent option for anyone that cares, it would need to be able to kick players and to lock the server as well, not just shut it down.

alright... 🥲
see you in december then 😅