Special Commands - Revision history

codex: Document dense cloud activity controls and separate cloud/fog illumination test; clarify BOLT requirements

2026-11-08T21:41:10Z

Document dense cloud activity controls and separate cloud/fog illumination test; clarify BOLT requirements

← Older revision		Revision as of 21:41, 8 November 2026
Line 133:		Line 133:

	'''000COMMANDBCLX.XXX'''		'''000COMMANDBCLX.XXX'''
	Sets the cloud ~~bases~~ in ~~kilometers~~ AGL (-1 to ~~reset~~, 0 is ~~on ground level~~, 1.~~5 would be 1500 meters~~)		Sets the local cloud ceiling in kilometres AGL, from 0 to 10. Decimals use a dot: <code>000COMMANDBCL0.125</code> selects 125 metres; <code>000COMMANDBCL0</code> selects ground level; <code>000COMMANDBCL-1</code> restores live weather. The override follows local terrain in the cloud and fog weather grids. It does not apply a new server visibility cap.

			'''000COMMANDCLOUDACTvalue''' and '''000COMMANDCLOUDACT-1'''

			Administrator-only, client-local cloud activity control. Enter a value from 0 to 1 directly after the prefix, for example <code>000COMMANDCLOUDACT0.6</code> for dense-cloud testing. The value changes cloud activity while retaining the normal cloud and fog paths; it is not an opacity percentage and does not guarantee that every location is inside a cloud. Wind, precipitation and visibility continue to follow their existing controls.

			For a low-cloud test, enter <code>000COMMANDVIS-1</code>, <code>000COMMANDCLOUDACT0.6</code>, then <code>000COMMANDBCL0.125</code> (or another desired ceiling). Keep VIS at -1 to retain spatial weather fog; an explicit VIS override selects uniform test visibility. Loaded local weather and terrain are still required.

			Use <code>000COMMANDCLOUDACT-1</code> and <code>000COMMANDBCL-1</code> independently to restore live activity and ceiling. Live weather continues updating during the test. Activity override is disabled and cleared in the simulator and also ends on client restart. Invalid values leave the prior setting unchanged. These local controls do not change other players' weather.


Line 181:		Line 189:


	'''000COMMANDBOLT'''		'''000COMMANDBOLT'''

			Administrator-only connected lightning test. The local strike ends at terrain about 1 km ahead along the camera's horizontal bearing, with full diagnostic intensity and a randomized connected chain. It requires a loaded local weather grid, terrain at the target and a positive ceiling below the cloud top. It is unavailable in the simulator, windowless interiors or above the nominal cloud deck. The local Communications history and client log report acceptance or the reason for rejection. The event ends automatically.

			At zero ceiling there is no exposed cloud-to-ground channel, so BOLT rejects the event, including its illumination. Use the separate illumination test below to test cloud and fog lighting at zero ceiling.

			'''000COMMANDBOLTLIGHT''' and '''000COMMANDBOLTLIGHT0'''

			Administrator-only, client-local cloud/fog illumination test. <code>000COMMANDBOLTLIGHT</code> starts one brief flash at the same target bearing, using a repeatable pulse. It produces no bolt mesh, afterimage, thunder, damage or server event, and does not light terrain/building materials or cockpit surfaces. It works with zero ceiling as well as a positive ceiling. A simultaneous real strike takes priority over the test light.

	~~A bolt of lightning 50% intensity~~ and ~~between 0 km~~ and ~~64 km distant (average of 16 km)~~		It requires the volumetric cloud renderer, current local weather and terrain, a view outside windowless interiors, and a position below the nominal cloud deck. It is disabled in the simulator. The flash expires automatically; <code>000COMMANDBOLTLIGHT0</code> cancels it immediately. Simulator entry, missing weather, reconnect and renderer reset clear it. Status and rejection reasons appear in local Communications history and the client log. Keep the camera and weather controls steady when comparing this test with BOLT.

codex: /* Ground-wash surface preview */ Describe mineral and pavement clouds and LF1/LF33 steam

2026-10-29T23:38:34Z

Ground-wash surface preview: Describe mineral and pavement clouds and LF1/LF33 steam

codex: Describe outward cloud waves and fine blowing snow in ground wash

2026-10-29T22:19:31Z

Describe outward cloud waves and fine blowing snow in ground wash

← Older revision		Revision as of 22:19, 29 October 2026
Line 233:		Line 233:
	Values 0 through 31 select the existing landform classifications; 32 through 34 are preview presets, not additional terrain IDs. The dry presets ignore local wetness, snow, roads and roofs for the ground-wash comparison. Other visible weather continues normally. Only the dust/spray material changes: terrain textures, terrain height, collisions, traction and other players are unaffected.		Values 0 through 31 select the existing landform classifications; 32 through 34 are preview presets, not additional terrain IDs. The dry presets ignore local wetness, snow, roads and roofs for the ground-wash comparison. Other visible weather continues normally. Only the dust/spray material changes: terrain textures, terrain height, collisions, traction and other players are unaffected.

	Each selection or reset clears the previous dust/spray cloud. The effect still requires actual engine output and a plume that reaches the local ground; it does not force emission from idle engines, in space, in interiors or in unsupported vehicles. Height, thrust direction and surface wind continue to control the wash. The preview uses the normal bounded ground-wash model. Dry snow and loose sand/dirt can form dense ~~clouds~~ that obscure the surroundings; it does not simulate erosion or change vehicle performance. See [[VTOL#Near-surface effects\|near-surface effects]] for the normal limits.		Each selection or reset clears the previous dust/spray cloud. The effect still requires actual engine output and a plume that reaches the local ground; it does not force emission from idle engines, in space, in interiors or in unsupported vehicles. Height, thrust direction and surface wind continue to control the wash. The preview uses the normal bounded ground-wash model. Dry snow and loose sand/dirt can form outward-moving waves of dense cloud that obscure the surroundings, with blowing flakes over snow; it does not simulate erosion or change vehicle performance. See [[VTOL#Near-surface effects\|near-surface effects]] for the normal limits.

	An active vehicle outside the in-world simulator is required. Simulator entry clears the preview, and leaving the simulator does not restore it. Changing vehicles, becoming inactive, losing administrator access, a graphics-device reset or restarting the client also clears it. Use <code>000COMMANDLF-1</code> to stop manually.		An active vehicle outside the in-world simulator is required. Simulator entry clears the preview, and leaving the simulator does not restore it. Changing vehicles, becoming inactive, losing administrator access, a graphics-device reset or restarting the client also clears it. Use <code>000COMMANDLF-1</code> to stop manually.

	The prefix is case-insensitive. Use ordinary decimal digits, or exactly <code>-1</code> to reset; fractions, plus signs, exponent notation, extra parameters and values outside the listed range are rejected without changing the current selection. Accepted selections and resets appear in the local Communications history as the command you entered. Detailed command status, rejection reasons and usage guidance appear in the client log. The command is handled locally and is not sent to other players or the server.		The prefix is case-insensitive. Use ordinary decimal digits, or exactly <code>-1</code> to reset; fractions, plus signs, exponent notation, extra parameters and values outside the listed range are rejected without changing the current selection. Accepted selections and resets appear in the local Communications history as the command you entered. Detailed command status, rejection reasons and usage guidance appear in the client log. The command is handled locally and is not sent to other players or the server.

codex: Clarify local Communications history for accepted ground-wash preview commands

2026-10-29T21:52:48Z

Clarify local Communications history for accepted ground-wash preview commands

← Older revision		Revision as of 21:52, 29 October 2026
Line 237:		Line 237:
	An active vehicle outside the in-world simulator is required. Simulator entry clears the preview, and leaving the simulator does not restore it. Changing vehicles, becoming inactive, losing administrator access, a graphics-device reset or restarting the client also clears it. Use <code>000COMMANDLF-1</code> to stop manually.		An active vehicle outside the in-world simulator is required. Simulator entry clears the preview, and leaving the simulator does not restore it. Changing vehicles, becoming inactive, losing administrator access, a graphics-device reset or restarting the client also clears it. Use <code>000COMMANDLF-1</code> to stop manually.

	The prefix is case-insensitive. Use ordinary decimal digits, or exactly <code>-1</code> to reset; fractions, plus signs, exponent notation, extra parameters and values outside the listed range are rejected without changing the current selection. ~~Command~~ status, rejection reasons and usage guidance appear in the client log. The command is handled locally and is not sent to other players or the server.		The prefix is case-insensitive. Use ordinary decimal digits, or exactly <code>-1</code> to reset; fractions, plus signs, exponent notation, extra parameters and values outside the listed range are rejected without changing the current selection. Accepted selections and resets appear in the local Communications history as the command you entered. Detailed command status, rejection reasons and usage guidance appear in the client log. The command is handled locally and is not sent to other players or the server.

codex: Describe dense snow and loose-dirt ground wash, visibility loss and lingering clouds

2026-10-29T18:32:37Z

Describe dense snow and loose-dirt ground wash, visibility loss and lingering clouds

← Older revision		Revision as of 18:32, 29 October 2026
Line 233:		Line 233:
	Values 0 through 31 select the existing landform classifications; 32 through 34 are preview presets, not additional terrain IDs. The dry presets ignore local wetness, snow, roads and roofs for the ground-wash comparison. Other visible weather continues normally. Only the dust/spray material changes: terrain textures, terrain height, collisions, traction and other players are unaffected.		Values 0 through 31 select the existing landform classifications; 32 through 34 are preview presets, not additional terrain IDs. The dry presets ignore local wetness, snow, roads and roofs for the ground-wash comparison. Other visible weather continues normally. Only the dust/spray material changes: terrain textures, terrain height, collisions, traction and other players are unaffected.

	Each selection or reset clears the previous dust/spray cloud. The effect still requires actual engine output and a plume that reaches the local ground; it does not force emission from idle engines, in space, in interiors or in unsupported vehicles. Height, thrust direction and surface wind continue to control the wash. ~~This command~~ does not ~~increase the particle budget~~ or ~~simulate a full volumetric dust cloud~~. See [[VTOL#Near-surface effects\|near-surface effects]] for the normal limits.		Each selection or reset clears the previous dust/spray cloud. The effect still requires actual engine output and a plume that reaches the local ground; it does not force emission from idle engines, in space, in interiors or in unsupported vehicles. Height, thrust direction and surface wind continue to control the wash. The preview uses the normal bounded ground-wash model. Dry snow and loose sand/dirt can form dense clouds that obscure the surroundings; it does not simulate erosion or change vehicle performance. See [[VTOL#Near-surface effects\|near-surface effects]] for the normal limits.

	An active vehicle outside the in-world simulator is required. Simulator entry clears the preview, and leaving the simulator does not restore it. Changing vehicles, becoming inactive, losing administrator access, a graphics-device reset or restarting the client also clears it. Use <code>000COMMANDLF-1</code> to stop manually.		An active vehicle outside the in-world simulator is required. Simulator entry clears the preview, and leaving the simulator does not restore it. Changing vehicles, becoming inactive, losing administrator access, a graphics-device reset or restarting the client also clears it. Use <code>000COMMANDLF-1</code> to stop manually.

	The prefix is case-insensitive. Use ordinary decimal digits, or exactly <code>-1</code> to reset; fractions, plus signs, exponent notation, extra parameters and values outside the listed range are rejected without changing the current selection. Command status, rejection reasons and usage guidance appear in the client log. The command is handled locally and is not sent to other players or the server.		The prefix is case-insensitive. Use ordinary decimal digits, or exactly <code>-1</code> to reset; fractions, plus signs, exponent notation, extra parameters and values outside the listed range are rejected without changing the current selection. Command status, rejection reasons and usage guidance appear in the client log. The command is handled locally and is not sent to other players or the server.

codex: Document admin-only local ground-wash landform preview and reset

2026-10-29T14:46:24Z

Document admin-only local ground-wash landform preview and reset

← Older revision		Revision as of 14:46, 29 October 2026
Line 205:		Line 205:

	Temporarily toggles whether the current vehicle is equipped with [[Night Vision Goggles]]		Temporarily toggles whether the current vehicle is equipped with [[Night Vision Goggles]]


			===Ground-wash surface preview===

			'''<nowiki>000COMMANDLF<number></nowiki>''' and '''000COMMANDLF-1'''

			Administrator-only, client-local [[VTOL#Near-surface effects\|ground-wash]] material preview (updated client required). Enter a whole number immediately after <code>000COMMANDLF</code> to compare surface effects without moving the vehicle:

			{\| class="wikitable"
			! Command !! Preview
			\|-
			\| <code>000COMMANDLF0</code> or <code>000COMMANDLF10</code> \|\| Dry loose sand/dirt
			\|-
			\| <code>000COMMANDLF1</code> \|\| Open-water spray
			\|-
			\| <code>000COMMANDLF2</code> through <code>000COMMANDLF31</code>, except 10 \|\| Dry mineral dust
			\|-
			\| <code>000COMMANDLF32</code> \|\| Dry pavement/road dust
			\|-
			\| <code>000COMMANDLF33</code> \|\| Wet-ground mist
			\|-
			\| <code>000COMMANDLF34</code> \|\| Snow aerosol
			\|-
			\| <code>000COMMANDLF-1</code> \|\| Restore the current live surface, wetness and snow
			\|}

			Values 0 through 31 select the existing landform classifications; 32 through 34 are preview presets, not additional terrain IDs. The dry presets ignore local wetness, snow, roads and roofs for the ground-wash comparison. Other visible weather continues normally. Only the dust/spray material changes: terrain textures, terrain height, collisions, traction and other players are unaffected.

			Each selection or reset clears the previous dust/spray cloud. The effect still requires actual engine output and a plume that reaches the local ground; it does not force emission from idle engines, in space, in interiors or in unsupported vehicles. Height, thrust direction and surface wind continue to control the wash. This command does not increase the particle budget or simulate a full volumetric dust cloud. See [[VTOL#Near-surface effects\|near-surface effects]] for the normal limits.

			An active vehicle outside the in-world simulator is required. Simulator entry clears the preview, and leaving the simulator does not restore it. Changing vehicles, becoming inactive, losing administrator access, a graphics-device reset or restarting the client also clears it. Use <code>000COMMANDLF-1</code> to stop manually.

			The prefix is case-insensitive. Use ordinary decimal digits, or exactly <code>-1</code> to reset; fractions, plus signs, exponent notation, extra parameters and values outside the listed range are rejected without changing the current selection. Command status, rejection reasons and usage guidance appear in the client log. The command is handled locally and is not sent to other players or the server.

codex: Explain effective test-loading weights in the cargo manifest

2026-10-28T13:18:09Z

Explain effective test-loading weights in the cargo manifest

← Older revision		Revision as of 13:18, 28 October 2026
Line 29:		Line 29:

	For example, a vehicle with an empty weight of 6,000 lb and a maximum gross weight of 10,000 lb receives 9,000 lb of fuel plus payload with '''000WEIGHT150''', giving 15,000 lb gross. '''000WEIGHT200''' loads 14,000 lb of fuel plus payload, giving 20,000 lb gross. These targets exclude additional modeled weight such as accumulated ice, which is still added separately by the flight model. Use an updated client for this maximum-gross percentage behavior; older clients apply the percentage only to the fuel-and-payload allowance.		For example, a vehicle with an empty weight of 6,000 lb and a maximum gross weight of 10,000 lb receives 9,000 lb of fuel plus payload with '''000WEIGHT150''', giving 15,000 lb gross. '''000WEIGHT200''' loads 14,000 lb of fuel plus payload, giving 20,000 lb gross. These targets exclude additional modeled weight such as accumulated ice, which is still added separately by the flight model. Use an updated client for this maximum-gross percentage behavior; older clients apply the percentage only to the fuel-and-payload allowance.

			During a loading test, the [[Manifest]] shows a signed '''Test Adjust''' row and marks '''Total Weight''' with '''OVERRIDE'''. Total Weight includes the current fuel, overridden payload and modeled ice used by the flight model; an Ice Weight row appears when applicable. Cargo-bay entries still describe actual contents. The adjustment is simulated loading and cannot be unloaded or transferred. These indicators disappear when the loading test ends. Use an updated client to see the override weight in the manifest.

	The percentage command adjusts loading once; fuel continues to burn. '''000WEIGHT100''' requests maximum-gross loading and '''000WEIGHT0''' requests minimum test loading.		The percentage command adjusts loading once; fuel continues to burn. '''000WEIGHT100''' requests maximum-gross loading and '''000WEIGHT0''' requests minimum test loading.

codex: Describe WEIGHT percentages of maximum gross weight and minimum loading

2026-10-28T03:37:53Z

Describe WEIGHT percentages of maximum gross weight and minimum loading

← Older revision		Revision as of 03:37, 28 October 2026
Line 15:		Line 15:
	Enter a non-negative whole-number percentage directly after the command, without a percent sign, for example '''000WEIGHT125'''. '''Values above 100 are supported''' and allow overweight testing. Use ordinary decimal digits without leading zeros in the percentage; fractional percentages are not supported.		Enter a non-negative whole-number percentage directly after the command, without a percent sign, for example '''000WEIGHT125'''. '''Values above 100 are supported''' and allow overweight testing. Use ordinary decimal digits without leading zeros in the percentage; fractional percentages are not supported.

	The percentage applies to ~~the normal fuel-and-payload allowance:~~ '''maximum gross weight ~~minus~~ empty weight'''. The requested load is:		The percentage applies to '''maximum gross weight, including empty weight'''. The target gross weight and requested fuel-and-payload load are:

	:<code>(~~maximum~~ gross weight - empty weight) * percent / 100</code>		:<code>target gross weight = maximum gross weight * percent / 100</code>
			:<code>fuel + payload = max(2% of tank capacity, target gross weight - empty weight)</code>

	Fuel is filled first, up to tank capacity, and any remaining load becomes payload. A percentage loading request never sets fuel below 2% of tank capacity. ~~The extra load~~ above 100~~% is~~ not capped at maximum gross weight.		Fuel is filled first, up to tank capacity, and any remaining load becomes payload. A percentage loading request never sets fuel below 2% of tank capacity or removes empty weight. If the requested gross weight is below empty weight plus that minimum fuel, the result is zero payload and 2% fuel. Values above 100 are not capped at maximum gross weight.

	* '''000WEIGHT0''': zero payload and 2% fuel; slightly above empty weight.		* '''000WEIGHT0''': zero payload and 2% fuel; slightly above empty weight.
	* '''000WEIGHT50''': ~~half the normal fuel-and-payload allowance~~, subject to the minimum fuel load.		* '''000WEIGHT50''': 50% of maximum gross weight, subject to empty weight plus the minimum fuel load.
	* '''000WEIGHT100''': ~~the normal~~ maximum-gross ~~fuel-and-payload loading~~.		* '''000WEIGHT100''': 100% of maximum gross weight.
	* '''000WEIGHT125''': 125% of ~~the normal fuel-and-payload allowance~~.		* '''000WEIGHT125''': 125% of maximum gross weight.
	* '''000WEIGHT150''' or '''000WEIGHT200''': 150% or 200% of ~~that allowance~~ for ~~heavier~~ overload tests.		* '''000WEIGHT150''' or '''000WEIGHT200''': 150% or 200% of maximum gross weight for overload tests.

	For example, a vehicle with an empty weight of 6,000 lb and a maximum gross weight of 10,000 lb ~~has a 4~~,000 lb ~~allowance~~. '''~~000WEIGHT150~~''' loads 6,000 lb of fuel plus payload, giving 12,000 lb gross ~~before any~~ additional ice ~~weight~~. ~~It does not mean 150% of~~ maximum gross ~~weight~~.		For example, a vehicle with an empty weight of 6,000 lb and a maximum gross weight of 10,000 lb receives 9,000 lb of fuel plus payload with '''000WEIGHT150''', giving 15,000 lb gross. '''000WEIGHT200''' loads 14,000 lb of fuel plus payload, giving 20,000 lb gross. These targets exclude additional modeled weight such as accumulated ice, which is still added separately by the flight model. Use an updated client for this maximum-gross percentage behavior; older clients apply the percentage only to the fuel-and-payload allowance.

	The percentage command adjusts loading once; fuel continues to burn. '''000WEIGHT100''' requests maximum-gross loading and '''000WEIGHT0''' requests minimum test loading.		The percentage command adjusts loading once; fuel continues to burn. '''000WEIGHT100''' requests maximum-gross loading and '''000WEIGHT0''' requests minimum test loading.

codex: /* Players */ Document 000WEIGHT-1 restoration, fuel burn, server precedence and vehicle/simulator transitions

2026-10-25T12:29:20Z

Players: Document 000WEIGHT-1 restoration, fuel burn, server precedence and vehicle/simulator transitions

← Older revision		Revision as of 12:29, 25 October 2026
Line 9:		Line 9:
	Using this command has the same implications as a normal [[deaths\|death]]. You will also be refueled but there are limitations ... for example, you can't self-destruct to get fuel, sell all the fuel, and then expect to be awarded a full tank on subsequent self-destruct ... you must burn fuel awarded through self-destruct in order to get fuel in the future.		Using this command has the same implications as a normal [[deaths\|death]]. You will also be refueled but there are limitations ... for example, you can't self-destruct to get fuel, sell all the fuel, and then expect to be awarded a full tank on subsequent self-destruct ... you must burn fuel awarded through self-destruct in order to get fuel in the future.
	<br /><br />		<br /><br />
	'''000WEIGHT<percent>'''		'''000WEIGHT<percent>''' and '''000WEIGHT-1'''

	Artificially set your vehicle's fuel and payload loading for flight testing. Administrators can use this in their current vehicle; other players can use it only while in a [[Flight Simulators\|simulator]].		Artificially set your vehicle's fuel and payload loading for flight testing. Administrators can use this in their current vehicle; other players can use it only while in a [[Flight Simulators\|simulator]].

	Enter a whole-number percentage directly after the command, without a percent sign, for example '''000WEIGHT125'''. '''Values above 100 are supported''' and allow overweight testing. Use ordinary decimal digits without leading zeros in the percentage; fractional percentages are not supported.		Enter a non-negative whole-number percentage directly after the command, without a percent sign, for example '''000WEIGHT125'''. '''Values above 100 are supported''' and allow overweight testing. Use ordinary decimal digits without leading zeros in the percentage; fractional percentages are not supported.

	The percentage applies to the normal fuel-and-payload allowance: '''maximum gross weight minus empty weight'''. The requested load is:		The percentage applies to the normal fuel-and-payload allowance: '''maximum gross weight minus empty weight'''. The requested load is:
Line 19:		Line 19:
	:<code>(maximum gross weight - empty weight) * percent / 100</code>		:<code>(maximum gross weight - empty weight) * percent / 100</code>

	Fuel is filled first, up to tank capacity, and any remaining load becomes payload. ~~Fuel is~~ never ~~set~~ below 2% of tank capacity ~~by this command~~. The extra load above 100% is not capped at maximum gross weight.		Fuel is filled first, up to tank capacity, and any remaining load becomes payload. A percentage loading request never sets fuel below 2% of tank capacity. The extra load above 100% is not capped at maximum gross weight.

	* '''000WEIGHT0''': zero payload and 2% fuel; slightly above empty weight.		* '''000WEIGHT0''': zero payload and 2% fuel; slightly above empty weight.
Line 29:		Line 29:
	For example, a vehicle with an empty weight of 6,000 lb and a maximum gross weight of 10,000 lb has a 4,000 lb allowance. '''000WEIGHT150''' loads 6,000 lb of fuel plus payload, giving 12,000 lb gross before any additional ice weight. It does not mean 150% of maximum gross weight.		For example, a vehicle with an empty weight of 6,000 lb and a maximum gross weight of 10,000 lb has a 4,000 lb allowance. '''000WEIGHT150''' loads 6,000 lb of fuel plus payload, giving 12,000 lb gross before any additional ice weight. It does not mean 150% of maximum gross weight.

	~~This is a one-time~~ loading ~~adjustment, not a weight lock:~~ fuel continues to burn, and ~~subsequent server~~ loading ~~updates can~~ replace the fuel and ~~payload values~~. ~~To return~~ to ~~normal maximum-gross~~ loading, ~~enter~~ '''~~000WEIGHT100~~'''; ~~for minimum loading, enter~~ '''~~000WEIGHT0~~'''. ~~Neither command~~ restores the ~~exact fuel~~ and ~~payload carried before~~ the ~~test~~.		The percentage command adjusts loading once; fuel continues to burn. '''000WEIGHT100''' requests maximum-gross loading and '''000WEIGHT0''' requests minimum test loading.

			'''000WEIGHT-1: restore normal loading (updated client required)'''

			Enter '''000WEIGHT-1''' to end the loading test. The client restores the payload carried before the first percentage command and the fuel carried at that point minus fuel burned during the test, with a minimum of zero. Changing the test percentage again does not replace the original saved loading or refund fuel already burned. Normal weight calculation then uses empty weight, fuel, payload and any additional modeled weight such as accumulated ice. The 2% test fuel floor does not apply to restoration.

			If no loading test is active, '''000WEIGHT-1''' leaves the current loading unchanged. A new fuel/payload update from the server takes precedence and ends the test; a later '''000WEIGHT-1''' does not overwrite that update. Entering or leaving simulator mode on the same vehicle also ends the test and restores its normal loading. Transferring to another vehicle discards the saved loading, so it cannot be restored into the new vehicle. Saved restoration data is local to the current client session.

			The same permissions apply to setting and restoring loading: administrators, or any player while in the simulator. In the updated client, fractional values, malformed commands, integers outside the supported 32-bit range and negative values other than '''-1''' are ignored without changing loading. Older clients do not have the restore command; use an updated client for this procedure.

	==Admins Only==		==Admins Only==

reskin: Undo revision 5055 by reskin (talk)

2026-10-25T12:17:52Z

Undo revision 5055 by reskin (talk)

← Older revision		Revision as of 12:17, 25 October 2026
Line 9:		Line 9:
	Using this command has the same implications as a normal [[deaths\|death]]. You will also be refueled but there are limitations ... for example, you can't self-destruct to get fuel, sell all the fuel, and then expect to be awarded a full tank on subsequent self-destruct ... you must burn fuel awarded through self-destruct in order to get fuel in the future.		Using this command has the same implications as a normal [[deaths\|death]]. You will also be refueled but there are limitations ... for example, you can't self-destruct to get fuel, sell all the fuel, and then expect to be awarded a full tank on subsequent self-destruct ... you must burn fuel awarded through self-destruct in order to get fuel in the future.
	<br /><br />		<br /><br />
	'''~~000WEIGHT0''' through '''000WEIGHT100~~'''		'''000WEIGHT<percent>'''

	Artificially set your vehicle ~~weight (~~[[Flight Simulators\|~~flight simulators~~]])		Artificially set your vehicle's fuel and payload loading for flight testing. Administrators can use this in their current vehicle; other players can use it only while in a [[Flight Simulators\|simulator]].

	~~Set your~~ vehicle ~~weight between "~~empty weight" and ~~"max~~ gross weight" for ~~flight testing (admins) or when in~~ the ~~[[Flight Simulators\|simulator]] (all other players)~~.		Enter a whole-number percentage directly after the command, without a percent sign, for example '''000WEIGHT125'''. '''Values above 100 are supported''' and allow overweight testing. Use ordinary decimal digits without leading zeros in the percentage; fractional percentages are not supported.

			The percentage applies to the normal fuel-and-payload allowance: '''maximum gross weight minus empty weight'''. The requested load is:

			:<code>(maximum gross weight - empty weight) * percent / 100</code>

			Fuel is filled first, up to tank capacity, and any remaining load becomes payload. Fuel is never set below 2% of tank capacity by this command. The extra load above 100% is not capped at maximum gross weight.

			* '''000WEIGHT0''': zero payload and 2% fuel; slightly above empty weight.
			* '''000WEIGHT50''': half the normal fuel-and-payload allowance, subject to the minimum fuel load.
			* '''000WEIGHT100''': the normal maximum-gross fuel-and-payload loading.
			* '''000WEIGHT125''': 125% of the normal fuel-and-payload allowance.
			* '''000WEIGHT150''' or '''000WEIGHT200''': 150% or 200% of that allowance for heavier overload tests.

			For example, a vehicle with an empty weight of 6,000 lb and a maximum gross weight of 10,000 lb has a 4,000 lb allowance. '''000WEIGHT150''' loads 6,000 lb of fuel plus payload, giving 12,000 lb gross before any additional ice weight. It does not mean 150% of maximum gross weight.

			This is a one-time loading adjustment, not a weight lock: fuel continues to burn, and subsequent server loading updates can replace the fuel and payload values. To return to normal maximum-gross loading, enter '''000WEIGHT100'''; for minimum loading, enter '''000WEIGHT0'''. Neither command restores the exact fuel and payload carried before the test.

	==Admins Only==		==Admins Only==

← Older revision		Revision as of 23:38, 29 October 2026
Line 218:		Line 218:
	\| <code>000COMMANDLF0</code> or <code>000COMMANDLF10</code> \|\| Dry loose sand/dirt		\| <code>000COMMANDLF0</code> or <code>000COMMANDLF10</code> \|\| Dry loose sand/dirt
	\|-		\|-
	\| <code>000COMMANDLF1</code> \|\| Open-water spray		\| <code>000COMMANDLF1</code> \|\| Open-water steam/spray
	\|-		\|-
	\| <code>000COMMANDLF2</code> through <code>000COMMANDLF31</code>, except 10 \|\| Dry mineral dust		\| <code>000COMMANDLF2</code> through <code>000COMMANDLF31</code>, except 10 \|\| Dry mineral dust
Line 224:		Line 224:
	\| <code>000COMMANDLF32</code> \|\| Dry pavement/road dust		\| <code>000COMMANDLF32</code> \|\| Dry pavement/road dust
	\|-		\|-
	\| <code>000COMMANDLF33</code> \|\| Wet-ground mist		\| <code>000COMMANDLF33</code> \|\| Wet-ground steam/mist
	\|-		\|-
	\| <code>000COMMANDLF34</code> \|\| Snow aerosol		\| <code>000COMMANDLF34</code> \|\| Snow aerosol
Line 231:		Line 231:
	\|}		\|}

	Values 0 through 31 select the existing landform classifications; 32 through 34 are preview presets, not additional terrain IDs. The dry presets ignore local wetness, snow, roads and roofs for the ground-wash comparison. Other visible weather continues normally. Only the ~~dust/spray~~ material changes: terrain textures, terrain height, collisions, traction and other players are unaffected.		Values 0 through 31 select the existing landform classifications; 32 through 34 are preview presets, not additional terrain IDs. The dry presets ignore local wetness, snow, roads and roofs for the ground-wash comparison. Other visible weather continues normally. Mineral dust retains the current location's base terrain tint. Only the ground-wash material changes: terrain textures, terrain height, collisions, traction and other players are unaffected.

	Each selection or reset clears the previous ~~dust/spray~~ cloud. The effect still requires actual engine output and a plume that reaches the local ground; it does not force emission from idle engines, in space, in interiors or in unsupported vehicles. Height, thrust direction and surface wind continue to control the wash. The preview uses the normal bounded ground-wash model. Dry snow and loose sand/dirt can form outward-moving waves of dense cloud that obscure the surroundings, with blowing flakes over snow; it does not simulate erosion or change vehicle performance. See [[VTOL#Near-surface effects\|near-surface effects]] for the normal limits.		Each selection or reset clears the previous ground-wash cloud. The effect still requires actual engine output and a plume that reaches the local ground; it does not force emission from idle engines, in space, in interiors or in unsupported vehicles. Height, thrust direction and surface wind continue to control the wash. The preview uses the normal bounded ground-wash model. Dry snow and loose sand/dirt can form outward-moving waves of dense cloud that obscure the surroundings, with blowing flakes over snow; it does not simulate erosion or change vehicle performance. See [[VTOL#Near-surface effects\|near-surface effects]] for the normal limits.

			Mineral dust forms faint rolling clouds tinted by the terrain; pavement dust is lighter and gray. Wet ground adds subtle pale steam/mist, while open water produces much denser, taller white steam with spray. Detached steam rises as it fades, more strongly over open water. Steam is a visual proxy for condensed droplets and spray, not a heat-transfer, boiling or water-consumption simulation.

	An active vehicle outside the in-world simulator is required. Simulator entry clears the preview, and leaving the simulator does not restore it. Changing vehicles, becoming inactive, losing administrator access, a graphics-device reset or restarting the client also clears it. Use <code>000COMMANDLF-1</code> to stop manually.		An active vehicle outside the in-world simulator is required. Simulator entry clears the preview, and leaving the simulator does not restore it. Changing vehicles, becoming inactive, losing administrator access, a graphics-device reset or restarting the client also clears it. Use <code>000COMMANDLF-1</code> to stop manually.

	The prefix is case-insensitive. Use ordinary decimal digits, or exactly <code>-1</code> to reset; fractions, plus signs, exponent notation, extra parameters and values outside the listed range are rejected without changing the current selection. Accepted selections and resets appear in the local Communications history as the command you entered. Detailed command status, rejection reasons and usage guidance appear in the client log. The command is handled locally and is not sent to other players or the server.		The prefix is case-insensitive. Use ordinary decimal digits, or exactly <code>-1</code> to reset; fractions, plus signs, exponent notation, extra parameters and values outside the listed range are rejected without changing the current selection. Accepted selections and resets appear in the local Communications history as the command you entered. Detailed command status, rejection reasons and usage guidance appear in the client log. The command is handled locally and is not sent to other players or the server.