-
Content count
9 -
Donations
0.00 EUR -
Joined
-
Last visited
Community Reputation
3 NeutralAbout Swash
-
Rank
Bambi
Personal Information
- Homepage
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Ok for everyone else wondering the same thing. I do not know why I keep hearing that removing triggers (sensors) disables loot/build restrictions and removes the marker. I've read this multiple places, which prompted this post in the first place. It's simply not true. Just as GR8 said, removing the triggers does NOTHING else, other than kill safe zones and enter/leaving messages. Simply derapify your mission.sqm (if you haven't already) Look for the 3 entries under "class Sensors" and remove them. Save your mission.sqm (rapify optional, I don't bother) PBO your map and you are done. (note windows server doesn't seem to care if you don't have your map folder PBOed, linux however get's cranky if you don't. lol) Markers stay, building restrictions stay, loot restrictions stay. Later I will post replacements for the triggers so you can still have alert messages saying "Entering/Leaving Trader Area."
-
Thank you GR8. Copy that Cupcake_Actual
-
That's exactly why I'm asking for another way lol I want to keep loot spawn and building restriction, and the map markers, but kill the "safe zone" part. This really should be optional in settings...
-
First make sure you have the HC's IP listed in your servers config.cfg.. if the HC is on the server machine use this. //headless client localClient[]={127.0.0.1}; headlessClients[] = {"127.0.0.1"}; battleyeLicense=1; If it's on a network machine use the network IP for the HC. If it's over the internet use the external IP. Make sure you have the headless client section added to your mission file. (as per the instructions) If you are getting battleye kicks, look at the battleye logs to see what needs to be fixed. When testing I like to set everything to 3 in my battleye restrictions so it just logs everything, but allows me to see if everything is working. Then I look at the logs and make the appropriate adjustments to battleye then set everything back to 7 when I've got everything else playing nice.
-
One thing I absolutely can't stand is "safe zones" in an apocalyptic scenario. Life is supposed to suck and suck hard. No place should ever be "safe". I like knowing trading is a risk, and a team effort to get through the ordeal. Even through I'm the one most likely to get ganked. lol That said, how would one go about removing the "safe zone" part without removing trade post map markers and loot spawn/building restrictions for trader areas?
-
There is nothing extra that I know of that needs to be changed. Just make sure the config.cfg on the rental server has the correct IP from the HC connecting. I can see from your setup you have the client IP the same as the server IP. You have 213.163.69.57 as your client ip and you are attempting to connect to 213.163.69.57. They are the same, so one of those IP's is wrong. d:\localuser\g557551\arma3server.exe" -client -nosound -connect=SERVERIP -port=2312 -mod="@Exile" -profiles=HCLogs headlessClients[] = {"HCIP"}; I don't think localClient is needed since it's not local. Don't forget to upload your map mission.sqf as this has the HC info required for the client to connect. Then check your server logs to see if the client is connecting or attempting to connect and go from there. You should also note a headless client should be on the same machine or at least in the same local network or latency will be a big concern. You are likely to get alot of complaints of impossible to kill ai. Best bet would be to find a host that does Arma 3 servers with HC.
-
Where would I go about changing how mission messages are displayed. I'd like to move them away from the top middle. They seem to get in the way a lot.
-
Here is a couple of scripts that will backup database with date/time stamps and cleanup old backups. First let's create the backup script. dbbackup.sh Now we create the cleanup script. dbcleanup.sh Use the "crontab -e" command to schedule these scripts. You can use this to help with your schedule. I add this to the end of my cron to schedule backups every 30 minutes and cleanup once a week. (4am sundays) You will want to change the locations of your scripts accordingly.