Useractor - Revision history

Fox: Redirected page to Actor

2020-02-20T07:42:02Z

Redirected page to Actor

← Older revision		Revision as of 00:42, 20 February 2020
Line 1:		Line 1:
	~~'''useractor''' <actortype> <name> [strength] [action] [move] [moveflags...]<br>~~		#REDIRECT [[actor]]
	~~:(actor code...)<br>~~
	~~[[enda]]~~

	Similar to [[actor]]. This defines a new [[actor]] in a slightly more specific manner, and it does so without restraining the amount of [[define]]d [[actor]]s. Version 1.3D only allowed so many [[actor]]s so to add a new one required replacing another. Version 1.5 remedied this with useractor.

	~~<actortype> is technically a [[bitfield]], though "3" is invalid. It is generally either "enemy", "enemystayput", or "notenemy".~~

	~~{\| {{prettytable}}~~
	~~!DEFS.CON Label!!Value!![[htflags]] implied!!Description~~
	\|-
	\|notenemy\|\|0\|\|<font color="gray">(none)</font>\|\|The catch-all default category for generic objects such as decorations. No shadow by default. Will not be targeted if autoaim is enabled. Code begins executing at the start of a level.
	\|-
	~~\|enemy\|\|1\|\|SFLAG_BADGUY\|\|Enables hardcoded behavior for enemies/monsters such as shadows and autoaim. Code only begins executing upon player sight.~~
	\|-
	~~\|enemystayput\|\|2\|\|SFLAG_BADGUY<br>SFLAG_BADGUYSTAYPUT\|\|Same as "enemy" plus the [[actor]] will not leave the [[sector]] it is placed in.~~
	\|-
	~~\|<font color="gray">(none)</font>\|\|4\|\|SFLAG_ROTFIXED\|\|"Doesn't move", therefore the actor's position in rotating sectors can be calculated without rounding errors.~~
	\|}

	~~<name> is the name/tile of the [[actor]]. You can either input a defined name, or the tile number directly.~~

	~~<strength> is the health of the [[actor]]. Also see [[strength]].~~

	~~<action> is the intial [[action]] an [[actor]] uses (optional).~~

	~~<move> is the initial [[move]] of the actor (optional).~~

	~~<moveflags...> is is a (possibly empty) sequence of parameters that specify certain hardcoded movement behavior (optional, see [[move]]).~~

	~~(actor code...) is obviously the code for the [[actor]].~~

	~~[[enda]] ends an [[actor]].~~



	~~'''useractor''' is typically used for all new~~ [[actor~~]]s you may code.~~

	~~A shadow may be applied in EDuke32 using the [[spriteshadow]] command.~~

	~~When the notenemy option is chosen, the blocking feature will work differently. For some reason, you can walk through moving actors, but when they stand still, you can't?~~

	~~[[Category:Duke3D 1.3/1.5 commands]]~~
	~~[[Category:Sprite manipulation~~]]

Hendricks266 at 09:12, 28 February 2014

2014-02-28T09:12:59Z

← Older revision		Revision as of 02:12, 28 February 2014
Line 5:		Line 5:
	Similar to [[actor]]. This defines a new [[actor]] in a slightly more specific manner, and it does so without restraining the amount of [[define]]d [[actor]]s. Version 1.3D only allowed so many [[actor]]s so to add a new one required replacing another. Version 1.5 remedied this with useractor.		Similar to [[actor]]. This defines a new [[actor]] in a slightly more specific manner, and it does so without restraining the amount of [[define]]d [[actor]]s. Version 1.3D only allowed so many [[actor]]s so to add a new one required replacing another. Version 1.5 remedied this with useractor.

	<actortype> is technically a [[bitfield]]. It is generally either "enemy", "enemystayput", or "notenemy".		<actortype> is technically a [[bitfield]], though "3" is invalid. It is generally either "enemy", "enemystayput", or "notenemy".

	{\| {{prettytable}}		{\| {{prettytable}}
Line 16:		Line 16:
	\|enemystayput\|\|2\|\|SFLAG_BADGUY<br>SFLAG_BADGUYSTAYPUT\|\|Same as "enemy" plus the [[actor]] will not leave the [[sector]] it is placed in.		\|enemystayput\|\|2\|\|SFLAG_BADGUY<br>SFLAG_BADGUYSTAYPUT\|\|Same as "enemy" plus the [[actor]] will not leave the [[sector]] it is placed in.
	\|-		\|-
	\|<font color="gray">(none)</font>\|\|4\|\|SFLAG_ROTFIXED\|\|		\|<font color="gray">(none)</font>\|\|4\|\|SFLAG_ROTFIXED\|\|"Doesn't move", therefore the actor's position in rotating sectors can be calculated without rounding errors.
	\|}		\|}

Hendricks266 at 07:18, 28 February 2014

2014-02-28T07:18:42Z

← Older revision		Revision as of 00:18, 28 February 2014
Line 5:		Line 5:
	Similar to [[actor]]. This defines a new [[actor]] in a slightly more specific manner, and it does so without restraining the amount of [[define]]d [[actor]]s. Version 1.3D only allowed so many [[actor]]s so to add a new one required replacing another. Version 1.5 remedied this with useractor.		Similar to [[actor]]. This defines a new [[actor]] in a slightly more specific manner, and it does so without restraining the amount of [[define]]d [[actor]]s. Version 1.3D only allowed so many [[actor]]s so to add a new one required replacing another. Version 1.5 remedied this with useractor.

	<actortype> ~~can~~ either be "enemy", "enemystayput", or "notenemy". ~~These terms are defined in DEFS.CON as:~~		<actortype> is technically a [[bitfield]]. It is generally either "enemy", "enemystayput", or "notenemy".

	~~:[[define]] notenemy 0~~		{\| {{prettytable}}
	:[[~~define~~]] ~~enemy 1~~		!DEFS.CON Label!!Value!![[htflags]] implied!!Description
	~~:[[define]] enemystayput 2~~		\|-
			\|notenemy\|\|0\|\|<font color="gray">(none)</font>\|\|The catch-all default category for generic objects such as decorations. No shadow by default. Will not be targeted if autoaim is enabled. Code begins executing at the start of a level.
	*The "~~enemy~~" ~~type makes an [[actor]] that~~ is ~~intended to be used~~ as ~~a character who commences actions on~~ player sight.		\|-
	*The "enemystayput~~" works the same~~ as "enemy," ~~except that~~ the [[actor]] will not leave the [[sector]] it is placed in.		\|enemy\|\|1\|\|SFLAG_BADGUY\|\|Enables hardcoded behavior for enemies/monsters such as shadows and autoaim. Code only begins executing upon player sight.
	*The "~~notenemy~~" type was primarily intended to make an [[actor]] that is a decoration or otherwise not a threat to the player. This type of [[actor]] will have no shadow by default, and it will not be targeted if autoaim is enabled. [[Actor]]s using the "notenemy" flag have their code executed at startup. This is extremely useful for coding enemies, as this allows for extended function, and has less quirks than using "enemy" or "enemystayput".		\|-
			\|enemystayput\|\|2\|\|SFLAG_BADGUY<br>SFLAG_BADGUYSTAYPUT\|\|Same as "enemy" plus the [[actor]] will not leave the [[sector]] it is placed in.
			\|-
			\|<font color="gray">(none)</font>\|\|4\|\|SFLAG_ROTFIXED\|\|
			\|}

	<name> is the name/tile of the [[actor]]. You can either input a defined name, or the tile number directly.		<name> is the name/tile of the [[actor]]. You can either input a defined name, or the tile number directly.
Line 28:		Line 32:

	[[enda]] ends an [[actor]].		[[enda]] ends an [[actor]].



	'''useractor''' is typically used for all new [[actor]]s you may code.		'''useractor''' is typically used for all new [[actor]]s you may code.
Line 34:		Line 40:

	When the notenemy option is chosen, the blocking feature will work differently. For some reason, you can walk through moving actors, but when they stand still, you can't?		When the notenemy option is chosen, the blocking feature will work differently. For some reason, you can walk through moving actors, but when they stand still, you can't?

	~~Also see [[actor]].~~

	[[Category:Duke3D 1.3/1.5 commands]]		[[Category:Duke3D 1.3/1.5 commands]]
	[[Category:Sprite manipulation]]		[[Category:Sprite manipulation]]

Helixhorned: ai -> moveflags

2012-06-17T18:00:47Z

ai -> moveflags

← Older revision		Revision as of 11:00, 17 June 2012
Line 1:		Line 1:
	'''useractor''' <actortype> <name> [strength] [action] [move] [ai]<br>		'''useractor''' <actortype> <name> [strength] [action] [move] [moveflags...]<br>
	:(actor code...)<br>		:(actor code...)<br>
	[[enda]]		[[enda]]
Line 23:		Line 23:
	<move> is the initial [[move]] of the actor (optional).		<move> is the initial [[move]] of the actor (optional).

	<ai> is ~~the actor's initial~~ [[ai]] ~~routine (optional~~).		<moveflags...> is is a (possibly empty) sequence of parameters that specify certain hardcoded movement behavior (optional, see [[move]]).

	(actor code...) is obviously the code for the [[actor]].		(actor code...) is obviously the code for the [[actor]].

Hendricks266 at 03:02, 6 March 2011

2011-03-06T03:02:29Z

← Older revision		Revision as of 20:02, 5 March 2011
Line 25:		Line 25:
	<ai> is the actor's initial [[ai]] routine (optional).		<ai> is the actor's initial [[ai]] routine (optional).

	{ actor code } is obviously the code for the [[actor]].		(actor code...) is obviously the code for the [[actor]].

	[[enda]] ends an [[actor]].		[[enda]] ends an [[actor]].

Hendricks266 at 03:00, 6 March 2011

2011-03-06T03:00:22Z

← Older revision		Revision as of 20:00, 5 March 2011
Line 1:		Line 1:
	'''useractor''' <actortype> <name> [strength] [action] [move] [ai] { actor code } [[enda]]		'''useractor''' <actortype> <name> [strength] [action] [move] [ai]<br>
			:(actor code...)<br>
			[[enda]]

	Similar to [[actor]]. This defines a new [[actor]] in a slightly more specific manner, and it does so without restraining the amount of [[define]]d [[actor]]s. Version 1.3D only allowed so many [[actor]]s so to add a new one required replacing another. Version 1.5 remedied this with useractor.		Similar to [[actor]]. This defines a new [[actor]] in a slightly more specific manner, and it does so without restraining the amount of [[define]]d [[actor]]s. Version 1.3D only allowed so many [[actor]]s so to add a new one required replacing another. Version 1.5 remedied this with useractor.

Hendricks266 at 02:58, 6 March 2011

2011-03-06T02:58:24Z

← Older revision		Revision as of 19:58, 5 March 2011
Line 1:		Line 1:
	'''useractor''' <actortype> <name> <strength~~> <~~action~~> <~~move~~> <~~ai> { actor code } [[enda]]		'''useractor''' <actortype> <name> [strength] [action] [move] [ai] { actor code } [[enda]]

	Similar to [[actor]]. This defines a new [[actor]] in a slightly more specific manner, and it does so without restraining the amount of [[define]]d [[actor]]s. Version 1.3D only allowed so many [[actor]]s so to add a new one required replacing another. Version 1.5 remedied this with useractor.		Similar to [[actor]]. This defines a new [[actor]] in a slightly more specific manner, and it does so without restraining the amount of [[define]]d [[actor]]s. Version 1.3D only allowed so many [[actor]]s so to add a new one required replacing another. Version 1.5 remedied this with useractor.
Line 11:		Line 11:
	*The "enemy" type makes an [[actor]] that is intended to be used as a character who commences actions on player sight.		*The "enemy" type makes an [[actor]] that is intended to be used as a character who commences actions on player sight.
	*The "enemystayput" works the same as "enemy," except that the [[actor]] will not leave the [[sector]] it is placed in.		*The "enemystayput" works the same as "enemy," except that the [[actor]] will not leave the [[sector]] it is placed in.
	*The "notenemy" type was primarily intended to make an [[actor]] that is a decoration or otherwise not a threat to the player. This type of [[actor]] will have no shadow by default, and it will not be targeted if autoaim is enabled. [[Actor]]s using the "notenemy" flag have their code executed at startup. This is extremely useful for coding enemies, as this allows for extended function, and has less quirks than using "enemy" or "enemystayput". A shadow may be applied in Eduke32 using the [[spriteshadow]] command. This is typically used for all new [[actor]]s you may code. Not that even it blocking is on. When the notenemy option is chosen, the blocking feature will work differently. For some reason, you can walk through moving actors, but when they stand still, you can't?		*The "notenemy" type was primarily intended to make an [[actor]] that is a decoration or otherwise not a threat to the player. This type of [[actor]] will have no shadow by default, and it will not be targeted if autoaim is enabled. [[Actor]]s using the "notenemy" flag have their code executed at startup. This is extremely useful for coding enemies, as this allows for extended function, and has less quirks than using "enemy" or "enemystayput".

	<name> is the name/tile of the [[actor]]. You can either input a defined name, or the tile number directly.		<name> is the name/tile of the [[actor]]. You can either input a defined name, or the tile number directly.
Line 26:		Line 26:

	[[enda]] ends an [[actor]].		[[enda]] ends an [[actor]].

			'''useractor''' is typically used for all new [[actor]]s you may code.

			A shadow may be applied in EDuke32 using the [[spriteshadow]] command.

			When the notenemy option is chosen, the blocking feature will work differently. For some reason, you can walk through moving actors, but when they stand still, you can't?

	Also see [[actor]].		Also see [[actor]].

Rasmusthorup at 20:30, 5 March 2011

2011-03-05T20:30:29Z

← Older revision		Revision as of 13:30, 5 March 2011
Line 11:		Line 11:
	*The "enemy" type makes an [[actor]] that is intended to be used as a character who commences actions on player sight.		*The "enemy" type makes an [[actor]] that is intended to be used as a character who commences actions on player sight.
	*The "enemystayput" works the same as "enemy," except that the [[actor]] will not leave the [[sector]] it is placed in.		*The "enemystayput" works the same as "enemy," except that the [[actor]] will not leave the [[sector]] it is placed in.
	*The "notenemy" type was primarily intended to make an [[actor]] that is a decoration or otherwise not a threat to the player. This type of [[actor]] will have no shadow by default, and it will not be targeted if autoaim is enabled. [[Actor]]s using the "notenemy" flag have their code executed at startup. This is extremely useful for coding enemies, as this allows for extended function, and has less quirks than using "enemy" or "enemystayput". A shadow may be applied in Eduke32 using the [[spriteshadow]] command. This is typically used for all new [[actor]]s you may code.		*The "notenemy" type was primarily intended to make an [[actor]] that is a decoration or otherwise not a threat to the player. This type of [[actor]] will have no shadow by default, and it will not be targeted if autoaim is enabled. [[Actor]]s using the "notenemy" flag have their code executed at startup. This is extremely useful for coding enemies, as this allows for extended function, and has less quirks than using "enemy" or "enemystayput". A shadow may be applied in Eduke32 using the [[spriteshadow]] command. This is typically used for all new [[actor]]s you may code. Not that even it blocking is on. When the notenemy option is chosen, the blocking feature will work differently. For some reason, you can walk through moving actors, but when they stand still, you can't?

	<name> is the name/tile of the [[actor]]. You can either input a defined name, or the tile number directly.		<name> is the name/tile of the [[actor]]. You can either input a defined name, or the tile number directly.

One at 20:40, 4 May 2009

2009-05-04T20:40:56Z

← Older revision		Revision as of 13:40, 4 May 2009
Line 1:		Line 1:
			'''useractor''' <actortype> <name> <strength> <action> <move> <ai> { actor code } [[enda]]

	Similar to [[actor]]. This defines a new [[actor]] in a slightly more specific manner, and it does so without restraining the amount of [[define]]d [[actor]]s. Version 1.3D only allowed so many [[actor]]s so to add a new one required replacing another. Version 1.5 remedied this with useractor.		Similar to [[actor]]. This defines a new [[actor]] in a slightly more specific manner, and it does so without restraining the amount of [[define]]d [[actor]]s. Version 1.3D only allowed so many [[actor]]s so to add a new one required replacing another. Version 1.5 remedied this with useractor.

	~~useractor <actortype> <name> <strength> <action> <move> <ai> { actor code } [[enda]]~~

	<actortype> can either be "enemy", "enemystayput", or "notenemy". These terms are defined in DEFS.CON as:		<actortype> can either be "enemy", "enemystayput", or "notenemy". These terms are defined in DEFS.CON as:

Usurper: Reverted edits by Ilovefoxes (Talk); changed back to last version by TX

2006-12-29T02:44:54Z

Reverted edits by Ilovefoxes (Talk); changed back to last version by TX

← Older revision		Revision as of 19:44, 28 December 2006
Line 28:		Line 28:

	Also see [[actor]].		Also see [[actor]].


	It works like flags, where more than one can be set, wich means that enemy and enemystayput already have notenemy code. Using more than one isn't usefull, as long as the most can be done is use enemy and enemystayput togheder, where there is no difference from enemystayput itself.

	~~If set to a not defined flag like as 4, looks like useractorenemy wich is already activated when the game starts like a actor.~~

	[[Category:Duke3D 1.3/1.5 commands]]		[[Category:Duke3D 1.3/1.5 commands]]
	[[Category:Sprite manipulation]]		[[Category:Sprite manipulation]]