- Importing an Existing Config
- Using Beacon with Ark Single Player
- Updating Your Nitrado Server
- Updating Your Server With FTP
- Updating Your Server Manually
- Ark Config File Reference
- The Difference Between Deploy and Export
- Using Config Sets
- Using Presets to Automate Item Set Creation
- Adding Unsupported Engrams, Creatures, or Spawn Points to Beacon
- Preset Selectors Guide
- Breeding Multipliers
- Crafting Costs
- Creature Adjustments
- Creature Spawns
- Custom Config
- Day and Night Cycle
- Decay and Spoil
- Engram Control
- Harvest Rates
- Item Stat Limits
- Levels and XP
- Loot Drops
- Stack Sizes
- Stat Multipliers
- Create or Recover Your Account
- Sign Into Beacon
- Activating Beacon Omni
- Sharing Beacon Documents with Other Users
- About User Privacy
- Item Quality Is Different Than Expected
- Loot Drops Are Not Working As Intended
- How to Stop Using the Custom Config Editor
- Solving Connection Problems to Beacon or Nitrado
- Beacon System Status
Adding Unsupported Engrams, Creatures, or Spawn Points to Beacon
Beacon maintains a database of nearly all items in the game, and some mods list their contents with Beacon, but most mod items need to be added to Beacon by the user.
If you find that something is missing which Ark supports without mods, please let us know.
What You Need
Beacon needs the full blueprint path to everything you want to add. Beacon can extract the paths from the spawn cheats, such as
cheat giveitem or
cheat spawndino. Less specific variants, such as
cheat summon, and
cheat spawnactor will not work, as they do not contain the full blueprint path or do not provide Beacon with enough information. If you don't have the cheat codes, you will need to add items one by one.
If you only have the class strings, such as
PrimalItemStructure_Something_C, Beacon will allow you to enter the value as a blueprint path. You will be warned that doing so is not recommended, because Beacon will need to make up a fake path for the item. It will not be correct and could cause confusion should the correct path ever be added to Beacon.
At the top of the window, select the Blueprints view. This is where mod authors can manage the engrams, creatures, and spawn points their mod provides. But all Beacon users also have a "User Blueprints" mod that is exclusive to their Beacon account. This isn't really a mod, but it is used by Beacon to separate user-specific content from content shared by all users. For most users, selecting the Blueprints view will also automatically open the User Blueprints mod for editing.
In the User Blueprints mod tab there are seven buttons. From left to right, they are:
- New Blueprint, which is used for adding a blueprint manually.
- Import File, which imports all available blueprints from the selected file. The file must contain the cheat codes; it cannot import from Ark game files.
- Import URL, which imports all available blueprints from the provided url. The url must contain the cheat codes.
- Import Copied, which will be disabled until you have copied cheat codes. Pressing it will import from the copied cheat codes.
- Export, will prepare a JSON file of your blueprints that can be imported by another user or onto another computer.
- Save or Publish will be used for saving changes to the mod. Save will be displayed for the User Blueprints mod, while Publish will be displayed for globally-shared mods.
- Revert will discard all the changes made and restore the mod back to the last saved or published state.
Adding From a Website
The easiest way to get items into Beacon is using the Import URL button described above. Enter the full URL to a web page containing the cheat codes, and Beacon will attempt to do the rest.
This feature works with most websites, but some websites such as Google Docs will not work with Beacon.
Adding From the Clipboard
When adding from a website isn't practical, you can also copy the cheat codes for Beacon to import. Beacon can find any number of codes through just about any formatting, so selecting a copying an entire column of codes from a Google Docs spreadsheet should work just fine. Once you have copied at least one working cheat code, the Import Copied button will become enabled. All you need to do is click it.
Adding From a File
Beacon can also import from a file on your computer. Just like the other methods, formatting is not important to Beacon. Select a file containing cheat codes in some form, and Beacon will try to find them.
Pressing the New Blueprint button will present an empty editor for the new blueprint.
See the next step for editing blueprints.
Everything that Beacon has imported will be listed in the list. Double clicking a blueprint allows it to be edited.
Every field is important in some way. For imported blueprints, the Type and Blueprint Path fields should almost never be changed. Manually created blueprints will need these filled in though.
Beacon will guess at the blueprint name based on its path. While these are reasonable guesses, if you wish to fine tune the names, use the Name field to do so.
The Tags field allows you to add organization to your blueprints. You can add as many tags as you like, separated by commas. Beacon uses a few special tags.
Blueprintable means the blueprint can be a blueprint in the game, and causes Beacon to enable the Chance To Be Blueprint setting in the loot drop editor. The
Blueprint tag is tells Beacon the blueprint is a recipe, such as the "Element from Dust" blueprint that crafts Element. The
Generic tag tells Beacon that the blueprint is non-specific, such as "Any Egg" or "Any Artifact" and is intended for use in crafting recipes. The loot drop editor will not export or deploy drops containing engrams with either the
The Map Availability checkboxes tell Beacon which maps to pre-select when adding the blueprint to a Preset. Most users choose to leave all maps selected.
There is an Advanced tab at the top of the blueprint editor that will display a different set of fields depending on the blueprint type. These advanced fields are optional, but each can help Beacon in some way. If you choose to set these values, be sure to set them to match their in-game values, not the values you would like them to be.
Entry String, Unlockable At Level, and Required Engram Points will allow the engram to appear in the Engram Control editor.
Stack Size is used by Beacon's Stack Sizes editor to make sure the user does not set the stack size greater than Ark can handle. For example, Ark stack sizes cannot exceed 2,147,483,647. If the engram normally stacks to 1,000 and the user were to enter a Global Stack Size Multiplier value of 10,000,000 (don't laugh, users do it) Beacon will know the engram would exceed the maximum and automatically insert a
ConfigOverrideItemMaxQuantity line to limit the engram appropriately.
Crafting Recipe is used by Beacon's Crafting Cost editor when the user checks the Load Official Values When Available checkbox. It also allows the Adjust All Crafting Costs tool to work on the engram.
Incubation Time and Mature Time are for the incubation/gestation time and mature times for the creature. Setting these values will allow the creature to appear in the Breeding Multipliers editor.
Mating Interval Min and Mating Interval Max are used to specify the default range of the creature's mating interval.
Stats will allow the creature to appear as a preview option in Beacon's Stat Multipliers editor.
The Advanced tab for a Spawn Point is a full spawn point editor. Use this to provide Beacon default values available when the user choose the Load Simplified Defaults in Beacon's Spawn Points editor. This data also allows the Convert Creature Replacements to Spawn Point Additions tool to function corrected with the mod's spawn point.
Users can select multiple blueprints to edit them at the same time. Right click any of the selected blueprints and choose Edit.
When selecting multiple blueprints, only the Tags and Map Availability options will be available. No Advanced tab will be available when editing multiple blueprints. Blue tags will be added to all blueprints that do not already have the tag, and Red tags will be removed from any blueprint that has the tag. Gray tags will be left alone, neither added nor removed from any blueprint.