Instances - Revision history

Usr 40be82e7-f7d5-4548-b314-3fc7b26d22ee: formatting

2026-07-19T01:41:23Z

formatting

Usr c0fd3826-5fbd-465b-869b-142f974af714: Marked this version for translation

2026-04-28T22:38:21Z

Marked this version for translation

← Older revision		Revision as of 22:38, 28 April 2026
Line 128:		Line 128:
	A user can direct-connect to an instance if another of their own clients is already inside. The new client kicks the old one on entry, letting you switch between VR and desktop without losing your slot in a full instance.		A user can direct-connect to an instance if another of their own clients is already inside. The new client kicks the old one on entry, letting you switch between VR and desktop without losing your slot in a full instance.

	~~<!--T:312-->~~		====Avatar Performance Gated==== <!--T:312-->
	====Avatar Performance Gated====

	<!--T:313-->		<!--T:313-->

Usr c0fd3826-5fbd-465b-869b-142f974af714: remove unreleased notice for avatar performance gating

2026-04-28T22:38:09Z

remove unreleased notice for avatar performance gating

← Older revision		Revision as of 22:38, 28 April 2026
Line 130:		Line 130:
	<!--T:312-->		<!--T:312-->
	====Avatar Performance Gated====		====Avatar Performance Gated====
	~~{{Noticebox/unreleased\|{{Upcoming_inline\|2026.2.1\|docs.vrchat.com/docs/vrchat-202621-open-beta}}}}~~

	<!--T:313-->		<!--T:313-->

Usr c0fd3826-5fbd-465b-869b-142f974af714: Marked this version for translation

2026-04-11T04:10:27Z

Marked this version for translation

← Older revision		Revision as of 04:10, 11 April 2026
Line 128:		Line 128:
	A user can direct-connect to an instance if another of their own clients is already inside. The new client kicks the old one on entry, letting you switch between VR and desktop without losing your slot in a full instance.		A user can direct-connect to an instance if another of their own clients is already inside. The new client kicks the old one on entry, letting you switch between VR and desktop without losing your slot in a full instance.

			<!--T:312-->
	====Avatar Performance Gated====		====Avatar Performance Gated====
	{{Noticebox/unreleased\|{{Upcoming_inline\|2026.2.1\|docs.vrchat.com/docs/vrchat-202621-open-beta}}}}		{{Noticebox/unreleased\|{{Upcoming_inline\|2026.2.1\|docs.vrchat.com/docs/vrchat-202621-open-beta}}}}

			<!--T:313-->
	Group instances have the option to set a minimum performance limit for avatars. These limits are set on instance creation and applies to all users within the instance. The Minimum Performance Limit can be set to limit Poor, Medium, or Good avatars. The default is set to none.		Group instances have the option to set a minimum performance limit for avatars. These limits are set on instance creation and applies to all users within the instance. The Minimum Performance Limit can be set to limit Poor, Medium, or Good avatars. The default is set to none.

			<!--T:314-->
	When the limit is in effect, users violating the performance limit will be subject to:		When the limit is in effect, users violating the performance limit will be subject to:
	* Attempting to join the instance will notify the user that their avatar violates the performance limit. They will receive a warning pop-up showing their current avatar rank, the instance performance limit, and how users will see their avatar.		* Attempting to join the instance will notify the user that their avatar violates the performance limit. They will receive a warning pop-up showing their current avatar rank, the instance performance limit, and how users will see their avatar.
	* Within the instance, users will see their avatar as a [[Special:MyLanguage/Fallbacks\|Fallback]] or an [[Special:MyLanguage/Impostors\|Impostor]], but locally the user will still be in their regular avatar.		* Within the instance, users will see their avatar as a [[Special:MyLanguage/Fallbacks\|Fallback]] or an [[Special:MyLanguage/Impostors\|Impostor]], but locally the user will still be in their regular avatar.

			<!--T:315-->
	Groups can set up a role to bypass avatar performance requirements.		Groups can set up a role to bypass avatar performance requirements.

Usr c0fd3826-5fbd-465b-869b-142f974af714: Added section on upcoming avatar performance gated group instances.

2026-04-11T04:09:56Z

Added section on upcoming avatar performance gated group instances.

@@ Line 127: / Line 127: @@
 <!--T:225-->
 A user can direct-connect to an instance if another of their own clients is already inside. The new client kicks the old one on entry, letting you switch between VR and desktop without losing your slot in a full instance.
 ==Regions== <!--T:226-->

Usr c0fd3826-5fbd-465b-869b-142f974af714: Marked this version for translation

2026-04-07T00:38:19Z

Marked this version for translation

← Older revision		Revision as of 00:38, 7 April 2026
Line 280:		Line 280:
	\|-		\|-
	\|\|<translate><!--T:304--> Maximum Capacity</translate>		\|\|<translate><!--T:304--> Maximum Capacity</translate>
	\|\|<translate><!--T:305--> The configured maximum capacity value. Once the maximum capacity is reached, users will be unable to join the instance. If the instance is owned by a group, users may join a Queue if activated. The Maximum Capacity cannot be set higher than 80.</translate><ref name="CapNote" group="note"><translate> While the Maximum Capacity of a world cannot be set higher than 80 under normal circumstances, VRChat staff can manually increase the instance capacity. This usually occurs during events or [https://vrc.group/MAXCAP.0000 instance capacity stress tests]. </translate></ref>		\|\|<translate><!--T:305--> The configured maximum capacity value. Once the maximum capacity is reached, users will be unable to join the instance. If the instance is owned by a group, users may join a Queue if activated. The Maximum Capacity cannot be set higher than 80.</translate><ref name="CapNote" group="note"><translate> <!--T:311--> While the Maximum Capacity of a world cannot be set higher than 80 under normal circumstances, VRChat staff can manually increase the instance capacity. This usually occurs during events or [https://vrc.group/MAXCAP.0000 instance capacity stress tests]. </translate></ref>
	\|-		\|-
	\|\|<translate><!--T:306--> Instance creator or group owner</translate>		\|\|<translate><!--T:306--> Instance creator or group owner</translate>

Usr c0fd3826-5fbd-465b-869b-142f974af714: translation fix

2026-04-07T00:38:00Z

translation fix

← Older revision		Revision as of 00:38, 7 April 2026
Line 290:		Line 290:
	<translate>		<translate>
	<!--T:310-->		<!--T:310-->
	The maximum configurable capacity on the VRChat website is 80, resulting in an effective maximum of 82 players in normal conditions. If the instance creator or world author is already in the instance, their reserved slot is occupied and cannot be used by other players to exceed the maximum capacity. <ref group="note" name="CapNote"></ref>		The maximum configurable capacity on the VRChat website is 80, resulting in an effective maximum of 82 players in normal conditions. If the instance creator or world author is already in the instance, their reserved slot is occupied and cannot be used by other players to exceed the maximum capacity.</translate> <ref group="note" name="CapNote"></ref>
	<references group="note" />		<references group="note" />
			<translate>

	== Instance duration and automatic resets == <!--T:287-->		== Instance duration and automatic resets == <!--T:287-->

Usr c0fd3826-5fbd-465b-869b-142f974af714: /* Instance capacity */ More corrections

2026-04-07T00:36:22Z

Instance capacity: More corrections

← Older revision		Revision as of 00:36, 7 April 2026
Line 131:		Line 131:

	<!--T:227-->		<!--T:227-->
	Whilst selecting an instance type, there are choices for varying regions to better optimize their experience. Choosing an instance closest to your location will see a decrease in [[Special:MyLanguage/:Community:Terminology#Ping\|ping]], and ensuring a more stable connection to the instance, preventing disconnections and lag.		Whilst selecting an instance type, there are choices for varying regions to better optimize their experience. Choosing an instance closest to your location will see a decrease in [[Special:MyLanguage/Community:Terminology#Ping\|ping]], and ensuring a more stable connection to the instance, preventing disconnections and lag.

	<!--T:228-->		<!--T:228-->
Line 270:		Line 270:

	<!--T:299-->		<!--T:299-->
	The ~~'''Capacity'''~~ of a world can be configured on the VRChat website without reuploading the world. However, the capacity value does not represent the absolute maximum number of players that can be in an instance. The effective maximum is calculated as follows:		The capacity of a world can be configured on the VRChat website without reuploading the world. However, the capacity value does not represent the absolute maximum number of players that can be in an instance. The effective maximum is calculated as follows:
	</translate>		</translate>
	{\| class="wikitable"		{\| class="wikitable"
Line 277:		Line 277:
	\|-		\|-
	\|\| <translate><!--T:302--> Recommended Capacity</translate>		\|\| <translate><!--T:302--> Recommended Capacity</translate>
	\|\|<translate><!--T:303--> The configured recommended capacity value. Once the current user count reaches this value, the instance is no longer listed publicly.</translate>		\|\|<translate><!--T:303--> The configured recommended capacity value. Once the current user count reaches this value, the instance is no longer listed publicly. The Recommended Capacity cannot be set higher than Maximum Capacity.</translate>
	\|-		\|-
	\|\|<translate><!--T:304--> Maximum Capacity</translate>		\|\|<translate><!--T:304--> Maximum Capacity</translate>
	\|\|<translate><!--T:305--> The configured maximum capacity value. Once the maximum capacity is reached, users will be unable to join the instance. If the instance is owned by a group, users may join a Queue if activated.</translate>		\|\|<translate><!--T:305--> The configured maximum capacity value. Once the maximum capacity is reached, users will be unable to join the instance. If the instance is owned by a group, users may join a Queue if activated. The Maximum Capacity cannot be set higher than 80.</translate><ref name="CapNote" group="note"><translate> While the Maximum Capacity of a world cannot be set higher than 80 under normal circumstances, VRChat staff can manually increase the instance capacity. This usually occurs during events or [https://vrc.group/MAXCAP.0000 instance capacity stress tests]. </translate></ref>
	\|-		\|-
	\|\|<translate><!--T:306--> +1 Instance creator or group owner</translate>		\|\|<translate><!--T:306--> Instance creator or group owner</translate>
	\|\|<translate><!--T:307--> The user who created the instance can always join, even if the instance is at its ~~recommended cap~~. For Group, Group+, and Group Public instances, this reserved slot belongs to the group owner instead.</translate>		\|\|<translate><!--T:307--> The user who created the instance can always join, even if the instance is at its maximum capacity. For Group, Group+, and Group Public instances, this reserved slot belongs to the group owner instead.</translate>
	\|-		\|-
	\|\|<translate><!--T:308--> +1 World author</translate>		\|\|<translate><!--T:308--> World author</translate>
	\|\|<translate><!--T:309--> The user who uploaded the world can always join, even if the instance is at its ~~max~~ cap.</translate>		\|\|<translate><!--T:309--> The user who uploaded the world can always join, even if the instance is at its maximum cap.</translate>
	\|}		\|}
	<translate>		<translate>
	<!--T:310-->		<!--T:310-->
	The maximum configurable capacity on the VRChat website is 40, resulting in an effective maximum of 82 players in normal conditions ~~(40 × 2 + 1 + 1)~~. If the instance creator or world author is already in the instance, their reserved slot is occupied and cannot be used by other players to exceed the ~~soft cap~~.		The maximum configurable capacity on the VRChat website is 80, resulting in an effective maximum of 82 players in normal conditions. If the instance creator or world author is already in the instance, their reserved slot is occupied and cannot be used by other players to exceed the maximum capacity. <ref group="note" name="CapNote"></ref>
			<references group="note" />

	== Instance duration and automatic resets == <!--T:287-->		== Instance duration and automatic resets == <!--T:287-->

Usr adbb8876-cc64-48a6-adf5-8ee651bc98f4: Marked this version for translation

2026-04-06T21:12:39Z

Marked this version for translation

← Older revision		Revision as of 21:12, 6 April 2026
Line 172:		Line 172:
	Instance naming within the client is [[Special:MyLanguage/VRC+\|VRC+]] feature, although naming an instance through the API does not require VRC+.		Instance naming within the client is [[Special:MyLanguage/VRC+\|VRC+]] feature, although naming an instance through the API does not require VRC+.

	== Short links ==		== Short links == <!--T:296-->

			<!--T:297-->
	Instances can be shared using VRChat's <code>vrch.at</code> short link domain combined with the instance's short name, for example <code><nowiki>https://vrch.at/<shortName></nowiki></code>. This redirects to the instance's launch page on the VRChat website.		Instances can be shared using VRChat's <code>vrch.at</code> short link domain combined with the instance's short name, for example <code><nowiki>https://vrch.at/<shortName></nowiki></code>. This redirects to the instance's launch page on the VRChat website.

Line 266:		Line 267:
	\|}		\|}
	<translate>		<translate>
	== Instance capacity ==		== Instance capacity == <!--T:298-->

			<!--T:299-->
	The '''Capacity''' of a world can be configured on the VRChat website without reuploading the world. However, the capacity value does not represent the absolute maximum number of players that can be in an instance. The effective maximum is calculated as follows:		The '''Capacity''' of a world can be configured on the VRChat website without reuploading the world. However, the capacity value does not represent the absolute maximum number of players that can be in an instance. The effective maximum is calculated as follows:
	</translate>		</translate>
	{\| class="wikitable"		{\| class="wikitable"
	!<translate>Component</translate>		!<translate><!--T:300--> Component</translate>
	! <translate>Description</translate>		! <translate><!--T:301--> Description</translate>
	\|-		\|-
	\|\| <translate>Recommended Capacity</translate>		\|\| <translate><!--T:302--> Recommended Capacity</translate>
	\|\|<translate>The configured recommended capacity value. Once the current user count reaches this value, the instance is no longer listed publicly.</translate>		\|\|<translate><!--T:303--> The configured recommended capacity value. Once the current user count reaches this value, the instance is no longer listed publicly.</translate>
	\|-		\|-
	\|\|<translate>Maximum Capacity</translate>		\|\|<translate><!--T:304--> Maximum Capacity</translate>
	\|\|<translate>The configured maximum capacity value. Once the maximum capacity is reached, users will be unable to join the instance. If the instance is owned by a group, users may join a Queue if activated.</translate>		\|\|<translate><!--T:305--> The configured maximum capacity value. Once the maximum capacity is reached, users will be unable to join the instance. If the instance is owned by a group, users may join a Queue if activated.</translate>
	\|-		\|-
	\|\|<translate>+1 Instance creator or group owner</translate>		\|\|<translate><!--T:306--> +1 Instance creator or group owner</translate>
	\|\|<translate>The user who created the instance can always join, even if the instance is at its recommended cap. For Group, Group+, and Group Public instances, this reserved slot belongs to the group owner instead.</translate>		\|\|<translate><!--T:307--> The user who created the instance can always join, even if the instance is at its recommended cap. For Group, Group+, and Group Public instances, this reserved slot belongs to the group owner instead.</translate>
	\|-		\|-
	\|\|<translate>+1 World author</translate>		\|\|<translate><!--T:308--> +1 World author</translate>
	\|\|<translate>The user who uploaded the world can always join, even if the instance is at its max cap.</translate>		\|\|<translate><!--T:309--> The user who uploaded the world can always join, even if the instance is at its max cap.</translate>
	\|}		\|}
	<translate>		<translate>
			<!--T:310-->
	The maximum configurable capacity on the VRChat website is 40, resulting in an effective maximum of 82 players in normal conditions (40 × 2 + 1 + 1). If the instance creator or world author is already in the instance, their reserved slot is occupied and cannot be used by other players to exceed the soft cap.		The maximum configurable capacity on the VRChat website is 40, resulting in an effective maximum of 82 players in normal conditions (40 × 2 + 1 + 1). If the instance creator or world author is already in the instance, their reserved slot is occupied and cannot be used by other players to exceed the soft cap.

Usr adbb8876-cc64-48a6-adf5-8ee651bc98f4: prepared table for translation

2026-04-06T21:12:15Z

prepared table for translation

← Older revision		Revision as of 21:12, 6 April 2026
Line 265:		Line 265:
	\|✔️		\|✔️
	\|}		\|}
			<translate>
	== Instance capacity ==		== Instance capacity ==

	The '''Capacity''' of a world can be configured on the VRChat website without reuploading the world. However, the capacity value does not represent the absolute maximum number of players that can be in an instance. The effective maximum is calculated as follows:		The '''Capacity''' of a world can be configured on the VRChat website without reuploading the world. However, the capacity value does not represent the absolute maximum number of players that can be in an instance. The effective maximum is calculated as follows:
			</translate>
	{\| class="wikitable"		{\| class="wikitable"
	! Component		!<translate>Component</translate>
	! Description		! <translate>Description</translate>
	\|-		\|-
	\|\| Recommended Capacity		\|\| <translate>Recommended Capacity</translate>
	\|\| The configured recommended capacity value. Once the current user count reaches this value, the instance is no longer listed publicly.		\|\|<translate>The configured recommended capacity value. Once the current user count reaches this value, the instance is no longer listed publicly.</translate>
	\|-		\|-
	\|\| Maximum Capacity		\|\|<translate>Maximum Capacity</translate>
	\|\| The configured maximum capacity value. Once the maximum capacity is reached, users will be unable to join the instance. If the instance is owned by a group, users may join a Queue if activated.		\|\|<translate>The configured maximum capacity value. Once the maximum capacity is reached, users will be unable to join the instance. If the instance is owned by a group, users may join a Queue if activated.</translate>
	\|-		\|-
	\|\| +1 Instance creator or group owner		\|\|<translate>+1 Instance creator or group owner</translate>
	\|\| The user who created the instance can always join, even if the instance is at its recommended cap. For Group, Group+, and Group Public instances, this reserved slot belongs to the group owner instead.		\|\|<translate>The user who created the instance can always join, even if the instance is at its recommended cap. For Group, Group+, and Group Public instances, this reserved slot belongs to the group owner instead.</translate>
	\|-		\|-
	\|\| +1 World author		\|\|<translate>+1 World author</translate>
	\|\| The user who uploaded the world can always join, even if the instance is at its max cap.		\|\|<translate>The user who uploaded the world can always join, even if the instance is at its max cap.</translate>
	\|}		\|}
			<translate>
	The maximum configurable capacity on the VRChat website is 40, resulting in an effective maximum of 82 players in normal conditions (40 × 2 + 1 + 1). If the instance creator or world author is already in the instance, their reserved slot is occupied and cannot be used by other players to exceed the soft cap.		The maximum configurable capacity on the VRChat website is 40, resulting in an effective maximum of 82 players in normal conditions (40 × 2 + 1 + 1). If the instance creator or world author is already in the instance, their reserved slot is occupied and cannot be used by other players to exceed the soft cap.

	~~<translate>~~
	== Instance duration and automatic resets == <!--T:287-->		== Instance duration and automatic resets == <!--T:287-->