Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
(Of your main Steam installation, not where you have Arma installed.)
----> C:\Program Files (x86)\Steam\userdata\*Top Folder*\107410\remote
Take this and put it in the mission folder for your server. Hope this helps.
No entry 'mpmissions/__CUR.MP.mske/description.ext/liberation_deploy/DeployMap/widthRailWay' .
Any fixes?
To find the PBO file for the mission, after you subscribed and steam updated your Arma Workshop, navigate to your Steam Userdata folder.
(Of your main Steam installation, not where you have Arma installed.)
----> C:\Program Files (x86)\Steam\userdata\*Top Folder*\107410\remote
Should be in there so you can copy it to your dedi server, hope that clears it up.
I recommend reading up on a KP Liberation guide such as this one: KP Liberation
It is a lot to read, but worth it if you really want to get into it. Note that a lot of values and things don't apply to my mission, as I adjusted most of them. But the general idea is the same of course. Hope this was helpful.
Cheers.
If you are using some kind of external dedicated server software, like TADST, you will need the mission PBO.
To find the PBO file for the mission, after you subscribed and steam updated your Arma Workshop, navigate to your Steam Userdata folder.
(Of your main Steam installation, not where you have Arma installed.)
----> C:\Program Files (x86)\Steam\userdata\*Top Folder*\107410\remote
Take this and put it in the mission folder for your server. Hope this helps with the issue you have.
As for the issue. Are you certain that you have logged in as an admin in your dedicated server?
(Type in game chat: #login "password") Please double check this first, admin password needs to be set in your dedi server software or in the settings file for the server.
If it still does not work, I will check if I messed the code up in the last update.
For one, anything else happen? Text message or something?
Only air vehicles, or is this related to any vehicle?
Are the vehicles from RHS or Vanilla that kick you back out?
Any additional mods that where used, such as vehicles or faction mods?
Vehicles where bought with the in-game systems or spawned in via Zeus?
If these vehicles happen to be from the A3 Jet DLC and you should not have it, you will have to give me 20 pushups Cadet...
But if you add vehicle mods, they won't just show up in the build menu. Simple way to get them would be to log in as admin and spawn them in with zeus or via debug console!
Otherwise you would have to edit the mission file with a pbo editor.
But don't give me too much credit haha ^^ I only changed most of the game values and implemented new scripts and made my own scripts for it as well.
Other people deserve praise for it more than me.
Inside the mission PBO, navigate to the UI folder.
There you will find "mission_params.hpp" Search for the value "class HaloJump"
Replace 'default = 15' with 'default = 0'
It that should fail somehow, when you are in the slot select screen, as admin, at the top click on Parameters, which is essentialy temporarely adjusting the file I just directed you to previously.
As for the mobile respawn, there is a mobile respawn truck instead of the helicopter, maybe try that one instead, to move it closer. Use rocks and hills for cover etc.
But a respawn Tent was something I already thought about, I'll see if I can look more into it since you mentioned it.
For now I recommend using the ground mobile respawn truck.
I hope that the current version causes no problems. Until next time.
Allright! The Arma3Profile file is the mission progress you are looking for. TADST is build up the same way. When you replace the mission with the updated one make sure to not change profile name, and that the mission name stays the same as the outdated one. For saftey of course just make a copy of the entire previous folder, and if putting in the update is not working, you could always roll back by replacing the old folder. I locked a bit into the code again and it should work as intended. So once you updated the mission to V0.5, Zeus should work by a logged in admin!
How are you hosting the mission? Are you hosting it by a third party, or are you using TADST on a dedicated server? If it is TADST, replacing the mission file wont change progress at all, just make sure that the file name is exactly the same as before.
Look a few more comments below to see the same person asking about how to backup saves with TADST. If it is not this dedicated server tool you are using, please tell me what you are using so I can tell you more.