Setting the wild creature cap to 150 does not mean most creatures will be near level 150. The maximum level that can spawn and how often each level is selected are different things. Creatures that were already present before the change also cannot confirm the new spawn conditions.
This guide covers standard wild creatures on an ASA dedicated server whose settings you can change. Leave special spawn conditions such as caves, special creatures, and creatures whose levels were changed by mods out of your initial comparison. These are dedicated-server settings, not steps for changing the local settings on a participant's PC, PS5, or Xbox. Console controls vary by platform and should be checked separately.
Choose what to check based on the symptom
| Symptom | Check first |
|---|---|
| Many low-level creatures even though the cap is 150 | Check the level increments on new creatures, not just the setting value |
| A creature from before the change remains at the same level | It is an old creature and cannot tell you whether the new settings took effect |
| Levels appear as 5, 10, 15… but none are 150 | Compare multiple locations; a few creatures cannot confirm the cap |
| Unexpected increments keep appearing | Check the file or panel being edited, saved values, mods, and which creatures you observed |
| Only some creatures exceed the expected cap | Check the conditions for that creature and spawn location |
The two settings and how “increments of 5, cap 150” relate
Both are difficulty-related settings under [ServerSettings] in GameUserSettings.ini.
| Setting | Role and caveat |
|---|---|
| DifficultyOffset | A difficulty-related modifier. Its value is not the maximum level itself. |
| OverrideOfficialDifficulty | Overrides the difficulty. 5.0 is a reference value for a level-150 cap on standard wild creatures. This is not a field where you enter 150 directly. |
For creatures that use the standard 30 base level tiers, difficulty 5.0 corresponds to levels 5, 10, 15…150. The override value multiplied by 30 is a rule of thumb for the ordinary maximum level; do not apply the same calculation to special creatures or special spawns.
Example setting line for a level-150 cap on standard creatures
On a dedicated server where you have admin access, check the existing [ServerSettings] section in GameUserSettings.ini. This is an example of where the override value goes.
[ServerSettings]
OverrideOfficialDifficulty=5.0Do not enter 150 as the value; edit the existing key. Do not append duplicate sections or lines at the end of the file. DifficultyOffset is a separate setting, and this one line is not a complete settings file that applies to every environment.
Record the old values, then save the world, shut the server down normally, back up the settings and world, edit and save, and start the server. If you use Override Official Difficulty in Nitrado's general settings, save the value 5 and restart. Do not alternate between the same setting in the panel and in the INI file so they overwrite one another. Confirm the change using new creatures as described below; this setting does not make every creature level 150.
Do not keep increasing DifficultyOffset. Check the OverrideOfficialDifficulty value and whether the admin panel or startup settings retain a conflicting value. If you use a “Maximum Difficulty” toggle, record its state too.
See the basics of changing server settings (Japanese only) for editing, and the server settings reference (Japanese only) for setting locations and support notes.
Confirm the change on newly spawned creatures
Do not treat an old low-level creature that remains in the world as proof that the settings failed. Changing settings and replacing wild creatures are separate tasks. A restart alone does not mean every creature has been replaced.
First check that the settings were saved, then inspect creatures that spawned afterward. It is easier to assess the result if you leave creatures whose age you cannot determine out of your confirmed observations.
Before using a full wild-creature wipe
DestroyWildDinos is an admin command that removes untamed creatures from the map. It may also remove the wild creature you were looking for or an untamed creature involved in a taming process. It is not a required step for confirming a settings change.
If considering it, the administrator should first check that:
- The target server and map are correct.
- Participants have been notified, and there are no wild creatures or taming activities they need to keep.
- The world and settings are backed up and the restore process is understood.
An administrator who chooses to run it connects to the target server in-game and enters cheat DestroyWildDinos in the in-game console after admin authentication. This is an in-game admin action after startup; it is not a setting line for GameUserSettings.ini or Game.ini, and it is not an SSH or PowerShell command. See Nitrado's ASA admin-command guide for opening the console and authenticating. If authentication fails, do not try another input method; contact the administrator.
A wipe does not guarantee high-level spawns. Respawning takes time, so do not change the settings again based only on the number of creatures immediately afterward or on just a few observations.
Follow this order to narrow down the cause
- Separate the goal from what you observed. Record what is known, such as “I want a level-150 cap for standard creatures,” “I see many low-level creatures,” or “I do not know whether these are old or new.”
- Check the settings that are actually in effect. Compare the server connection, file or panel being edited, [ServerSettings], and saved values. If values revert, inspect the admin panel or settings-generation feature.
- Use a consistent comparison set. Observe standard wild creatures at multiple locations on the same map and record levels on creatures that spawned recently. Track creatures with special conditions separately.
- Consider increments and the highest level observed together. Increments of 5 alone do not prove the value is 5.0, and not finding level 150 does not prove failure. Seeing the target level on a standard creature makes it less likely that the cap is still too low.
- Change only the part that matches the cause. If values do not persist, check the editing method; if only old creatures are involved, change what you observe; if only some creatures differ, check their species, location, or mod conditions. Change one thing at a time and keep before-and-after notes.
If you want a higher share of high-level creatures
Some distribution mods for ASA let you choose an even level distribution or one that favors higher levels. Consider them after confirming that the cap took effect. If you already use a mod, check the author's documentation for the affected creatures and how the change applies. This guide does not provide specific spawn probabilities by map.
Sources and references
Questions and contributions
Share questions, corrections or play reports. Only approved posts for this article and language appear here.
Submit for review
Do not include personal details, passwords or private information about others. Text only. Publication and replies are not guaranteed.