Resources

Everything you need to know when creating adventure maps for the AtePlant Archive.

Map Making Guidelines

Everything you need to know to create and submit a map for the AtePlant Archive.

Priority 1: Gameplay

The number one priority is that the gameplay is high-effort, fun, and creative. Your map will not be accepted if it does not meet all three of these criteria. These will be judged loosely, especially the fun part.

If your map requires a plugin, datapack, resource pack, or command blocks that are necessary to how the map is played or enjoyed, you must let me know before you start building so I can approve it. If you want me to make a plugin, datapack, or resource pack for your map, just tell me.

Priority 2: Build Quality

The build should be good. This does not mean your map requires a build to be accepted - floating parkour with some pixel art in the sky is totally fine. However, anything that is built should be high quality.

Do not use any existing map on this server as a frame-of-reference for quality.

Submission Template

Is the map complete?

There are no plot worlds on this server, so all building should be done elsewhere.

If your map requires server-side support to create the gameplay (custom plugins, AteScripts, resource packs, command blocks, etc.), provide the following. Make this post in #support - do not send it here.

Submitting a Completed Map

Use the following fields when submitting a finished map.

AteScript

AteScript is the server's custom Minecraft scripting language parsed and executed by a server plugin. The AtePlant Archive uses Mutiverse-Core where each map gets their own world; However, DataPacks work on a per-dimension basis. In order to alleviate this issue, AteScript was created to replicate the behaviour of DataPacks while also having the events you find in Spigot API. The compiler for AteScript is public, so you are able to test your scripts on a local server.

Script Structure

Every script file is named after its purpose and ends in .atescript. Each script declares a trigger, a world, and then its logic. The following header fields are required at the top of every script:

Variables

$player is automatically set to the player who triggered the script. Additional variables are available depending on the trigger used. This is clarified in the Triggers section below.

Logic & Commands

Logic Statements

Use endif to conditionally end the script.

• 1Syntax: endif <variable> <operator> <value>
• 2Use is / isnot to check if a value is or isn't equal to something.

endif $btype isnot CHISELED_RESIN_BRICKS
/give $player cyan_wool 1

Console Commands

Run any command directly on the console by prefixing it with /. Variables like $player are substituted inline. Also clarify the origin of the command: Use /minecraft:give ... if you are using a base-Minecraft give command, Use /Essentials:give if you are using the EssentialsX give command.

/minecraft:gamemode creative $player

Data Storage

Persist data to a player using the * prefix. Data is stored in persistent data containers and survives across sessions.

Triggers

Triggers define what event causes the script to run. Set the trigger at the top of the script with $trigger <name>.

Examples

$trigger onBlockBreak
$world DarkerBramble
endif $btype isnot CHISELED_RESIN_BRICKS
/give $player cyan_wool[can_place_on=[{blocks:cyan_glazed_terracotta}]] 1

$trigger onTeleport
$world DarkerBramble
/clear $player minecraft:purple_wool
/clear $player minecraft:cyan_wool

Tools

All server-specific tools to help with mechanics and helpful mods to make map-making easier. Commands listed are ones you can use in AteScripts. If your map requires a plugin with a different mechanic/function then:

• 1If it is simple, try to make it using an AteScript.
• 2If it is complex, let AtePlant know through dms or #support to see if that idea is possible, and it will be made for you if so.

Block Triggers

World Settings