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
Host Havoc seems to have an issue with all ark mods, they seem to randomly restrict the mod files to read only, meaning updates fail to be written to the folder. we get a few users on the discord with this issue every now and again.
This is what the general advice is for this host havoc issue,
Attempt to delete the contents of the mod folder 764755314, then check if the folder is actually empty once you have performed the deletion and also check to make sure the size of the folder is 0mb, if there are still files present or the folder does not read 0mb then there is a restriction on the files somewhere. This is not caused by the mod and this issue only occurs with host Havoc servers. They seem to have this issue with all ark mods, not just this one. Most modders would not suggest using Havoc as a host for this reason.
If you have the the symptoms mentioned above after trying to delete the files, if you put a ticket request to host havoc, saying the there seems to be an issue writing and deleting files from the mod folder, they should take the restrictions off.
Feel free to join the support discord;
https://discord.gg/Y3cpf4j
You will be able to get more help and support there not only from us but from other users who have had the same issues with host havoc and be able to get information on how they resolved it. I believe they just put in a ticket as I mentioned above, but they may be able to offer more details :)
It's something to do with the size of the mod and the speed which Host Havocs auto managed mods script works on a server restart. It deletes the mod, but the auto updater doesn't go fast enough to download large mods correctly, so they become corrupt.
It's simple to fix this issue-
In the commandline manager, untick Auto Managed Mods.
Whenever you need to update a mod, just enter the mod ID into their "update and manage mods" (make sure you enable the Ark Mod Installer/Updater in the Mod Manager.
I now keep auto managed mods off, and have never had an issue since, with this or any other mods updating correctly.
Good luck!