CordIAsis

I'm back! :) I was really poorly for a while but pigs do fly and now I'm fixed :P
I've actually been working on CSAT over the past 3-4 days and got quite a few nice extra features implemented, one of which I just
I'll get a new set of files out in the next few days.

CSAT: Admin-Tool & Anti-Hack
A free & pretty admin-tool and anti-hack.
 
UPDATE
I was very ill, I'm no longer ill(ish).
Which means that I'm now working on CSAT again at long last. I've been working on it for the last 3-4 days and have already got a handful of new features implemented and made quite a few improvements on what was already there. I won't be working on this as much as I used to, I gotta keep my health in check, but the days I do work on it I'm gonna go HAM on this keyboard.
 
Screenies:
Patience, you must have.
 
Video:
Ain't nobody got time for that.
 
Files:
Computer says no.
 
Ideas:
If you have any ideas of what you might like in an admin tool, let me know.
 
Features: (Fractional List)



 

CSAT: Admin-Tool & Anti-Hack
A free & pretty admin-tool and anti-hack.
 
UPDATE
I was very ill, I'm no longer ill(ish).
Which means that I'm now working on CSAT again at long last. I've been working on it for the last 3-4 days and have already got a handful of new features implemented and made quite a few improvements on what was already there. I won't be working on this as much as I used to, I gotta keep my health in check, but the days I do work on it I'm gonna go HAM on this keyboard.
 
Screenies:
Patience, you must have.
 
Video:
Ain't nobody got time for that.
 
Files:
Computer says no.
 
Ideas:
If you have any ideas of what you might like in an admin tool, let me know.
 
Features: (Fractional List)



 

That deals with the problem in the same way as in my first spolier tag, a-la
if (_this isKindOf 'BLAAAAAAAAAH') then { _this removeWeapon 'cannon'; _this removeWeapon 'something'; ....... ..... and so on. }; if (_this isKindOf 'MEHHHHHHHH') then { blah blah blah; }; Which is what I wanted to avoid :)

Soooo, after quite a while of being away (poorly, blah blah) I've finally been able to come back to ArmA scripting about a month ago, woo.
And to kick things off I decided to make a solution for a problem I used to see very often and is probably still fairly common now, getting non DZ/DZE suffixed vehicles to spawn without ammo on server restarts or after being bought. (I actually created this as a feature of CSAT!)
I've seen solutions where people do something along the lines of-





It's a fine solution, if you're only planning on having a few non standard vehicles on your server but it's a gigantic pain in the arse when you want as many vehicles as you can get. This is where my solution comes into play, it's a single function that is run on every vehicle on server start or on being bought or whatever and will remove every magazine from the vehicle with the exception of the pilot's flares and horn.
 
Installation is fairly straight forward too, which is always nice :)
 
Step 1:
At the very top of your server_functions.sqf file add this little nugget (And create the corresponding file, serverside):



Step 2:
Wherever the file is you chose to create, add this into it:



 
This works by over-writing your default fnc_veh_ResetEH, but only serverside so clients don't need to download extra mission data to get a new version of it. fnc_veh_ResetEH is called on every vehicle that is bought or spawned naturally in the world so it will affect every single vehicle. It's also important that you ExecVM your new file from the very top of server_functions.sqf because it needs to catch and replace the default fnc_veh_ResetEH before any vehicles start being made.
 
I can't be sure how it'll affect server start times on servers with hundreds of vehicles but on my dev server with a whopping 16 vehicles it made no difference.
Credit where it's due: Thanks to DenVdmj for the post found here, if I didn't find that I'd be still banging my head against my keyboard trying to figure out how to get turret paths correctly.
 
I've not tried it, but if you wanted to also apply this to vehicles that spawn at missions you could put this-



 
inside wherever it is your mission system spawns it's vehicles and just replace _this with whatever variable references the mission vehicle. (No promises)
 
Enjoy! It's nice to be back :)

Soooo, after quite a while of being away (poorly, blah blah) I've finally been able to come back to ArmA scripting about a month ago, woo.
And to kick things off I decided to make a solution for a problem I used to see very often and is probably still fairly common now, getting non DZ/DZE suffixed vehicles to spawn without ammo on server restarts or after being bought. (I actually created this as a feature of CSAT!)
I've seen solutions where people do something along the lines of-





It's a fine solution, if you're only planning on having a few non standard vehicles on your server but it's a gigantic pain in the arse when you want as many vehicles as you can get. This is where my solution comes into play, it's a single function that is run on every vehicle on server start or on being bought or whatever and will remove every magazine from the vehicle with the exception of the pilot's flares and horn.
 
Installation is fairly straight forward too, which is always nice :)
 
Step 1:
At the very top of your server_functions.sqf file add this little nugget (And create the corresponding file, serverside):



Step 2:
Wherever the file is you chose to create, add this into it:



 
This works by over-writing your default fnc_veh_ResetEH, but only serverside so clients don't need to download extra mission data to get a new version of it. fnc_veh_ResetEH is called on every vehicle that is bought or spawned naturally in the world so it will affect every single vehicle. It's also important that you ExecVM your new file from the very top of server_functions.sqf because it needs to catch and replace the default fnc_veh_ResetEH before any vehicles start being made.
 
I can't be sure how it'll affect server start times on servers with hundreds of vehicles but on my dev server with a whopping 16 vehicles it made no difference.
Credit where it's due: Thanks to DenVdmj for the post found here, if I didn't find that I'd be still banging my head against my keyboard trying to figure out how to get turret paths correctly.
 
I've not tried it, but if you wanted to also apply this to vehicles that spawn at missions you could put this-



 
inside wherever it is your mission system spawns it's vehicles and just replace _this with whatever variable references the mission vehicle. (No promises)
 
Enjoy! It's nice to be back :)

While packing my admin tool up I remembered I had this piece of code which is exactly what you need.
handler = (findDisplay 72) displayAddEventHandler ['unload','_this spawn {hintSilent ""; (_this select 0) displayRemoveEventHandler ["unload",handler];};']; Stick that just after your hintC call and all should be good. Good luck.

CSAT: Admin-Tool & Anti-Hack
A free & pretty admin-tool and anti-hack.
 
UPDATE
I was very ill, I'm no longer ill(ish).
Which means that I'm now working on CSAT again at long last. I've been working on it for the last 3-4 days and have already got a handful of new features implemented and made quite a few improvements on what was already there. I won't be working on this as much as I used to, I gotta keep my health in check, but the days I do work on it I'm gonna go HAM on this keyboard.
 
Screenies:
Patience, you must have.
 
Video:
Ain't nobody got time for that.
 
Files:
Computer says no.
 
Ideas:
If you have any ideas of what you might like in an admin tool, let me know.
 
Features: (Fractional List)



 

You also didn't say you weren't running it, so I thought I would be as clear as I could be.

These snowmen, are you creating them in some sort of map addition which is created when the server starts?
If so, of course it won't work, there's no players on the server to reveal it to :P
I seriously doubt that revealing the object will do any good anyway. You're probably gonna have to accept defeat on finding it with cursorTarget.
I'd suggest doing something like spawning a 'Sign_sphere100cm_EP1' right on the head of the snowman and giving it an invisible texture. This will mimic the effect just fine, player's wont notice a difference.

In the 3D editor, place down a runway peice. Then spawn a small object, like a barrel or campfire and position it in the center of the runway peice. Now click and drag to select both the small object and the runway, then you can position it accurately in the 3D editor.

For everything else... there's Mastercard.

Another update guys.
I've started work on the anti-hack side of it, so far it protects against vehicles being hacked in. In my tests it works perfectly.
I'm planning to build on functions to monitor all kinds of spawnable objects, ammo boxes, buildings, epoch buildables and such.
I've also added in persistent bans and persistent logging for suspicious/hacking activity. All other logs will be made persistent also.
 
On the tools side of it, I've added in assignable admin power levels. There are 3 valid levels and you can modify the required power level for each function in the init file easily. I've also added in a simple welcome message and cycle message system if you choose to use it. Custom boxes and loadouts have been implemented which can be created and edited on the fly. You can choose to spawn boxes publicly or privately also. A debug monitor has been built on too after Elliot from FPG requested it a while back, it's optional so you can still use your own without issue. Server rules can be viewed by players by hitting ESC the clicking on server rules, this is also optional.
About 95% of the admin tool is finished, I just need to implement a little more anti hack before the other tool functions can be created properly.
It shouldn't be too long til a release now! :D

Well the backpack function in this line -
if ((backpack _unit) != "") then {removeBackpack _unit> is an ArmA 3 function, for ArmA 2 you should use unitBackpack.
Also, unitBackpack returns an object, not a string, so you would have to replace that if statement with this-
if (!isNull (unitBackpack _unit)) then {removeBackpack _unit;};

CSAT: Admin-Tool & Anti-Hack
A free & pretty admin-tool and anti-hack.
 
UPDATE
I was very ill, I'm no longer ill(ish).
Which means that I'm now working on CSAT again at long last. I've been working on it for the last 3-4 days and have already got a handful of new features implemented and made quite a few improvements on what was already there. I won't be working on this as much as I used to, I gotta keep my health in check, but the days I do work on it I'm gonna go HAM on this keyboard.
 
Screenies:
Patience, you must have.
 
Video:
Ain't nobody got time for that.
 
Files:
Computer says no.
 
Ideas:
If you have any ideas of what you might like in an admin tool, let me know.
 
Features: (Fractional List)



 

It's quite strange how people can be so disrespectful to the people who are making something for them, FOR FREE. It's a bit like a homeless man spitting in your face because the room in your house you offered him for the night isn't painted in his favourite colour.
It's extremely hypocritical to berate people for the actions they may or may not have taken, insult them on an almost daily basis, yet feel comfortable using their end product. It's disgusting.

It's quite strange how people can be so disrespectful to the people who are making something for them, FOR FREE. It's a bit like a homeless man spitting in your face because the room in your house you offered him for the night isn't painted in his favourite colour.
It's extremely hypocritical to berate people for the actions they may or may not have taken, insult them on an almost daily basis, yet feel comfortable using their end product. It's disgusting.

It's quite strange how people can be so disrespectful to the people who are making something for them, FOR FREE. It's a bit like a homeless man spitting in your face because the room in your house you offered him for the night isn't painted in his favourite colour.
It's extremely hypocritical to berate people for the actions they may or may not have taken, insult them on an almost daily basis, yet feel comfortable using their end product. It's disgusting.

It's quite strange how people can be so disrespectful to the people who are making something for them, FOR FREE. It's a bit like a homeless man spitting in your face because the room in your house you offered him for the night isn't painted in his favourite colour.
It's extremely hypocritical to berate people for the actions they may or may not have taken, insult them on an almost daily basis, yet feel comfortable using their end product. It's disgusting.

Stay away from cultists.

Another little update, cause I feel like I've just been playing Cleudo and finally cracked the case!
Managed to finally get everything 100% serverside :D
I feel so stooooopid, the answer was staring me right in the eyes the whole damn time! XD

Yeah sure you could easily add it to an addAction. I only created this the way it is because I absolutely despise the damn action menu.

I did yeah, I then removed it after I came to my senses and realised just how big a security issue it was. Giving normal players access to certain dialogs is not a smart move whatsoever. It was a derp moment for me, creating that rules menu.

The attitude is probably because they spend day after day, working hard as hell to fix things, implement things and just make things better. Then people come one here, seemingly oblivious to the fact that IT'S NOT EVEN NEARLY FINISHED YET and start talking in a disrespectful way toward the devs and the mod. It can get tiresome when you feel unappreciated by the very community members you are building something for.

I must say. Even my english is better as a 3th language, then his native American language ^^.