PSUnreal Proximity Triggers - Revision history

Talad: /* Proximity triggers in PSLegacy and in PSUnreal */

2021-11-30T23:00:17Z

Proximity triggers in PSLegacy and in PSUnreal

← Older revision		Revision as of 23:00, 30 November 2021
Line 5:		Line 5:
	In Legacy we have three ways to use proximity triggers.		In Legacy we have three ways to use proximity triggers.

	1) '''Action Locations'''. You can set action_locations.triggertype field with the value PROXIMITY, and responsetype SCRIPT, to trigger a certain script when the player is within range from the action location. The range is defined with the field action_locations.radius		1) '''Action Locations'''. You can set [[Action locationsTable\|action_locations]].triggertype field with the value PROXIMITY, and responsetype SCRIPT, to trigger a certain script when the player is within range from the action location. The range is defined with the field action_locations.radius


	In PSUnreal, from the database point of view all data remains the same. From the server code point of view, we spawn a new ApsProxyTrigger class Actor, which is responsible of triggering the range proximity with a standard UE Overlap event.		In PSUnreal, from the database point of view all data remains the same. From the server code point of view, we spawn a new ApsProxyTrigger class Actor, which is responsible of triggering the range proximity with a standard UE Overlap event.

Talad at 22:46, 30 November 2021

2021-11-30T22:46:23Z

← Older revision		Revision as of 22:46, 30 November 2021
Line 5:		Line 5:
	In Legacy we have three ways to use proximity triggers.		In Legacy we have three ways to use proximity triggers.

	1) Action Locations. You can set action_locations.triggertype field with the value PROXIMITY, and responsetype SCRIPT, to trigger a certain script when the player is within range from the action location. The range is defined with the field action_locations.radius		1) '''Action Locations'''. You can set action_locations.triggertype field with the value PROXIMITY, and responsetype SCRIPT, to trigger a certain script when the player is within range from the action location. The range is defined with the field action_locations.radius

	In PSUnreal, from the database point of view all data remains the same. From the server code point of view, we spawn a new ApsProxyTrigger class Actor, which is responsible of triggering the range proximity with a standard UE Overlap event.		In PSUnreal, from the database point of view all data remains the same. From the server code point of view, we spawn a new ApsProxyTrigger class Actor, which is responsible of triggering the range proximity with a standard UE Overlap event.

	2) In npc_triggers.trigger_text we can use: !veryshortrange , !shortrange, !longrange . These predefined ranges which will trigger a response from an NPC, the response can be simple text or a script.		2) In '''npc_triggers.trigger_text''' we can use: !veryshortrange , !shortrange, !longrange . These predefined ranges which will trigger a response from an NPC, the response can be simple text or a script.

	In PSUnreal TBD		In PSUnreal TBD

	3) In quests, you can define a player trigger with : !veryshortrange , !shortrange, !longrange . Example:		3) In '''quests''', you can define a player trigger with : !veryshortrange , !shortrange, !longrange . Example:

	P: !shortrange.		P: !shortrange.

Talad at 22:20, 28 October 2021

2021-10-28T22:20:27Z

← Older revision		Revision as of 22:20, 28 October 2021
Line 9:		Line 9:
	In PSUnreal, from the database point of view all data remains the same. From the server code point of view, we spawn a new ApsProxyTrigger class Actor, which is responsible of triggering the range proximity with a standard UE Overlap event.		In PSUnreal, from the database point of view all data remains the same. From the server code point of view, we spawn a new ApsProxyTrigger class Actor, which is responsible of triggering the range proximity with a standard UE Overlap event.

	2)		2) In npc_triggers.trigger_text we can use: !veryshortrange , !shortrange, !longrange . These predefined ranges which will trigger a response from an NPC, the response can be simple text or a script.

			In PSUnreal TBD

			3) In quests, you can define a player trigger with : !veryshortrange , !shortrange, !longrange . Example:

			P: !shortrange.
			Stalg: [You see a very large marfusang almost as big as a stone house. Looks like Belcor Krakko was right!]

			In PSUnreal TBD

Talad: Created page with "=== Proximity triggers in PSLegacy and in PSUnreal === Proximity triggers are defined as a range in meters constantly checked by the engine, to trigger certain functionality..."

2021-10-28T22:15:14Z

Created page with "=== Proximity triggers in PSLegacy and in PSUnreal === Proximity triggers are defined as a range in meters constantly checked by the engine, to trigger certain functionality..."

New page

=== Proximity triggers in PSLegacy and in PSUnreal ===

Proximity triggers are defined as a range in meters constantly checked by the engine, to trigger certain functionality when the player is within that range from an NPC or an action location.

In Legacy we have three ways to use proximity triggers.

1) Action Locations. You can set action_locations.triggertype field with the value PROXIMITY, and responsetype SCRIPT, to trigger a certain script when the player is within range from the action location. The range is defined with the field action_locations.radius

In PSUnreal, from the database point of view all data remains the same. From the server code point of view, we spawn a new ApsProxyTrigger class Actor, which is responsible of triggering the range proximity with a standard UE Overlap event.

2)