🦖 Survival Legends

ASA Perfect Dino Generator — Scriptcommand SpawnDinoInBall · Open this link from your Discord admin channel

1. Player & creature

Replace this example with the target player's ID.

Researched mod creature paths have been added to the main searchable dinosaur dropdown. Some installed mods still need exact blueprint paths. Entries here without paths are placeholders. Select a creature, then paste its exact blueprint below to generate a command. You can also import confirmed paths into the main dropdown.

Search for “S-Dino”, “Moro Rex”, “Draconic Chronicles”, “Paleo Herbivores”, or “Drakara” in the main dinosaur search. Alpha Mosasaurus entries may not be usable with SpawnDinoInBall.

Includes official Lost Colony, Astraeos, Dragontopia and Fantastic Tames creature paths where documented. Tides of Fortune and Bob’s Tall Tales creatures remain subject to path verification. Expanded multi-map creature catalog with additional verified-reference DLC paths. This list is not yet complete; some legacy entries are unverified. Includes some boss and non-tameable entries that may not work with SpawnDinoInBall. Not guaranteed exhaustive or fully verified for the October 2026 game build; test commands on your server. Custom paths remain supported.

Paste any full vanilla or modded creature blueprint path.

2. Command options

The following options reproduce your example. Their exact behavior depends on your installed SpawnDinoInBall server plugin.

3. Stat points (-s)

Set any of the eight stat slots to 0–255. Defaults are all 255, exactly as in your example.

4. Generated command

Command syntax matches your supplied example. Test it with your installed plugin; 255-point behavior may vary.

5. Deliver dino + best available saddle

Generate two separate RCON commands: the Dino Depot ball and a high-quality saddle delivered to the same player. S-Dino variants are matched to their base creature saddle when a matching item path is available; mod-specific saddles still require verification. The saddle arrives in inventory, not equipped on the dinosaur.

Different from Dino Depot's -p identifier.

Quality 100 requests a high-quality saddle, NOT a guaranteed maximum armor rating. Adjust the requested quality for your server and check the resulting armor in-game. The two commands must be executed separately; this webpage cannot send RCON commands itself. Check the selected saddle path before use; missing or unsupported paths cannot generate a command.

Genesis Part 1 expanded with all 21 original X creature types, seven ASA-exclusive X creature types, and additional unique creatures. Newly added blueprint paths marked unverified are placeholders requiring confirmation before use.

⭐ Points Generator

Generate an AddPoints command to award shop points to a player using their EOS ID. Copy the command and run it through your server's RCON bot.

This reason is for your admin records. It is not added to the AddPoints command, which only accepts the player ID and amount in your supplied format.

This page generates the command only; it does not send points automatically. Your server's points plugin must support AddPoints with an EOS ID. No /rcon prefix is added because Discord RCON interfaces differ.

🔐 Permissions Generator

Generate a permissions command for your ASA server. This copies the command only; it does not execute it.

Warning: assigning the Admins group can grant powerful server privileges. Double-check the player's EOS ID and only run this command for trusted administrators. Your permissions plugin must support this exact command syntax.

🎯 Battlepass Quest Objectives

Browse the supplied quest objectives, IDs and required targets. These are reference details, not verified completion commands.

🎟️ Battlepass — Permissions Commands

Generate a Battlepass group permissions command for your ASA server. This copies the command only; it does not execute it.

These are Permissions plugin commands, not a separate Battlepass plugin API. Warning: assigning the Admins group can grant powerful server privileges. Double-check the player's EOS ID and only run this command for trusted administrators. Your permissions plugin must support this exact command syntax.

🚫 Donor Dino Exclusion List

Creatures and categories that are not eligible as donor dinos in Survival Legends.

Creature / CategoryReason / Notes
Reaper QueenBroken
GigadesmodusLost Colony boss fight drop
All Zytharian Tek DinosDeveloper's decision
Extinction TitansExcluded
TitanosaurExcluded
MeksExcluded
Mini Bosses (Ragnarök and Astraeos)No mini bosses

This list is informational; it does not automatically block creatures in the Dino Generator or on the server.

🐉 Draconic Settings

Wyvern Fire, Lightning, Poison — reference settings based on your screenshot. Save changes in this browser, or copy the settings for your server configuration.

Only the Fire Wyvern full path is visible in your screenshot. Lightning and Poison paths above are unverified examples — confirm them before using on your server.

Enabled wyvern variants

This tab saves reference settings only in your current browser. It does not change your Draconic Chronicles plugin settings or execute server commands.

Additional Draconic Spawn Settings

Values transcribed from your screenshot. Blueprint paths are editable references and have not been independently verified. Each entry saves locally in this browser, not to the server.

Ragnarok_Wyvern_Override_Ice1_C

Crystal Wyverns

Crystal Wyvern variants

InfernoWyvernBP_C

Wyvernicorn_BP_C

WyrmBP_C

SandDragonBP_C

BloodStormDragon_C

FlameforgeDragonBP_C

TidalDragon_BP_C

DragonKinBP_C

PolarDragonBP_C

HydroDragonBP_C

RejuvenatingDragonBP_C

GlowveilDragon_BP_C

HeadlessHydraBP_C

Draconic Ancestor

ElderWyvernBP_C

ShadowWyvern_BP_C

For new entries, some spawn-creature paths are not legible in the screenshot; enter the confirmed blueprint path before using them. These settings are stored locally and do not modify your server.

🥚 Incubator Settings

Reference values from your screenshot. Edit and save locally; these do not automatically update the server.

Amount per tick

Seconds between ticks

Number of slots

📘 Survival Legends Moderator Guidelines

The aim of this document is to help/guide the Survival Legends moderator team members with information to assist you in your moderator role.

1. Community-First Moderation

At Survival Legends, we moderate to help, not to punish. Every action you take should be through the lens of: “Does this make the community a better place for our players?”

  • Be Approachable: Don't just be a name in the staff list. Engage with players, participate in events, welcome in new players and show that you are a proud part of the Survial Legends community.
  • Listen First: Before taking disciplinary action, listen to the user’s side. Understanding “why” is as important as “what” happened.
  • Support Growth: Encourage positive behavior. A simple “Thanks for helping that new player” goes a long way.

2. Core Staff Expectations

  • Awareness: Being a mod is not just about answering tickets. Keeping an eye on discord channels is just as important.
  • Neutrality: Remain objective. Personal feelings toward a user must never influence a moderator action. No special treatment for friends/tribe members.
  • Activity: You don't need to be in game to help. Most things can actually be resolved in Discord.
  • Communication: Always report major incidents to the Lead Moderator/Admin. Transparency with the team is vital.
  • Professionalism: You are representing Survival Legends. Keep a cool head, even when users are being difficult (i know you just want to tell them to fuck off).

3. General Moderation: Do's & Don'ts

The Do's

  • De-escalate First: Try to calm a situation before it escalates. If you see something kicking off in game or discord have a polite word.
  • Explain Actions: Briefly cite the rule broken and point them towards the rules in discord if need be. We are a family friendly community after all.
  • Lead by Example: Follow the rules more strictly than anyone else.

The Don'ts

  • Don't Power Trip: Never use tools to “win” an argument.
  • Don't Argue in Public: Move disputes to Tickets or DMs immediately.
  • Don't Leak Internal Info: Keep staff-only channels confidential (this includes tribe members).

4. Ticket Handling & Support

StepActionDescription
1. ClaimAssignClaim the ticket so others know it is being handled.
2. InvestigateResearchCheck logs, user history, provided evidence and be sure to read the whole ticket there is nothing more frustrating than having to repeat yourself when all the information is already in front of you.
3. ResolveActApply the fix or issue the necessary outcome.
4. CloseFinalizeEnsure the player feels that the ticket has been resolved and prompt them to now close the ticket. (we do not close tickets ourselves) At this point the ticket can be renamed and deleted or just deleted.

5. Support for the Team

NEVER BE AFRAID TO ASK FOR HELP!

Moderating can be stressful and sometimes situations are not black and white. We are a team for a reason.

  • Unsure of a Rule? If you aren't 100% sure how to handle a situation, reach out to the Lead Moderator or an Admin before taking action.
  • Feeling Overwhelmed? If the community is being toxic or a ticket is getting to you, step back and ask another team member to take over. Your mental health matters.
  • Mistakes Happen: If you make a mistake, don't hide it. Tell the team immediately so we can fix it together. We are here to support you.

📋 Admin Command Logs

Records when an admin clicks a command-copy button. These are local browser activity logs, not confirmed RCON executions. Each admin has a separate log on their device.

Logs are saved only in this browser's local storage. Clearing browser data or using another computer may remove them. A shared, tamper-resistant audit log requires a secured server/database. Do not treat a copied command as proof it was executed.