Map unit - Revision history

CEObrainz: /* Rails */

2022-03-09T10:43:00Z

Rails

@@ Line 32: / Line 32: @@
 {{expand section}}
 Array of rail structures. Can only appear in group 0 maps (Static); this section is completely ignored for non-static map units.
 ==Link system==

9desertv0e: FixedCs description

2021-07-31T11:30:10Z

FixedCs description

← Older revision		Revision as of 11:30, 31 July 2021
Line 83:		Line 83:
	\|29\|\|DemoMember\|\|-\|\|デモ参加		\|29\|\|DemoMember\|\|-\|\|デモ参加
	\|-		\|-
	\|32\|\|FixedCs\|\|-\|\|固定CS		\|32\|\|FixedCs\|\|Rigid connection constraint\|\|固定CS
	\|-		\|-
	\|26\|\|ForSale\|\|Links a shop item to its seller (target is the seller NPC).\|\|売り物		\|26\|\|ForSale\|\|Links a shop item to its seller (target is the seller NPC).\|\|売り物

Waikuteru: /* Types */

2021-05-03T20:52:35Z

Types

← Older revision		Revision as of 20:52, 3 May 2021
Line 8:		Line 8:
	Two types of map units exist: ''Static'' and ''Dynamic''.		Two types of map units exist: ''Static'' and ''Dynamic''.

	'''Static map units''' are loaded during stage generation (see [[GameScene]] for more details). Their name is suffixed with <code>_Static</code>. They can contain both map rails and map objects; furthermore objects can be linked to each other to implement custom game logic using the [[#Link system]]. Static ~~actors~~ are always loaded in memory and will be visible if the player is within the actor's <code>TraverseDist</code> (draw distance) set in [[ActorInfo.product.sbyml]]. It's possible to see actors from the top-left to the bottom-right in open-world stages (MainField and AocField) if the <code>TraverseDist</code> is set high enough.		'''Static map units''' are loaded during stage generation (see [[GameScene]] for more details). Their name is suffixed with <code>_Static</code>. They can contain both map rails and map objects; furthermore objects can be linked to each other to implement custom game logic using the [[#Link system]]. Static units are always loaded in memory and will be visible if the player is within the actor's <code>TraverseDist</code> (draw distance) set in [[ActorInfo.product.sbyml]]. It's possible to see actors from the top-left to the bottom-right in open-world stages (MainField and AocField) if the <code>TraverseDist</code> is set high enough.

	'''Dynamic map units''' are loaded and unloaded on-the-fly. Their name is suffixed with <code>_Dynamic</code>. The dynamic loading capability is only really put to good use for open-world type stages (e.g. MainField and AocField). In such map units, the link system cannot be used and only map objects can be specified. Dynamic ~~actors~~ are considered to be loaded once the player is either inside of the map ~~it's~~ placed (always the case for CDungeon and MainFieldDungeon), or the player is (on MainField and AocField) located in one of the map-sections around the map-section the ~~actor~~ is placed in.		'''Dynamic map units''' are loaded and unloaded on-the-fly. Their name is suffixed with <code>_Dynamic</code>. The dynamic loading capability is only really put to good use for open-world type stages (e.g. MainField and AocField). In such map units, the link system cannot be used and only map objects can be specified. Dynamic units are considered to be loaded once the player is either inside of the map they are placed (always the case for CDungeon and MainFieldDungeon), or the player is (on MainField and AocField) located in one of the map-sections around the map-section the unit is placed in.

	'''<u>Example</u>:''' Player is located in <u>H-5</u> so ''G-4, H-4, I-4, G-5- I-5, G-6, H-6 and I-6'' dynamic ~~actors~~ are loaded in memory and will be displayed if the <code>TraverseDist</code> is high enough.		'''<u>Example</u>:''' Player is located in <u>H-5</u> so ''G-4, H-4, I-4, G-5- I-5, G-6, H-6 and I-6'' dynamic units are loaded in memory and will be displayed if the <code>TraverseDist</code> is high enough.

	==Contents==		==Contents==

Waikuteru: /* Types */

2021-05-03T20:48:44Z

Types

Show changes

Greenlord: Some clarification for Pulse Linktags. (Footnote)

2020-11-25T14:46:46Z

Some clarification for Pulse Linktags. (Footnote)

← Older revision		Revision as of 14:46, 25 November 2020
Line 138:		Line 138:
	Count LinkTags are used to increment a GameData flag every time the link tag itself is signalled.		Count LinkTags are used to increment a GameData flag every time the link tag itself is signalled.

	Pulse LinkTags continuously emit a basic signal with a configurable signal duration (PulseLength).		Pulse LinkTags continuously emit a basic signal with a configurable signal duration (PulseLength)<ref>This appears to require a BasicSig input and does not repeat automatically. In order to get this behavior, fire it with a SwitchTimer.</ref>.

	None LinkTags have no effect. They are only used to put different map unit objects into the same placement generation group.		None LinkTags have no effect. They are only used to put different map unit objects into the same placement generation group.

Leoetlino: /* Link tags */

2020-07-01T20:34:01Z

Link tags

← Older revision		Revision as of 20:34, 1 July 2020
Line 130:		Line 130:

	=== Link tags ===		=== Link tags ===
			''Not to be confused with [[actor tag]]s.''

	LinkTagAnd, LinkTagOr, LinkTagNAnd, LinkTagNOr, LinkTagXOr, LinkTagCount, LinkTagPulse, LinkTagNone are small objects that are used to implement a basic logic system in map units.		LinkTagAnd, LinkTagOr, LinkTagNAnd, LinkTagNOr, LinkTagXOr, LinkTagCount, LinkTagPulse, LinkTagNone are small objects that are used to implement a basic logic system in map units.

Leoetlino: /* Definitions */

2020-05-17T17:07:00Z

Definitions

← Older revision		Revision as of 17:07, 17 May 2020
Line 38:		Line 38:
	===Definitions===		===Definitions===
	{{expand section}}		{{expand section}}
			Cs means Constraint<ref>SliderCs links are handled by a function {{addr\|a=0x7100F70D60\|ver=nx-1.5.0}} that is also called by [[AIDef:Action/SwitchStepSliderConstraint]]</ref>.

	{\|class="wikitable sortable"		{\|class="wikitable sortable"
	! ID !! Name !! Description !! Official description		! ID !! Name !! Description !! Official description
Line 55:		Line 57:
	\| 3 \|\| AxisZ \|\| - \|\| Z軸シグナル		\| 3 \|\| AxisZ \|\| - \|\| Z軸シグナル
	\|-		\|-
	\| 37 \|\| BAndSCs \|\| - \|\| ボール＆ソケットCS		\| 37 \|\| BAndSCs \|\| Ball & Socket constraint \|\| ボール＆ソケットCS
	\|-		\|-
	\| 38 \|\| BAndSLimitAngYCs \|\| - \|\| Y角速度制限付ボール＆ソケットCS		\| 38 \|\| BAndSLimitAngYCs \|\| Y angular velocity limited Ball & Socket constraint \|\| Y角速度制限付ボール＆ソケットCS
	\|-		\|-
	\| 0 \|\| BasicSig \|\| Basic signal \|\| 基本シグナル		\| 0 \|\| BasicSig \|\| Basic signal \|\| 基本シグナル
Line 65:		Line 67:
	\| 14 \|\| ChangeAtnSig \|\| Signal on Attention change (e.g. picking up a weapon) \|\| アテンション変更時シグナル		\| 14 \|\| ChangeAtnSig \|\| Signal on Attention change (e.g. picking up a weapon) \|\| アテンション変更時シグナル
	\|-		\|-
	\| 39 \|\| CogWheelCs \|\| - \|\| 歯車CS		\| 39 \|\| CogWheelCs \|\| Gear/cogwheel constraint \|\| 歯車CS
	\|-		\|-
	\| 21 \|\| CopyWaitRevival \|\| Activate links when the revival flag of the CopyWaitRevival target is set (e.g. can be used with LinkTagAnd to trigger basic signals when a chest is opened) \|\| 配置自動セーブ継承		\| 21 \|\| CopyWaitRevival \|\| Activate links when the revival flag of the CopyWaitRevival target is set (e.g. can be used with LinkTagAnd to trigger basic signals when a chest is opened) \|\| 配置自動セーブ継承
Line 87:		Line 89:
	\| 7 \|\| GimmickSuccess \|\| Success signal (used for minigames) \|\| ネタ成功シグナル		\| 7 \|\| GimmickSuccess \|\| Success signal (used for minigames) \|\| ネタ成功シグナル
	\|-		\|-
	\| 33 \|\| HingeCs \|\| - \|\| ヒンジCS		\| 33 \|\| HingeCs \|\| Hinge constraint \|\| ヒンジCS
	\|-		\|-
	\| 12 \|\| LifeZero \|\| Emit a LifeZero signal when the life of the source object is 0 \|\| ライフ0		\| 12 \|\| LifeZero \|\| Emit a LifeZero signal when the life of the source object is 0 \|\| ライフ0
	\|-		\|-
	\| 34 \|\| LimitHingeCs \|\| - \|\| 制限付ヒンジCS		\| 34 \|\| LimitHingeCs \|\| Limited hinge constraint \|\| 制限付ヒンジCS
	\|-		\|-
	\| 27 \|\| ModelBind \|\| - \|\| モデルバインド		\| 27 \|\| ModelBind \|\| - \|\| モデルバインド
Line 105:		Line 107:
	\| 36 \|\| PulleyCs \|\| - \|\| 滑車CS		\| 36 \|\| PulleyCs \|\| - \|\| 滑車CS
	\|-		\|-
	\| 40 \|\| RackAndPinionCs \|\| - \|\| ラック＆ピニオンCS		\| 40 \|\| RackAndPinionCs \|\| Rack-and-pinion constraint \|\| ラック＆ピニオンCS
	\|-		\|-
	\| 23 \|\| Recreate \|\| Recreates the target object \|\| 再生成		\| 23 \|\| Recreate \|\| Recreates the target object \|\| 再生成
Line 115:		Line 117:
	\| 25 \|\| SensorBind \|\| - \|\| センサバインド		\| 25 \|\| SensorBind \|\| - \|\| センサバインド
	\|-		\|-
	\| 35 \|\| SliderCs \|\| - \|\| スライダーCS		\| 35 \|\| SliderCs \|\| Slider constraint \|\| スライダーCS
	\|-		\|-
	\| 13 \|\| Stable \|\| - \|\| 安定		\| 13 \|\| Stable \|\| - \|\| 安定

imported>Leoetlino: /* Link system */ emphasis on generation group

2019-12-20T15:08:02Z

Link system: emphasis on generation group

← Older revision		Revision as of 15:08, 20 December 2019
Line 34:		Line 34:
	LinkTags and other tag objects are lightweight actors that are used to link objects together.		LinkTags and other tag objects are lightweight actors that are used to link objects together.

	Objects that are linked together, either directly or via indirect links, are put into the same generation group and loaded at the same time{{check}}. If the placement system fails to load an actor, the entire generation group is discarded.		Objects that are linked together, either directly or via indirect links, are put into the same '''generation group''' and loaded at the same time{{check}}. If the placement system fails to load an actor, the entire generation group is discarded.

	===Definitions===		===Definitions===

imported>Leoetlino: /* Link tags */ boolean op -> logical op

2019-12-17T20:27:53Z

Link tags: boolean op -> logical op

← Older revision		Revision as of 20:27, 17 December 2019
Line 130:		Line 130:
	LinkTagAnd, LinkTagOr, LinkTagNAnd, LinkTagNOr, LinkTagXOr, LinkTagCount, LinkTagPulse, LinkTagNone are small objects that are used to implement a basic logic system in map units.		LinkTagAnd, LinkTagOr, LinkTagNAnd, LinkTagNOr, LinkTagXOr, LinkTagCount, LinkTagPulse, LinkTagNone are small objects that are used to implement a basic logic system in map units.

	AND, OR, NAND, NOR, XOR LinkTags are ~~boolean~~ operators. They can be used to conditionally set or clear GameData flags, or conditionally spawn objects, trigger other objects, etc. A basic signal is emitted when the LinkTag has been triggered by ''all'' of the source links (for LinkTagAnds) or by one of them (for LinkTagOrs), etc.		AND, OR, NAND, NOR, XOR LinkTags are logical operators. They can be used to conditionally set or clear GameData flags, or conditionally spawn objects, trigger other objects, etc. A basic signal is emitted when the LinkTag has been triggered by ''all'' of the source links (for LinkTagAnds) or by one of them (for LinkTagOrs), etc.

	Count LinkTags are used to increment a GameData flag every time the link tag itself is signalled.		Count LinkTags are used to increment a GameData flag every time the link tag itself is signalled.

imported>Leoetlino at 22:36, 12 October 2019

2019-10-12T22:36:28Z

← Older revision		Revision as of 22:36, 12 October 2019
Line 1:		Line 1:
	~~{{Stub\|what=Complete the contents section, the link system (and possibly other things)}}~~
	''Not to be confused with [[map]]s, [[Stage\|stages]] or [[Scene\|scenes]]''.		''Not to be confused with [[map]]s, [[Stage\|stages]] or [[Scene\|scenes]]''.

Line 14:		Line 13:

	=== <code>LocationPosX</code> ===		=== <code>LocationPosX</code> ===
			X coordinate of the center of the map unit.

	=== <code>LocationPosZ</code> ===		=== <code>LocationPosZ</code> ===
			Y coordinate of the center of the map unit.

	=== <code>LocationSize</code> ===		=== <code>LocationSize</code> ===
			Size of the map unit (side length of the square).

	=== <code>Objs</code> ===		=== <code>Objs</code> ===
			{{expand section}}
	Array of object structures. '''Must be sorted by HashId'''<ref>Technically, sorting is only required for Dynamic (non-group 0) map units. However, not sorting causes the game to fall back to a slower linear search.</ref> because the placement subsystem performs binary searches on the object array in various cases<ref>0x7101256E14</ref>.		Array of object structures. '''Must be sorted by HashId'''<ref>Technically, sorting is only required for Dynamic (non-group 0) map units. However, not sorting causes the game to fall back to a slower linear search.</ref> because the placement subsystem performs binary searches on the object array in various cases<ref>0x7101256E14</ref>.

	=== <code>Rails</code> ===		=== <code>Rails</code> ===
			{{expand section}}
	Array of rail structures. Can only appear in group 0 maps (Static); this section is completely ignored for non-static map units.		Array of rail structures. Can only appear in group 0 maps (Static); this section is completely ignored for non-static map units.

Line 33:		Line 37:

	===Definitions===		===Definitions===
			{{expand section}}
	{\|class="wikitable sortable"		{\|class="wikitable sortable"
	! ID !! Name !! Description !! Official description		! ID !! Name !! Description !! Official description