From 71e08f8104d859da640917f45874a751139b594f Mon Sep 17 00:00:00 2001 From: FrenchFox1 Date: Mon, 11 May 2026 12:51:37 +0200 Subject: [PATCH] Update user.mdx The "System_no_captcha" is a tag that allows a user to join an instance even if the max capacity is reached. I am unsure if the way I wrote it is clear, so feel free to modify it --- content/docs/(guides)/tags/user.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/content/docs/(guides)/tags/user.mdx b/content/docs/(guides)/tags/user.mdx index f195cfb..b200ccc 100644 --- a/content/docs/(guides)/tags/user.mdx +++ b/content/docs/(guides)/tags/user.mdx @@ -33,6 +33,7 @@ description: Trust ranks, access to features, and other metadata about users. | `system_trust_legend` | User is "Veteran User" (gold color) Trust rank
(Role was removed in Sep 2018. Tag removed in 2022-05-05) | | `system_world_access` | User can upload and publish Worlds | | `system_vital_test_user_do_not_delete` | User should not be deleted as it is vital for testing or other internal systems
(Tag was visible briefly on 2025-09-29 and removed on 2025-09-30) | +| `system_no_captcha` | User can bypass the instance max capacity Trust rank tags have an offset of 1 with their name, so `system_trust_trusted` is actually only `Known User` (orange). The arrows in the following picture highlight the offset naming inaccuracy. The naming system is because of legacy reasons. Visistors have no trust rank at all. It is common for people User and above to be missing the tag for New User.