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
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2986071927
Step-by-step fix for Rome II mods not loading on macOS
ISSUE:
Mods don’t load properly with user.script.txt, even when you follow the usual Mac modding method.
WHY:
Feral’s macOS version doesn’t auto-create the correct /mods/ folder or link to the real Steam Workshop .pack files. What you see in VFS/local/mods are usually stubs — not the actual mod files.
Create the actual mods folder manually here:
~/Library/Application Support/Feral Interactive/Total War ROME II/VFS/User/AppData/Roaming/The Creative Assembly/Rome2/mods/
Note: This folder won’t exist unless you create it yourself.
Find the real .pack files:
Go to this folder:
~/Library/Application Support/Steam/steamapps/workshop/content/214950/
Each numbered folder represents a Steam Workshop mod. Inside those folders you’ll find .pack files (usually large, 1–7GB). Copy the .pack files you want to use into the mods folder you just created.
Go to this folder:
~/Library/Application Support/Feral Interactive/Total War ROME II/VFS/User/AppData/Roaming/The Creative Assembly/Rome2/scripts/
Create a plain text file called user.script.txt (make sure it’s not a .rtf file from TextEdit).
Write your mods in reverse load order, like this:
mod "modname_2.pack";
mod "modname_1.pack";
Important: macOS loads mods from the bottom up, so the first line is loaded last and has the highest priority.
In the Rome II launcher:
Enable mod support
Uncheck all individual mods
Leave global mod support turned on — just uncheck each mod in the list
Your mods will now load via the script instead of the UI
Fckn oath, enjoy this mod!! ! I litterally just figured it out and have been wanting to play it for weeks now !
https://steamhost.cn/steamcommunity_com/workshop/filedetails/discussion/2280460874/2997669714002809993/
First, navigate to the scripts folder. The exact path is: ~/Library/Application Support/Feral Interactive/Total War ROME II/VFS/User/AppData/Roaming/The Creative Assembly/Rome2/scripts/
In this folder, create a new file called user.script.txt (if it doesn't already exist)
The user.script.txt file loads from the bottom up, meaning the last item on the list is the last file loaded Total War CenterTotal War Center. This is crucial to understand because it's the opposite of what most people expect.
For example, if you have two mod files a.pack and b.pack in your mods folder, and the mod creator instructs you to load A first, then B second (A -> B order), you need to write them in reverse order in the script file like this:
mod "b.pack";
mod "a.pack";
The mod files (.pack files) are located in: ~/Library/Application Support/Feral Interactive/Total War ROME II/VFS/User/AppData/Roaming/The Creative Assembly/Rome2/mods/
The general rule is: whatever the mod author says should load last (to have priority) should be placed at the TOP of your user.script.txt file, since the top entries load last and overwrite previous entries.
@azaris, we are really sorry that AI made u suffer :)
If you don't enjoy the mechanics and the balancing there's not much more we can do.
We can't re-balance the mod to suit every subscriber's needs.
Or create a submod which suits your needs and release on the workshop.