MINR.ORG WIKI - User contributions [en]

Tet's Dark Maze

2025-08-18T22:21:56Z

Tetration:

{{Infobox_Map
| image = dark_start.png
| caption = Take the plunge into the dark
| points = 4
| location = FFA
| mapcode = dark
| creators = Tetration, ZombieKiler
| foodtype =
| foodamount =
| publication = Mar 4, 2022
| description = Tet's Dark Maze is a pure maze map on zero.minr.org, worth 4 points. Use "/join Tet's Dark Maze" to join the map.
}}

Tet's Dark Maze is a pure maze map on zero.minr.org by Tetration and ZombieKiler. It awards 4 points. Use "/join Tet's Dark Maze" to join the map.

== General ==

=== Gameplay ===
Tet's Dark Maze is a unique experience on Minr. You are given the map to the maze and you have to figure out what to do to win. Since you are submersed in total darkness, the best way to play is to not move the mouse and simply use movement keys to navigate the map. The effect of this is that you are essentially playing a 2D maze game on the map, reminiscent classic flash games.

Tet's Dark Maze is best enjoyed on the Nightmare Mode setting which adds some fun horror elements to the map. This can be disabled for accessibility purposes, but if you don't have light sensitivity it is highly recommended to play on Nightmare Mode. Either way, be sure to adjust settings as instructed at the beginning of the map.

=== Aesthetics ===
Tet's Dark Maze has a simple palette of mostly black concrete. The resource pack the map provides makes the black concrete pure black so that it can't be seen at all. The resource map also makes most HUD elements invisible to enhance the immersion. The resource pack also provides music, sound effects, and some extra textures.

== Challenges ==
This map appears in 5 [[Challenge|challenges]]: 2022 Assortment, Hexa Challenge, Hexa Chapter III: New Heights, Sightseeing 2022, The Amazeingly Painful Marathon.

== Trivia ==
*The horror elements were added late into the creation of the map to make it more engaging and give Bailey06 a punishment for not playing Wrong Floor.
*This map shares a lot with the 2003 Flash hit, Scary Maze Game, but this was not an intentional inspiration.
*The blue and yellow dots used to be green and red, but this was changed to be colorblind friendly.
*The actual map was mostly built around 2018 as mostly a joke map with no intention of being in FFA.

Tet's Dark Maze

2025-08-18T22:20:02Z

Tetration: Created page with "{{Infobox_Map | image = dark_start.png | caption = Take the plunge into the dark | points = 4 | location = FFA | mapcode = dark | creators = Tetration, ZombieKiler | foodtype..."

{{Infobox_Map
| image = dark_start.png
| caption = Take the plunge into the dark
| points = 4
| location = FFA
| mapcode = dark
| creators = Tetration, ZombieKiler
| foodtype =
| foodamount =
| publication = Mar 4, 2022
| description = Tet's Dark Maze is a pure maze map on zero.minr.org, worth 4 points. Use "/join Tet's Dark Maze" to join the map.
}}

Tet's Dark Maze is a pure maze map on zero.minr.org by Tetration and ZombieKiler. It awards 4 points. Use "/join Tet's Dark Maze" to join the map.

== General ==

=== Gameplay ===
Tet's Dark Maze is a unique experience on Minr. You are given the map to the maze and you have to figure out what to do to win. Since you are submersed in total darkness, the best way to play is to not move the mouse and simply use movement keys to navigate the map. The effect of this is that you are essentially playing a 2D maze game on the map, reminiscent classic flash games.

Tet's Dark Maze is best enjoyed on the Nightmare Mode setting which adds some fun horror elements to the map. This can be disabled for accessibility purposes, but if you don't have light sensitivity it is highly recommended to play on Nightmare Mode. Either way, be sure to adjust settings as instructed at the beginning of the map.

=== Aesthetics ===
Tet's Dark Maze has a simple palette of mostly black concrete. The resource pack the map provides makes the black concrete pure black so that it can't be seen at all. The resource map also makes most HUD elements invisible to enhance the immersion. The resource pack also provides music, sound effects, and some extra textures.

== Challenges ==
This map appears in 5 [[Challenge|challenges]]: 2022 Assortment, Hexa Challenge, Hexa Chapter III: New Heights, Sightseeing 2022, The Amazeingly Painful Marathon.

== Trivia ==
*The horror elements were added late into the creation of the map to make it more engaging and give Bailey06 a punishment for not playing Wrong Floor.
*This map shares a lot with the 2003 Flash hit, Scary Maze Game, but this was not an intentional inspiration.
*The blue and yellow dots used to be green and red, but this was changed to be color-blind friendly.
*The actual map was mostly built around 2018 as mostly a joke map with no intention of being in FFA.

File:Dark start.png

2025-08-18T21:42:37Z

Tetration: Starting room in Tet's Dark Maze

== Summary ==
Starting room in Tet's Dark Maze

Hardcore

2025-06-30T12:15:48Z

Tetration: /* Version 11.0 - 11.1 */

== Overview ==

Hardcore (Commonly shortened to HC) is a series of challenging parkour, maze, puzzle, and adventure maps. Hardcore serves as a challenge that tests players' trustworthiness and integrity before granting them build rights. It is the sole requirement to earn Green (Builders) rank on the server.

There have been 11 major versions of Hardcore, with tuning changes to balance difficulty, or to make adjustments for changing game mechanics.

Historically, it has also been called the rotation, the HC rotation, or the gauntlet.

Hardcore has difficulty elements not seen in FFA, such as:
* Limited quantities of food / little to no saturation.
* Item pickup being disabled to prevent food sharing.
* Having to play multiple maps without checkpoints in-between.

Levels within hardcore are notated with a dash (Ex: HC-1), and versions are notated with a dot (EX: HC 1.0)

== Current Iteration ==
[[File:Hc12.png|800px]]

== Hardcore Iterations ==
=== Version 1.0–1.4 ===
[[File:Hardcore 1.0.PNG|600px]] 

During this time period, Hardcore was iterating rapidly as new maps were created. Since these iterations used a similar design, they are grouped collectively under "1.0".

At this stage in the server's history, both the game and the server's identity were early in development. FFA and the blue rank did not exist; Minecraft was in the Alpha / Beta stages of development. The checkpoint system we use today was non-existent. Minecraft was a new game, and only a couple hundred-thousand players owned the game. At this time, spawn was in the TNT cube, but was shortly switched to the desert spawn.

In the beginning, there were only the trials found within the TNT cube at X. Player's spawned at the bottom, and warped into the following lineup:
* 1. Skytop Labyrinth
* 2. Original Level 2 (No warp, the maps were linked)
* 3. Jiga's Claymaze

This is the earliest known iteration of HC, and lasted for less then half a year. Note that the maps were not all implemented simultaneously. This meant for a time Hardcore only contained one or two maps. The next iteration of HC (1.1) consisted of 5 Levels with no checkpoints in-between the maps. From this point forward maps would swap with one another to maintain the 5-map course design.

This layout created a unique meta because it meant if the player died in any level, they had to start over at the beginning. This resulted in a strategy of people starting Hardcore in groups, with unofficial "leaders" guiding people through the first one or two levels. If people could keep up with the leader, they could learn where to go for the beginning levels.

In early 2011, [[Creators#HatterTheMad|HatterTheMad]] finished a lava maze, and that was quickly entered into the HC system as a replacement for the other lava themed level, lava parkour.

There was a 7 level system, HC 1.4, that existed between the 5 and 10 level system. A diagram does not exist for it yet. Like 1.3, its existence was short, and not all of the layout is known with certainty.

=== Version 2.0–2.1 ===
[[File:Hardcore 2.0.PNG|600px]]
[[File:Hardcore 2.1.PNG|600px]] 
The second version of HC was created as the earliest greens had began building maps.

Minecraft had recently transitioned from alpha to beta. The blue rank and the point system did not exist yet. The border of the map lied around the 4000 block range. This was also the time where MINR experimented with an economy. MINR was primarily a survival server at this time, instead of the semi-vanilla/creative realms that exist today.

The layout consisted of HC-1 and HC-10 being stand alone maps. For the in-between levels, players could choose 1 of 2 un-named courses at random to play. Checkpoints existed between every level, allowing easy switching between the two maps. This was later revised with 2-map segments in order to balance out the difficulty. Even with this change, some map choices were not balanced. This resulted in certain maps being picked more often, and players asking which map or path is easier in chat.

Towards the end of this iteration, an airship was constructed to house the maps that were not in Hardcore. This was later made public, and deemed the "Free For All" area, or FFA for short.

Many maps used in HC2.0 have changed in some form:
* Sra was originally a cave-maze segment known as Srenmaze.
* Blitz was originally known as Chillers' Timed Maze, and was broken for several years due to the removal of a plugin known as Falsebook.
* Stone Maze cannot be found in FFA or the Valley, and has been broken by the removal of Falsebook.
* Mineco was originally known as Void42's Jump Map.
* Heaven Parkour was broken by the removal of Falsebook, but can still be found above Hell Parkour.

=== Version 3.0–3.1 ===
[[File:Hardcore 3.0.PNG|600px]]
[[File:Hardcore 3.1.PNG|600px]] 

During this time, Minecraft was in beta, and saw its complete release in November 2011. Many concepts that now define the server were put in place during this version of HC. Most notably, FFA+ (Nov 2012) and the Blue Rank (Unknown) were launched at this time. All FFA Maps awarded one point, and the requirement to enter Hardcore was set at 5 FFA points.

This Hardcore design was in effect from August 2011 to May 2013, marking the longest period of time without a version change (21+ months) until HC 11.0 (2021-2025). This version was designed by c_dric. This version also introduced the glass boxes that are used in between levels for several versions. This version also introduced the "loop-back" mechanic, where players could play an extra map (Sky Parkour) in order to re-choose which HC4 level they wanted to play.

In Minecraft update 1.3.1, Mojang silently changed how long the player was able to breathe for. This resulted in Aquarium and Elusion becoming unplayable. At that time, admins AJDJ and Yeroc (alongside Packs as a moderator) proposed and implemented the following temporary solution:

* HC-3: Aquarium --> Wolly Mammoth
* HC-4: Wolly Mammoth --> The Face
* HC-5: Elusion --> The Big Egyptian

In one of the next updates to Minecraft this was reverted, and Aquarium was put back into the HC rotation in the 4.0 iteration.

=== Version 4.0–4.1 ===
[[File:Hardcore 4.0.PNG|600px]]
[[File:Hardcore 4.1.PNG|600px]] 

At this point in the server's history, HC 3.0 had been unchanged for a long time. Due to rampant cheating popularized by hacked clients, as well as a large influx of players completing HC3.1, the goal was to make HC much harder. With that in mind, themed segments of HC were conceived, based on the multi-pathed decisions used in HC2.0 and HC 3.0.

Many levels from HC 3.1 remain in this rotation, with an expansion of the paths being the newest feature. Another feature that returned from HC1.0 was multiple levels without checkpoints. This meant that levels 8-11 had to be completed in 1 life. This concept would be retained in subsequent iterations of Hardcore.

In summary, 4.0 has created the "legs" of hardcore that are iterated upon by almost every future version.
* Leg 1: Introduction to the different map types.
* Leg 2: Choosing a personalized path.
* Leg 3: An endurance run with no checkpoints at the end.

After this iteration was implemented, staff determined that the Path of Ice and Fire were easier than the others, so the following revisions were made in the 4.1 Patch:
*Snow Fort --> Snowstorm
*Satyrs --> Demon
*Hell Parkour --> Lava Parkour

This gave it sufficient difficulty to balance out the other paths. It's estimated that approximately 70 players completed this version of Hardcore.

This is first of several versions that AJDJ led designs for.

=== Version 5.0 ===
[[File:Hardcore 5.0.PNG|600px]] 

While designing 5.0, HC4.0-4.1 had seen most players use the fire/ice path, even after balancing. In order to remediate this, the path was removed and replaced with the path of nostalgia. This would allow players to pick an easier path, but receive no middle checkpoint. Newer maps joined this rotation, replacing a few older maps. It was around this time in the design process that those working on the HC designs shifted towards adding map-quality as one of the criteria for HC maps.

At the time, HC 5.0 was considered to be one of the hardest HC versions conceived.

Towards the end of this version of HC is where server ownership changed hands.

=== Version 6.0–6.1 ===
[[File:Hardcore 6.0.PNG|600px]]
[[File:Hardcore 6.1.PNG|600px]] 

Around this time, the server's activity had slowed significantly, and very few players had cleared HC5.0. The goal of HC6.0 was to make the overall difficulty slightly lower. This was achieved by revising the branching paths to use map type rather than theme, and lowering the number of maps in the final run.

The thematic paths were replaced with paths oriented around map types. This allowed players to lean into their strengths for a portion of HC.

Shortly after the 6.0 launch, it was determined that the puzzle path was too easy. In order to balance this out, the following changed were made for 6.1:

* Remove the puzzle path.
* Replace Paradox with Viemort.
* 154 Returns to FFA.

=== Version 7.0 ===
[[File:Hardcore 7.0.PNG|600px]] 

This version of HC heavily reworked the middle leg. The choices were now between 2 of the 3 map types, allowing players to lean on their strengths and completely avoid 1 map type if desired. Another goal of this system was to shift the layout towards persistence based maps rather than just difficult maps.

This is the last version that AJDJ lead designs for, concluding his time as the lead admin for Hardcore design (HC 4.0 through HC 7.0).

=== Version 8.0–8.1 ===
[[File:HC8.0.png|600px]]
[[File:HC8.1.png|600px]]

HC 8.0 was intended to make Hardcore longer, and have a greater focus on persistence and uniform difficulty. The iteration consisted of twelve maps, with a mix of parkour and mazes. This was also the first version of HC that had automatic transfers into the new system. Previously, there was a time period where users had to request transfer into the equivalent level of the new design.

This iteration was unique for multiple reasons:
* There were no puzzle maps on the main path.
**([[MYTH]] contains small puzzles, but isn't technically a puzzle map).
* When players reached HC-4, they could either continue along the main path (of parkour and mazes) or opt for a shorter but much harder path that consisted of puzzles only.
* One of the puzzles, Miner's Millions, was considered one of the hardest on the server. Few players completed this path.

In addition, HC8.0 introduced the two loop-back feature for switching between the two paths. [[Satyrs]] had to be completed to switch from the main path to the puzzle path, and [[Minetech]] was required to switch from the puzzle path to the main path.

This was the longest version of Hardcore upon release, however many users do not consider it to be the toughest.

Due to the gameplay changes in the Minecraft 1.14 update and low usage of the path, the puzzle path was later removed resulting in the first entirely linear structure since Hardcore's inception.

=== Version 9.0 ===
[[File:HC9.0.png|600px]]

This goals for HC9.0 included:
* Expanding the variety of map types to include adventure / puzzle maps.
* Allowing users to lean into a strength in the second leg, and receive easier maps of the types the player was aiming to avoid.
* Introducing limited food supply / regeneration as way to tune the difficulty of parkour maps.
* Reduce the number of "choke" maps (where players complete a difficult map then breeze through several levels).

The design of this version used a unique two-step approach:
1. Create the desired layout of the HC in a staff discussion, with estimated difficulty for each map slot, how the branching paths would work, etc.
2. Take the design to the greens and gather community feedback on the design and which maps would work best for each slot.

This version also featured maps that were made specifically for HC that never entered FFA.

=== Version 10.0-10.2 ===
[[File:HC10.0.png|600px]]
[[File:HC10.1.png|600px]]
[[File:Hc10.2.png|600px]]

In March 2020, the server saw a large increase in players due to the global COVID-19 pandemic changing most schools and jobs to be remote as people self-quarantined in their homes. This resulted in many players completing hardcore in March and April of that year. Staff determined that HC needed to be updated as soon as possible to account for the larger player base. While most HC designs are usually spread out over several months, HC 10.0 was designed in only four weeks, and implemented in another three weeks.

This design featured similar segments to 9.0, but changed the logic of the branching paths. Players could completely avoid one map type, but would play challenging levels that used the other two primary map types, as well as adventure maps of the corresponding types. Players could switch between the paths at any time without playing a loopback map. This version also adds a fourth section in-between the paths and the final gauntlet. It was named "The Big Three", since all 3 of the maps in that section are fairly challenging, with checkpoints between every level.

This design also saw the exit of two maps heavily used in Hardcore since their introduction in 2011:
* Lava maze returned to FFA, after having been in hardcore since 2016, and in every version of hardcore except HC 6.0.
* Elusion was retired from HC, having been replaced by a remastered version. Elusion had been in several versions of HC by this point (3.0 through 6.0 & 9.0).

This Hardcore design was led by Hex and AJDJ.

Hardcore 10.0 was later updated to 10.1 to address balance issues with the three paths. In particular, the path of Tenacity was only completed once in HC10.0. Some other adjustments were made as well including replacing Paisley Prison with Construction, and making the entire final section no-sprint. In November 2020, it was updated to 10.2 to address additional difficulty issues. Overall, HC was made slightly easier to complete. The most notable change was removing Telepads.

=== Version 11.0 - 11.1 ===
[[File:HC11.0_fix.png|800px]]
[[File:hc11.1New.png|800px]]

Hardcore 11.0's design process began around the same time that 10.0 was being designed. Many ideas that were rejected from 10.0 due to time constraints were explored as possibilities for 11.0. One of the largest goals for this version was to eliminate the split paths, and replace it with a choice section, where players had to complete a certain number of maps out of a pool in order to advance to the next section.

Design followed a similar process to 9.0, where a staff design was created and then taken to greens in order to gather feedback. This time, it also included room for new maps, where greens could build maps tuned specifically for hardcore: the entire 'Endurance' leg was built uniquely for HC 11.0 by members of the community as part of a 'HC Map-Building Competition' in which greens were asked to design maps under specific constraints that are desired in hardcore maps. Such constraints include difficulty, checkpoint layout, kill potential, length, repeatability, etc. Some maps in other legs (Aether, Persona and Fissure) were also built specifically for this rotation.

The end design resulted in the retiring of the split path leg, and the creation of 2 new legs:

*The Choice leg, where 3/4 maps must be completed to advance. Each map is of a different type, allowing users to bypass one map type.

*The Endurance leg, where you must complete several maps of similar design / kill potential, or face a single expert map to bypass. (Similar to HC8.0's split design).

Notably, this rotation saw the retirement of several 'staple' Hardcore maps such as 4 Corners Dojo, Wolly Mammoth, Invictus, The Big Egyptian and Iron Door among others. This was due to a desire to 'modernise' the Hardcore system by highlighting what modern maps have to offer.

This rotation was led by pieceofcheese.

It was later updated to Version 11.1, swapping out most of the maps in the Choice section for easier options. The Endurance leg was also made easier by sending players back to HC8 when they die in HC9, instead of back to HC7. The Magic Tower was also taken out and replaced with Framed, an easier puzzle.

=== Version 12.0 ===
[[File:hc12.png|1000px]]

The design process for HC 12.0 started in early 2023 with the objective of building on the strengths of HC 11.0 and amending specific issues with that rotation. This design was led by pieceofcheese.

HC 12.0's core design philosophy was the implementation of more randomisation in both the maps themselves and in the player's progression through HC. In previous rotations, staff had grown concerned that large groups were
progressing through puzzle and maze maps together, allowing some players to bypass challenges without having to solve (or contribute to solving) them, defeating the purpose of Hardcore itself. Large groups completing HC at the same
time also began to overwhelm the green applications system and made accurately reading logs difficult, if not impossible. Consequently, this design added several new maps with randomized features and brought back and modified
pre-existing maps to include randomization all for the purpose of splitting up groups and making answer sharing more difficult.

HC 12.0 retains mostly the same structure as HC 11.0, with some amendments. There was an effort to diversify the map types present in HC, with Search and Dropper maps being added. A new section, The Weave, was created, which forces players
to play one maze, one parkour and one puzzle, but allows the player to choose which maptype they’d like to play at the hardest, average and easiest level, varying in difficulty based on which column they are in. This change was made as
many HC11.0 players got stuck at the same points - the Weave ensures that although they still complete a map-type they may struggle with, they can choose an easier map in that category and harder difficulty maps in other categories to
compensate.

Much like HC 11.0, several new maps were constructed exclusively for this rotation and with its design requirements in mind. These include Citadel, Dancing With Devils and Nilhelm. The Gwishin, Rainbow Madhouse and Nightmare Fuel,
three pre-existing FFA maps, also saw heavy modifications in order to suit the design philosophy of the rotation. Additionally, there were minor tweaks to the difficulty and content of other pre-existing maps. Some maps purpose-built
for older HC rotations saw their retirement (and addition to FFA for the first time), including The Scorned Lands and Fissure. Several Hardcore 'veteran' maps saw a return, including Sra, Invictus, Iron Door and Sssnake.
This was due to a desire to populate HC with gameplay-focused maps (common among older maps), rather than story/aesthetic based maps. There was also a wish to greater represent the server's history within HC.

The design was originally intended to include a gauntlet of mini-maps, sourced from a HC map building competition. However due to low entries the design was amended, though Citadel, Bustlin' Bees, Freefall and Incinerate emerged from
this competition.

Notably, the implementation of HC12.0 marks the longest gap between rotations in the server's history. This was mostly due to a lack of available staff to complete the project. HC12.0 also contains the greatest number of maps total (31) and the greatest number of required maps (17) in the history of Hardcore.

==Trivia==

* The Hardcore System was released alongside the server upon launch.
* Hardcore is one of the oldest challenges in the history of Minecraft.
* The overall success rate of players making it through hardcore is less than 1%.
* Hardcore pre-dates the variant survival gamemode of the same name by over a year, as Hardcore survival launched in November 2011 in version 1.0.0.

File:HC11.0 fix.png

2025-06-30T12:13:03Z

Tetration:

Command List

2022-11-22T11:34:24Z

Tetration: Added /c by command

Commands are used on ''Zero'' to navigate the server, join maps and assist in building, among other uses. The player can execute any command granted to them by their rank, or any lower ranks.

== General Commands ==
''Note that /c and /cp are aliases of /checkpoint.
/ch is an alias of /challenge.'' 
When referencing a map, you can either use its name, or the map code (usually a three-letter abbreviated form of the map’s name, such as “aws” for “A Whittle Story” or “anh” for “ANHUR”). This can usually be found on the map's checkpoint sign.

=== General ===

==== help ====
/help
Displays help information

==== kill ====
/kill
Kills the player. They will respawn at their [[checkpoint]].

==== mail ====
/mail <player> <subject> [message]
Will send a message to a player, regardless if they are online or not. The message will be viewable at any time (until deleted).

/mail delete <number>
Will delete a message a player has received.

/mail list
Lists all of the messages a player has received.

/mail read <number>
Displays a message to the player.

==== me ====
/me <message>
/minecraft:me <message> ''(vanilla)''
Roleplaying command. Displays * playername <message> in chat.

==== message ====
/message <player> <message>
/m <player> <message> ''(alias)''
/msg <player> <message> ''(alias)''
/tell <player> <message> ''(alias)''
/whisper <player> <message> ''(alias)''
/w <player> <message> ''(alias)''
Sends a private message to a player. Multiple players can be messaged at once by separating each player name with a comma.

/minecraft:msg ''(vanilla)''
/minecraft:tell ''(vanilla)''
Uses the vanilla command to send a private message to a player.

==== note ====
An alias of [[#mail|/mail]].

==== ping ====
/ping [player]
Pings the server. The server pongs the player back. Displays the round-trip travel time for a packet between a player and the server. 
Can also be used to play ping-pong with the server.

==== reply ====
/reply <message>
/r <message> ''(alias)''
Replies to the sender of the last private message received. If last message was sent to multiple players, replies to all players.

==== spawn ====
/spawn
/hub ''(alias)''
/lobby ''(alias)''
/quit ''(alias)''
/quitmap ''(alias)''
/leave ''(alias)''
Teleports the player to [[Spawn|spawn]].

==== team ====
/tchat <message>
/teammsg <message> ''(alias)''
/t <message> ''(alias)''
Sends a message to everyone in the player's team (if they are in one).

==== whois ====
/whois [player]
Displays information about the player.

=== Party ===
These commands pertain to Minr's party system, which allows players to easily join maps together and communicate with their party.

==== accept ====
/party accept
Accepts a pending invite to a party.

==== create ====
/party create
Creates a new party. (Cannot create party while in another party)

==== disband ====
/party disband
Disbands the party. (Must be party leader to disband)

==== invite ====
/party invite <player>
Sends an invite to a player to join a party.

==== kick ====
/party kick <player>
Removes a player from your party. (Must be party leader to kick)

==== leave ====
/party leave
Leaves the player's current party.

==== list ====
/party list
Lists all players in the executor's party.

==== set allinvite/warp ====
/party set allinvite allow|disallow [default]
Allows or disallows party members sending party invites. If disallow is set, only the party leader can invite players to their party. The ''default'' keyword sets the default setting for any future parties the player creates.

/party set warp enable|disable [default]
Enables or disables warping all party members when any party member joins a map or challenge. The ''default'' keyword sets the default setting for any future parties the player creates.

(Must be party leader to change party settings)

==== summon ====
/party summon
Brings all party members to your current map.

==== transfer ====
/party transfer <player>
Transfers leadership to another party member. (Must be party leader to transfer)

=== Checkpoint and Maps===
These pertain specifically to [[Map|maps]].

==== by ====
/c by [player]
Displays a list of all the maps of which a player is a creator. If omitted, player defaults to the executor.

==== completed ====
/c completed [player <player>] [comparing <player>|party] map <map name|map code>
Checks how many times a player has completed a map, and their fastest time. If omitted, player defaults to the executor. The comparing specifier will show the completion information for an additional player or the executor's entire party.
/c completed [player <player>] [comparing <player>|party] [sortby <sort mode>] [page <number>]
Displays a list of all the maps a player has beaten, and their fastest times. If omitted, player defaults to the executor. The comparing specifier will filter the list to maps completed by both players or the executor's entire party. 
Sort mode can be one of the following:
* Alphabet – ''Default. Sorts alphabetically.''
* Points'' – ''Sorts on point value, from low to high, then alphabetically.''
* Rank'' – ''Sorts on the time rank accomplished by the player, then alphabetically.''
* Completions'' – ''Sorts on the amount of completions, from low to high, then alphabetically.''

==== cp ====
/c cp [player]
/c current [player] ''(alias)''
Displays checkpoint information about a player. If omitted, player defaults to the executor.

==== ffa ====
/c ffa
Respawns player at their ffa checkpoint.

==== info ====
/c info <map name|map code>
Displays information about a map, including the map type(s), creators, and difficulty.

==== join ====
/c join <map name|map code>
Joins a map
/c join <player>
Joins the map that a player is currently playing

==== points ====
/c points [player]
Displays the amount of [[Points|FFA Points]], [[Points|Challenge Points]], and [[Points|Global Points]] obtained by a player. If omitted, player defaults to the executor.

==== srscore ====
/c srscore <player> <map>
Displays the amount of [[Points|Speedrun Score]] a player has earned on a particular map. The higher the player’s time rank, the higher the Speedrun Score they’ll have on the map. If omitted, player defaults to the executor.

==== random ====
/c random [new]
Warps the player to a random map. If ''new'' is present, it will warp the player to a map they have not completed before.

==== restart ====
/c restart
Resets the player's progress in a map.

==== times ====
/c times [page] <map name|map code>
Displays the times for a map.

==== uncompleted ====
/c uncompleted [player <player>] [comparing <player>|party] [sortby <sort mode>] [page <number>]
Displays a list of all the maps a player has not completed. Maps that are not accessible or award no points are not included. If omitted, player defaults to the executor. The comparing specifier will filter the list to maps that are not completed by both players or the executor's entire party. 
Sort mode can be one of the following:
* Alphabet – ''Default. Sorts alphabetically.''
* Points'' – ''Sorts on point value, from low to high, then alphabetically.''
* Rank'' – ''Sorts on the time rank accomplished by the player, then alphabetically.''
* Completions'' – ''Sorts on the amount of completions, from low to high, then alphabetically.''

=== Challenge ===
These pertain specifically to [[Challenge|Challenges]].

==== completed ====
/ch completed [player <player>] [comparing <player>|party] map <map name|map code>
Checks how many times a player has completed a challenge, and their fastest time. If omitted, player defaults to the executor. The comparing specifier will show the completion information for an additional player or the executor's entire party.
/ch completed [player <player>] [comparing <player>|party] [sortby <sort mode>] [page <number>]
Displays a list of all the challenges a player has beaten, and their fastest times. If omitted, player defaults to the executor. The comparing specifier will filter the list to challenges completed by both players or the executor's entire party. 
Sort mode can be one of the following:
* Alphabet – ''Default. Sorts alphabetically.''
* Points'' – ''Sorts on point value, from low to high, then alphabetically.''
* Rank'' – ''Sorts on the time rank accomplished by the player, then alphabetically.''
* Completions'' – ''Sorts on the amount of completions, from low to high, then alphabetically.''

==== daily ====
/ch join daily
Begins the daily challenge.
/ch info [page] daily
Displays information about the currently daily challenge.

==== hexa ====
/ch hexa [player]
Displays information about a player's progress through the Hexa challenge. If player is omitted, a leaderboard for hexa stage completion is displayed instead.

==== info ====
/ch info [page] <challenge name|challenge code>
Displays information about a challenge.

==== join ====
/ch join <challenge name|challenge code>
Begins a challenge.

==== quit ====
/ch quit
Quits the current challenge.

==== random ====
/ch random
Joins a random challenge.

==== restart ====
/ch restart
Restarts a player's progress in a challenge.

==== uncompleted ====
/ch uncompleted [player <player>] [comparing <player>|party] [sortby <sort mode>] [page <number>]
Displays a list of all the challenges a player has not completed. If omitted, player defaults to the executor. The comparing specifier will filter the list to challenges that are not completed by both players or the executor's entire party. 
Sort mode can be one of the following:
* Alphabet – ''Default. Sorts alphabetically.''
* Points'' – ''Sorts on point value, from low to high, then alphabetically.''
* Rank'' – ''Sorts on the time rank accomplished by the player, then alphabetically.''
* Completions'' – ''Sorts on the amount of completions, from low to high, then alphabetically.''

== Blue Commands ==
==== hardcore ====
/c hardcore
/c hc ''(alias)''
Respawns the player at their [[Hardcore|Hardcore]] checkpoint.

== Green Commands ==
These commands are only available to greens and staff. They are used to assist in the creation of maps. 

==== bring ====
/bring <player>
Teleports a player to you who called recently. On other servers, it is commonly known as ''/tpaccept''.
Using this command will invalidate the player's timer.

==== call ====
/call <player>
Will request to teleport to any green or staff member. On other servers, it is commonly known as ''/tpa''.
Using this command will invalidate the player's timer.

==== home ====
/home [home name]
Teleports the player to their home. It will teleport them to one of their homes specified. If ''home name'' is omitted, the player will be teleported to their first home. 
Greens and Staff can have unlimited amounts of homes. 
Using this command will invalidate the player's timer.

==== listhomes ====
/listhomes
/listhome ''(alias)''
Displays all the homes the player has set.

==== listwarps ====
/listwarps
/listwarp ''(alias)''
Displays all the warps on ''Zero''.

==== sethome ====
/sethome [home name]
Sets the player's home to their current position. If ''home name'' is specified, then it will set their Home # to their current position. Homes can be set to either numbers or names.

==== warp ====
/warp <warp>
Will warp the player to a specified warp.
Using this command will invalidate the player's timer.

Points

2022-10-24T01:05:05Z

Tetration: /* Modern Style */ quadratic, not exponential

Points are the main reward on the server, obtained by completing [[Maps]] and [[Challenges]]. They are awarded at the end of both and the number awarded varies depending on their difficulty. Currently, there are three types of points.

== FFA Points ==
FFA Points, often referred to as points, are the original point type and the most commonly acknowledged. They are awarded upon completing published [[Maps]]. This, however, excludes maps residing in [[The Valley]], [[The Board]], or in [[Hardcore]].
=== Ancient Style ===
At the inception of the server, it utilized the ancient style, granting every single map a single point reward regardless of difficulty. This would lead to problems in the reward system as more maps were made, albeit at this time points had no reward incentive. This eventually transitioned into the Airship Style of points.
=== Airship Style ===
This is the longest-existing style of points, being in effect for well over half of the server's lifetime. The style divides maps into five difficulties, each rewarding points in a linear fashion. The colors and values proceeded as follows:
{| class ="wikitable"
!colspan="2"|Airship Style Points
|- style="color: blue"
|Blue
|1
|- style="color: lime"
|Green
|2
|- style="color: yellow"
|Yellow
|3
|- style="color: orange"
|Orange
|4
|- style="color: red"
|Red
|5
|}
Achieving 20 points for the first time will let you gain access to the [[Blue]] rank, and therefore [[Hardcore]] with this style. This eventually transitioned into the Modern Style with the realization that a new system needed to be developed for the drastic increase in the skill gap between new and old players.
=== Modern Style ===
This is the current style of points being used. In stark contrast to the airship style, the points vary roughly quadratically with each increment of difficulty. Likewise, it added the white and black difficulties to account for the skill gap between novices and veterans. The current colors and values proceed as follows:
{| class ="wikitable"
!colspan="2"|Modern Style Points
|- style="color: white"
|White
|1
|- style="color: blue"
|Blue
|2
|- style="color: lime"
|Green
|4
|- style="color: yellow"
|Yellow
|7
|- style="color: orange"
|Orange
|12
|- style="color: red"
|Red
|18
|- style="color: #5c687c"
|Black
|25
|}
With the change in points, the process of obtaining [[Blue]] rank modernized as well. It no longer is directly synced with entering [[Hardcore]] successfully, but occurs automatically. When Modern Style was first introduced, players needed to reach 35 points. This requirement changed and as of June 2020 the requirements are 100 points and completion of 5 [[Moderate]] or higher maps. It is no longer required to enter Hardcore to get Blue rank.

== Challenge Points ==
Challenge Points, most often shortened to C-Points, are the point type introduced with [[Challenges]]. They are awarded to the player upon the successful completion of a challenge. The amount awarded is dependent on the difficulty of the challenge.
 
Currently, there is no use for Challenge Points, but there are plans to change this in an upcoming update.
=== Daily Points ===
Recently with the push to have consistent point values with challenge difficulty, challenges increased the point rewards across the board. Along with this change came the divergence of Daily Points; it is the reward for challenges with changing maps based on time (Daily, Weekly, and Monthly Challenges).
== Speedrun Score ==
Speedrun Score is the most recent point type, catering to the speedrunning community. They are similar to FFA Points, except they are based on leaderboard placement for times on accessible maps. There is no use for these.

== Checking Points and Placement ==
For checking someone's points, the command is /c points <player>. For checking your own, ignore the <player> portion. If the player Dracula ran /c points with 2 Points, 5 "Stagnant Points," and 4 Speedrun Score, it would display like this: 
[MCP] Dracula has 2 Points (0%) (#109375). 
[MCH] Dracula has 5 (5 + 0) Challenge Points (#365). 
[MCP] Dracula has a Speedrun Score of 4 (#1137). 
The first line displays the regular Points next to the percent of total points obtained and ranking, the second displays total Challenge Points (along with the split between stagnant and daily Challenge Points) with Challenge ranking, and the final line shows the Speedrun Score along with Speedrun ranking.

Each point type has their own leaderboard ranking searchable with commands: the FFA Points one via /c ranks completion, the Challenge Points one via /ch ranks, and the Speedrun Score one via /c ranks speedrun.

== Trivia ==
*The bracketed abbreviations in the /c points command are for which part of the Minr plugin relates to them.
*Daily Points were initially calculated by subtracting the soon-to-be Stagnant Points number from challenges completed from the player's total Challenge Points. Because [[Creators#Zatharel|Zatharel]] had 12 C-Points and beat only the Welcome to Hell Challenge totaling 50 Challenge Points, he wound up with a calculated Daily Points amount of -38.
*As the result of a survey by [[Creators#Bahnarli|Bahnarli]], speedrun score calculations were changed from a dynamic score based on several map factors to the equation Score = 500 / (map rank^1.25) for each map.
*Null times in the past counted towards Speedrun Score, but as of [https://forums.minr.org/threads/11-0-39-patch-notes-2022-05-04.6409/ this update] no longer do.
*Speedrun Score was formally known as Global Points.

Command List

2022-10-24T00:53:34Z

Tetration: Fixed many old/outdated commands. Corrected the usages of certain commands. Added aliases. Added party commands.

Commands are used on ''Zero'' to navigate the server, join maps and assist in building, among other uses. The player can execute any command granted to them by their rank, or any lower ranks.

== General Commands ==
''Note that /c and /cp are aliases of /checkpoint.
/ch is an alias of /challenge.'' 
When referencing a map, you can either use its name, or the map code (usually a three-letter abbreviated form of the map’s name, such as “aws” for “A Whittle Story” or “anh” for “ANHUR”). This can usually be found on the map's checkpoint sign.

=== General ===

==== help ====
/help
Displays help information

==== kill ====
/kill
Kills the player. They will respawn at their [[checkpoint]].

==== mail ====
/mail <player> <subject> [message]
Will send a message to a player, regardless if they are online or not. The message will be viewable at any time (until deleted).

/mail delete <number>
Will delete a message a player has received.

/mail list
Lists all of the messages a player has received.

/mail read <number>
Displays a message to the player.

==== me ====
/me <message>
/minecraft:me <message> ''(vanilla)''
Roleplaying command. Displays * playername <message> in chat.

==== message ====
/message <player> <message>
/m <player> <message> ''(alias)''
/msg <player> <message> ''(alias)''
/tell <player> <message> ''(alias)''
/whisper <player> <message> ''(alias)''
/w <player> <message> ''(alias)''
Sends a private message to a player. Multiple players can be messaged at once by separating each player name with a comma.

/minecraft:msg ''(vanilla)''
/minecraft:tell ''(vanilla)''
Uses the vanilla command to send a private message to a player.

==== note ====
An alias of [[#mail|/mail]].

==== ping ====
/ping [player]
Pings the server. The server pongs the player back. Displays the round-trip travel time for a packet between a player and the server. 
Can also be used to play ping-pong with the server.

==== reply ====
/reply <message>
/r <message> ''(alias)''
Replies to the sender of the last private message received. If last message was sent to multiple players, replies to all players.

==== spawn ====
/spawn
/hub ''(alias)''
/lobby ''(alias)''
/quit ''(alias)''
/quitmap ''(alias)''
/leave ''(alias)''
Teleports the player to [[Spawn|spawn]].

==== team ====
/tchat <message>
/teammsg <message> ''(alias)''
/t <message> ''(alias)''
Sends a message to everyone in the player's team (if they are in one).

==== whois ====
/whois [player]
Displays information about the player.

=== Party ===
These commands pertain to Minr's party system, which allows players to easily join maps together and communicate with their party.

==== accept ====
/party accept
Accepts a pending invite to a party.

==== create ====
/party create
Creates a new party. (Cannot create party while in another party)

==== disband ====
/party disband
Disbands the party. (Must be party leader to disband)

==== invite ====
/party invite <player>
Sends an invite to a player to join a party.

==== kick ====
/party kick <player>
Removes a player from your party. (Must be party leader to kick)

==== leave ====
/party leave
Leaves the player's current party.

==== list ====
/party list
Lists all players in the executor's party.

==== set allinvite/warp ====
/party set allinvite allow|disallow [default]
Allows or disallows party members sending party invites. If disallow is set, only the party leader can invite players to their party. The ''default'' keyword sets the default setting for any future parties the player creates.

/party set warp enable|disable [default]
Enables or disables warping all party members when any party member joins a map or challenge. The ''default'' keyword sets the default setting for any future parties the player creates.

(Must be party leader to change party settings)

==== summon ====
/party summon
Brings all party members to your current map.

==== transfer ====
/party transfer <player>
Transfers leadership to another party member. (Must be party leader to transfer)

=== Checkpoint and Maps===
These pertain specifically to [[Map|maps]].

==== completed ====
/c completed [player <player>] [comparing <player>|party] map <map name|map code>
Checks how many times a player has completed a map, and their fastest time. If omitted, player defaults to the executor. The comparing specifier will show the completion information for an additional player or the executor's entire party.
/c completed [player <player>] [comparing <player>|party] [sortby <sort mode>] [page <number>]
Displays a list of all the maps a player has beaten, and their fastest times. If omitted, player defaults to the executor. The comparing specifier will filter the list to maps completed by both players or the executor's entire party. 
Sort mode can be one of the following:
* Alphabet – ''Default. Sorts alphabetically.''
* Points'' – ''Sorts on point value, from low to high, then alphabetically.''
* Rank'' – ''Sorts on the time rank accomplished by the player, then alphabetically.''
* Completions'' – ''Sorts on the amount of completions, from low to high, then alphabetically.''

==== cp ====
/c cp [player]
/c current [player] ''(alias)''
Displays checkpoint information about a player. If omitted, player defaults to the executor.

==== ffa ====
/c ffa
Respawns player at their ffa checkpoint.

==== info ====
/c info <map name|map code>
Displays information about a map, including the map type(s), creators, and difficulty.

==== join ====
/c join <map name|map code>
Joins a map
/c join <player>
Joins the map that a player is currently playing

==== points ====
/c points [player]
Displays the amount of [[Points|FFA Points]], [[Points|Challenge Points]], and [[Points|Global Points]] obtained by a player. If omitted, player defaults to the executor.

==== srscore ====
/c srscore <player> <map>
Displays the amount of [[Points|Speedrun Score]] a player has earned on a particular map. The higher the player’s time rank, the higher the Speedrun Score they’ll have on the map. If omitted, player defaults to the executor.

==== random ====
/c random [new]
Warps the player to a random map. If ''new'' is present, it will warp the player to a map they have not completed before.

==== restart ====
/c restart
Resets the player's progress in a map.

==== times ====
/c times [page] <map name|map code>
Displays the times for a map.

==== uncompleted ====
/c uncompleted [player <player>] [comparing <player>|party] [sortby <sort mode>] [page <number>]
Displays a list of all the maps a player has not completed. Maps that are not accessible or award no points are not included. If omitted, player defaults to the executor. The comparing specifier will filter the list to maps that are not completed by both players or the executor's entire party. 
Sort mode can be one of the following:
* Alphabet – ''Default. Sorts alphabetically.''
* Points'' – ''Sorts on point value, from low to high, then alphabetically.''
* Rank'' – ''Sorts on the time rank accomplished by the player, then alphabetically.''
* Completions'' – ''Sorts on the amount of completions, from low to high, then alphabetically.''

=== Challenge ===
These pertain specifically to [[Challenge|Challenges]].

==== completed ====
/ch completed [player <player>] [comparing <player>|party] map <map name|map code>
Checks how many times a player has completed a challenge, and their fastest time. If omitted, player defaults to the executor. The comparing specifier will show the completion information for an additional player or the executor's entire party.
/ch completed [player <player>] [comparing <player>|party] [sortby <sort mode>] [page <number>]
Displays a list of all the challenges a player has beaten, and their fastest times. If omitted, player defaults to the executor. The comparing specifier will filter the list to challenges completed by both players or the executor's entire party. 
Sort mode can be one of the following:
* Alphabet – ''Default. Sorts alphabetically.''
* Points'' – ''Sorts on point value, from low to high, then alphabetically.''
* Rank'' – ''Sorts on the time rank accomplished by the player, then alphabetically.''
* Completions'' – ''Sorts on the amount of completions, from low to high, then alphabetically.''

==== daily ====
/ch join daily
Begins the daily challenge.
/ch info [page] daily
Displays information about the currently daily challenge.

==== hexa ====
/ch hexa [player]
Displays information about a player's progress through the Hexa challenge. If player is omitted, a leaderboard for hexa stage completion is displayed instead.

==== info ====
/ch info [page] <challenge name|challenge code>
Displays information about a challenge.

==== join ====
/ch join <challenge name|challenge code>
Begins a challenge.

==== quit ====
/ch quit
Quits the current challenge.

==== random ====
/ch random
Joins a random challenge.

==== restart ====
/ch restart
Restarts a player's progress in a challenge.

==== uncompleted ====
/ch uncompleted [player <player>] [comparing <player>|party] [sortby <sort mode>] [page <number>]
Displays a list of all the challenges a player has not completed. If omitted, player defaults to the executor. The comparing specifier will filter the list to challenges that are not completed by both players or the executor's entire party. 
Sort mode can be one of the following:
* Alphabet – ''Default. Sorts alphabetically.''
* Points'' – ''Sorts on point value, from low to high, then alphabetically.''
* Rank'' – ''Sorts on the time rank accomplished by the player, then alphabetically.''
* Completions'' – ''Sorts on the amount of completions, from low to high, then alphabetically.''

== Blue Commands ==
==== hardcore ====
/c hardcore
/c hc ''(alias)''
Respawns the player at their [[Hardcore|Hardcore]] checkpoint.

== Green Commands ==
These commands are only available to greens and staff. They are used to assist in the creation of maps. 

==== bring ====
/bring <player>
Teleports a player to you who called recently. On other servers, it is commonly known as ''/tpaccept''.
Using this command will invalidate the player's timer.

==== call ====
/call <player>
Will request to teleport to any green or staff member. On other servers, it is commonly known as ''/tpa''.
Using this command will invalidate the player's timer.

==== home ====
/home [home name]
Teleports the player to their home. It will teleport them to one of their homes specified. If ''home name'' is omitted, the player will be teleported to their first home. 
Greens and Staff can have unlimited amounts of homes. 
Using this command will invalidate the player's timer.

==== listhomes ====
/listhomes
/listhome ''(alias)''
Displays all the homes the player has set.

==== listwarps ====
/listwarps
/listwarp ''(alias)''
Displays all the warps on ''Zero''.

==== sethome ====
/sethome [home name]
Sets the player's home to their current position. If ''home name'' is specified, then it will set their Home # to their current position. Homes can be set to either numbers or names.

==== warp ====
/warp <warp>
Will warp the player to a specified warp.
Using this command will invalidate the player's timer.