KMSI Arma Array Memory Waster, based on Spoody's SQF protection (New Poseidon) . Wipes the server of players. Standalone version from Private KMSI Menu. I wrote this aspect of the menu the day I literally left playing arma, only tested it in Simulated MP, which is still valid in the scheme of testing but still.
SO yeah big time you should not try this on a server, you may say "hey it says crasher in the name", but yeah you still have to give things their respective names, you can't dance around them. But still, I'm saying you shouldn't try this on actual servers because thats illegal (It's a denial of service in all sense of the definition), and it is up to you to weigh the risk of actually getting sued. This is for EDUCATIONAL PURPOSES ONLY IN THE EXPLORATION OF THE ARMA ENVIRONEMNT. THIS IS AS PROVIDED WITH NO WARRENTY WHAT-SO-EVER! YOU AGREE THAT YOU UNDERSTAND THAT THE CODE CONTAINED IN THIS REPOSITORY IS ONLY TO BE USED FOR EDUCATIONAL PURPOSES AND YOU SHOULDN'T TOTALLY DO ILLEGAL STUFF WITH IT. You (the end user) are your own sole individual with their own individual actions, that are attributed to you (the end user).
Load PBO with whatever method you have and hide it. Load into a server and into a unit. Hit the tilda key (key above tab to the left of the number 1 key). Hit 'ARM', then 'FIRE'. This Arm process makes sure you don't nuke yourself by not starting the script unless your player has a safety variable set to not nil.
Payload placed in unshedueled enviroment, no while loops = no timeout = no end. Code runs for as long as the player's client stays responding, not very long really.
(NOTE) This is a POC implementation, it is probably not able to get past script restrictions or even infistar of all things. The crash code is found in fn_nukefire.sqf and is transmitted by fn_nukefireandforget.sqf.
- Dialog opened by player ->
- Dialog option selected by player ->
- SQF executed, placing crash code into executer's Playernamespace temporaily and not saved* ->
- ProfileNamespace Variable loaded with crash code to the variable _crashcode ->
- Compile from the string function initalized (kmsi_fnc_execute) ->
- kmsi_fnc_execute is called with the argument _crashcode ->
- Bis_fnc_mp transfers this function to each machine
- User complies the code on each machine and then executes it (Bypasses the need for fnc_exec_vm or any other function delivery fnc's) ->
- User crashes within 10-20 seconds (Within that time they are not able to interact or alt-tab.) Windows at this point may reset graphics driver or completly crash out to hard reset.
However you may gawk at bis_fnc_mp and I do as well, but its the only way of transfering the code in it's state I really had the time to look into, unless you are confident you have another method in which you can easily adapt the network function.
*Unless the server executes saveplayernamespace in the brieftime you're doing this. Come to think of it, you could just put the code into everyones namespace and make it persistant! Like you could just spread it akin to a viral infection to everyone you meet and whenever you come across them you could just trigger it by asking them to compile the variable in their playernamespace! They couldn't remove it without a script to do so, or using a different profile! A weapon to truely surpass Metal Gear!