Importing Players
Besides generating random profiles, Asteroid can import specific players from a file, both Java and Bedrock. Use this to add a chosen list of accounts, for example your community members or a curated set of Bedrock gamertags, as fake players.
The command
/asteroid importfile <file>The file must be in your plugins/Asteroid/ folder. <file> is just the file name, for example players.txt or players.json.
File format
The file can be either:
A JSON array of entries:
["uuid1", "xuid2"]A plain list, one entry per line.
Each entry is one of two kinds, and Asteroid detects which automatically:
A Java UUID (like 069a79f4-44e9-4726-a5be-fca90e38aaf5)
Asteroid fetches that real account's name and skin from Mojang and adds it as a profile.
A Bedrock XUID (a plain number)
Asteroid uses Geyser to build the Floodgate UUID, fetch the real gamertag (with your Bedrock prefix), and grab the skin.
Example file
Plain list (players.txt):
069a79f4-44e9-4726-a5be-fca90e38aaf5
2535413200000000
d8ec7c9f-3e0c-4a63-8baa-1f6f3a2f9e11JSON (players.json):
Here the UUID entries are Java accounts and the numeric entry is a Bedrock XUID.
Bedrock support
Bedrock entries use the XUID (the numeric Xbox ID). Asteroid runs each one through Geyser to create a matching Floodgate UUID, resolves the real gamertag, and applies your configured Bedrock prefix:
So an imported Bedrock player might appear as *TheGamertag. This requires Geyser and Floodgate on your setup.
After importing
Imported players are added to your profile pool just like generated ones, and the console reports how many were imported. From then on they can be spawned as fake players like any other profile.