Help Guides &
Frequently Asked Questions
Browse setup information, troubleshooting steps, common questions, and official support resources for Cliffans Mods.
Help library
Choose a section below. New guides and answers can be added as recurring questions come up.
General Mod FAQ
Common questionsInstallation, support, commissions, compatibility, and bug-reporting information for Cliffan's mods.
＋
How are commissions handled?
New commission tickets are currently on hold while the existing backlog is reduced. New slots are expected to reopen closer to October, with Patreon members receiving priority. Check the commission information in Discord for the latest availability before opening a ticket.
How long will a commission take?
Completion time depends on the size of the project, current workload, feedback, and whether an ARK or DevKit update causes additional work. An exact completion date cannot be guaranteed before the project has been reviewed and scoped.
How do custom cosmetics work in ARK: Survival Ascended?
Custom cosmetics are client-side and do not appear in the normal mod list. See the How custom cosmetics work guide below for inventory access, server validation, and custom whitelist information.
Why can mod updates take time?
Cliffan maintains more than 17 mods while also creating new models, animations, and systems. Major ARK updates can break existing features and require compatibility work before planned development can continue.
Will a suggestion be added?
Suggestions are welcome, but they are not guaranteed. Commissioned work, existing commitments, bug fixes, and planned updates generally receive priority.
Where are spawn commands and configuration settings?
Open the relevant mod page and check its reference and configuration sections. Some pages are still being expanded, so missing information may not yet have been verified.
How are loot drops or creature spawns adjusted?
These usually use ARK's standard server configuration settings rather than a mod-specific option. Tools such as Beacon can help build compatible loot and spawn configurations.
Are the mods cross-platform?
Most are. Check the platform label near the top of the relevant mod page for the current compatibility information.
How should a bug be reported?
Use the website's bug-report form and include the mod, platform, map, version, other installed mods, and clear reproduction steps. Discord is better for general questions that are not reproducible bugs.
What should I try before reporting an issue?
Confirm the mod is fully updated, restart the game or server, and test without likely conflicts when possible. If the issue continues, submit one focused report with the steps that cause it.
Asset resources
Finding compatible 3D assetsMarketplaces and checks to consider when sourcing a model or asset for commissioned work.
＋
These marketplaces are useful when looking for models or source assets for a commission. Always check the license, included file formats, topology, rigging, texture files, and whether the asset can be used in a mod before purchasing it.
Fab
Generally reliable, with clear product details and a wide range of game-ready assets.
CGTrader
Offers a wide range of prices and quality levels. File information is usually available, which makes compatibility easier to judge.
ArtStation Marketplace
Often has high-quality and affordable assets, but listings do not always provide enough technical information. Check the included files carefully before buying.
Sketchfab Store
Quality varies, but many listings provide useful file and model information.
Other options include TurboSquid and Free3D.
Custom Cosmetics
How custom cosmetics workWhere cosmetics appear, how unofficial-server validation works, and how to configure a custom whitelist.
＋
Where custom cosmetics appear
Custom cosmetics will not show up in your mod list. They are client-side content, so open the cosmetic tab in your inventory to confirm that they are installed and available.
Adding a custom cosmetic to the server's normal mod list does nothing. It does not install or enable the cosmetic for players.
Unofficial servers and validation
By default, unofficial servers that enable cosmetic validation rely on the official whitelist. New custom cosmetics can take time to appear on that whitelist, and some may not be accepted. If a server is not relying on the official whitelist, the server owner must explicitly enable and allow the cosmetics before players can apply them.
For official-whitelist validation, server owners use the -DoCustomCosmeticValidation command-line argument. See Studio Wildcard's unofficial-server validation instructions for the current technical details.
Using a custom whitelist
Custom whitelists can be confusing because the system has changed several times. The whitelist must be hosted as a public plain-text file at a URL that clearly ends in .txt. Add each custom cosmetic as its own entry in that file.
The current entry format contains four parts:
Mod ID | Enable Dynamic Download (0/1) | Allow non-dataonly blueprints (0/1) | Calculated package CRC
The CRC must be updated whenever the cosmetic mod updates. Server owners can add -log -PrintCosmeticCRC to the Steam client launch arguments to print the current values for installed cosmetics.
If the whitelist file is inaccessible, does not end in .txt, contains an outdated CRC, or is not configured correctly on the server, the cosmetic may appear installed but still cannot be applied.