- 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
- How to Design Loot Drops Effectively
- How to Edit Crafting Costs
- Changing the Level Cap and Required Experience
- How to Change Stack Sizes
- Using Custom Config Content with Beacon
- Adjusting Breeding Multipliers and Finding the Perfect Imprint Multiplier
- Changing Creature Damage and Resistance
- Setting Harvesting Rates While Avoiding Server Lag
- Editing Creature Spawn Points
- Adjusting Server Day and Night Length
- Changing Player, Tamed, and Wild Creature Stats
- Setting Item Maximum Stats
- Controlling Engram Level Requirements, Auto Unlocks, and Earned Engram Points.
- 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
- Some Drops Are Edited, Others Are Not
- How to Stop Using Custom Config Content
- Solving Connection Problems to Beacon or Nitrado
- Beacon System Status
About User Privacy
Beacon takes user privacy very seriously. The data here may get a bit technical, so here's the simple outline:
- All user data is anonymous, even email addresses.
- Encryption is handled with 2048-bit RSA Public Key Cryptography.
- Beacon and its website are fully open source.
Beacon stores only a single piece of identifiable information on each user: their username. Which of course, could be anything the user desires. User email addresses are stored as salted bcrypt hashes with k-anonymity. This allows email addresses to be confirmed during login, but cannot be reversed.
Upon first launch, Beacon generates a cryptographically secure 128-bit random number to use as the user's UUID. This number is not based on any user or hardware information. Beacon also generates a 2048-bit RSA private key to use as proof of identity.
Unless the user chooses to disable community features when prompted at launch, Beacon will send the user's UUID and public key to the Beacon server. This grants the user access to community features, such as the ability to publish documents to the community library. This user is fully anonymous.
If the user decides to create a login with Beacon, some additional data is shared with Beacon's server. The user's password is run through the PBKDF2 algorithm to generate a key to Blowfish encrypt the user's RSA private key. Beacon's database stores these encrypted private keys so they can be transported to other computers the user signs into. When signing into Beacon, the private key is delivered to the computer encrypted and decrypted on the computer, not on Beacon's server.
Some parts of a Beacon document are encrypted using the user's private key, such as server information and user-defined parts of the Custom Config Content editor. If the user's private key cannot decrypt information from a document, that information is simply not loaded by Beacon.