Description

Usage for Mappers

The SBTriggerableSpawnPoint has to be activated by an Event; for example generated by a Trigger or the death of a ScriptedPawn.
If the prototype cannot be spawned or a property could not be set, a warning is written to the log file if LogLevel is set at least to LOG_Error.
If something does not work as you expected, set LogLevel to a higher level and inspect the file UnrealTournament.log in the System directory of UT.

See Maps\TestSBTriggerableSpawnPointV2.unr for examples.

If you release your map to public don't forget to add the file SBTriggerableSpawnPointV2.u to your package and set LogLevel of all SBTriggerableSpawnPoint to a low value.

Source code is included.

Detailed Description

Data Types

ELogType

Use one of the following:

LOG_None	Nothing will be logged.
LOG_Error	An error is a condition where the code cannot proceed further sensefully.
LOG_Warning	If something is unexpeced, a Warning is issued, but the code will proceed.
LOG_Info	Version info or a summory of actions will be logged.
LOG_Verbose	Tell me more than LOG_Info.
LOG_Debug	Log what is done.
LOG_All	Even log what is NOT done.

Boolean

Literally allowed values are "True" and "False".

Name

A Name may contain the letters A to Z, both upper and lowercase, the numbers 0 to 9, the underscore character _, the hyphen character - (not recommended) and the space character (not recommended). A Name may not exceed 63 characters. The case doesn't matter.

Float

A number that may contain a decimal separator. Also scientific notation is possible (e.g. 1.2e3).
See https://wiki.beyondunreal.com/Types#Float for details.

String

A String may contain any except the NULL character. The length is limited to 1023; on network games even less.

White Characters

White Characters create empty space to format text layout. Examples are Space, Tab, Newline.

Array

An Array is string followed by an integer index, embraced in square brackets. White characters around the integer value are NOT allowed.
Example: MultiSkins[2]

Tupel

A Tupel is a set of strings, embraced in round brackets, and contains at least one member. Multiple members are separated by comma. White characters around members are allowed. SBTriggerableSpawnPoint supports up to 8 members per Tupel.

Examples for Tupel

Value	Tupel results in
(test)	'test'
(1,2, 3)	'1', '2', '3'
(1,,2,3)	Error: empty value in second position
(1, ,2,3)	'1', ' ', '2', '3' (notice the white space between member '1' and '2')
()	Error: Tupel without member

EPhysics

Physics may contain one of the enumeration EPhysics values:

PHYS_None
PHYS_Walking
PHYS_Falling
PHYS_Swimming
PHYS_Flying
PHYS_Rotating
PHYS_Projectile
PHYS_Rolling
PHYS_Interpolating
PHYS_MovingBrush
PHYS_Spider
PHYS_Trailer

Special Property Cases

What you cannot do

• Because the function SetPropertyText() can only change single ("scalar") values, arrays, vectors or structs cannot be acessed in general, except the Special Property Cases.
• Const values (bStatic for example) can not be changed.

About

Copyright

Changelog

SBTriggerableSpawnPointV2, Release 08 Feb 2026

• added help (took longer than coding)
• added support for special cases Disable, Enable, GotoState, InitialState, Log, MultiSkins, Physics, RotationRate, Velocity, Warn
• changed two-array of Property/Value to one array of struct of Property/Value
• reduced the array length from 32 to 16
• added bTriggerOnceOnly
• added tiny trigger picture to icon

Filelist

SBTriggerableSpawnPointV1, Release 07 Dec 2025

• expanded PrototypeProperties array lengths from 8 to 32
• added support for arrays as PropertyValue
• added support for array MultiSkins
• added LogLevel for possibly debugging output

Filelist

SBTriggerableSpawnPointV0, Release 10. Jul. 2023

Filelist