Monster Scripts - Revision history

Panda at 19:38, 15 April 2024

2024-04-15T19:38:05Z

Panda at 19:34, 15 April 2024

2024-04-15T19:34:03Z

← Older revision		Revision as of 12:34, 15 April 2024
Line 50:		Line 50:
	<li> Click the path button to set the starting position. It will say in chat "Start pos SET"</li>		<li> Click the path button to set the starting position. It will say in chat "Start pos SET"</li>
	<li> The next steps are easier to do if you change the axis in the build tools to Local.</li>		<li> The next steps are easier to do if you change the axis in the build tools to Local.</li>
	<li> Drag the monster forward a bit and click the box to save a point.</li>		<li> Drag the monster forward a bit and click the box to save a point.
	<li> Rotate the monster and drag it a little bit forward. Then click it again to save that point. The short distance forward is needed because every step will tween both position AND rotation. And that looks bad if it tweens the rotation over the entire distance that it is walking.</li>		[[File:Monster box A.jpg\|frameless]]
	<li> Drag it forward some more and click again. This will be enough points for this tutorial.</li>		</li>
			<li> Rotate the monster and drag it a little bit forward. Then click it again to save that point. The short distance forward is needed because every step will tween both position AND rotation. And that looks bad if it tweens the rotation over the entire distance that it is walking.
			[[File:Monster box B.jpg\|frameless]]
			</li>
			<li> Drag it forward some more and click again. This will be enough points for this tutorial.
			[[File:Monster box C.jpg\|frameless]]
			</li>
	<li> Say WA in chat to have the path box generate code for you. In my case the output was this:		<li> Say WA in chat to have the path box generate code for you. In my case the output was this:
	<pre>		<pre>

Panda at 19:30, 15 April 2024

2024-04-15T19:30:37Z

← Older revision		Revision as of 12:30, 15 April 2024
Line 43:		Line 43:
	Monsters walking along a path in GoThongs is done with a monsterscript using llSetKeyframedMotion. But there is a built in walk helper to help you with it!		Monsters walking along a path in GoThongs is done with a monsterscript using llSetKeyframedMotion. But there is a built in walk helper to help you with it!

	# Click the Path button on the dev HUD.		<ol>
	# Spawn the monster that you want to walk as a dummy, such as the goblin that we created in the previous step.		<li> Click the Path button on the dev HUD.</li>
	# Enter build mode and select the goblin. Copy the position and rotation by clicking the C buttons next to Position and Rotation.		<li> Spawn the monster that you want to walk as a dummy, such as the goblin that we created in the previous step.</li>
	# Select the path box and paste the position and rotation by clicking the P Button next to Position and Rotation.[[File:Path box.png\|none\|thumb]]		<li> Enter build mode and select the goblin. Copy the position and rotation by clicking the C buttons next to Position and Rotation.</li>
	# Click the path button to set the starting position. It will say in chat "Start pos SET"		<li> Select the path box and paste the position and rotation by clicking the P Button next to Position and Rotation.[[File:Path box.png\|none\|thumb]]</li>
	# The next steps are easier to do if you change the axis in the build tools to Local.		<li> Click the path button to set the starting position. It will say in chat "Start pos SET"</li>
	# Drag the monster forward a bit and click the box to save a point.		<li> The next steps are easier to do if you change the axis in the build tools to Local.</li>
	# Rotate the monster and drag it a little bit forward. Then click it again to save that point. The short distance forward is needed because every step will tween both position AND rotation. And that looks bad if it tweens the rotation over the entire distance that it is walking.		<li> Drag the monster forward a bit and click the box to save a point.</li>
	# Drag it forward some more and click again. This will be enough points for this tutorial.		<li> Rotate the monster and drag it a little bit forward. Then click it again to save that point. The short distance forward is needed because every step will tween both position AND rotation. And that looks bad if it tweens the rotation over the entire distance that it is walking.</li>
	# Say WA in chat to have the path box generate code for you. In my case the output was this:		<li> Drag it forward some more and click again. This will be enough points for this tutorial.</li>
			<li> Say WA in chat to have the path box generate code for you. In my case the output was this:
	<pre>		<pre>
	[		[
Line 60:		Line 61:
	]		]
	Timeout: 6.178000		Timeout: 6.178000
	</pre>		</pre></li>
	# We can use the list that it generated to build the path. Let us edit the ms Goblin script in the level again and replace the llOwnerSay("I have been interacted with!"), with the following:		<li> We can use the list that it generated to build the path. Let us edit the ms Goblin script in the level again and replace the llOwnerSay("I have been interacted with!"), with the following:
	<pre>		<pre>
	Status$monster_overrideDesc("");		Status$monster_overrideDesc("");
Line 71:		Line 72:
	multiTimer(["STOP", 0, 6.178000, FALSE]);		multiTimer(["STOP", 0, 6.178000, FALSE]);
	AniAnim$restart("walk");		AniAnim$restart("walk");
	</pre>		</pre></li>
	# This code removes the interact, starts a keyframed motion, sets a timer called "STOP" with data 0 to fire after 6.178 seconds and not repeat and starts the "walk" animation.		<li> This code removes the interact, starts a keyframed motion, sets a timer called "STOP" with data 0 to fire after 6.178 seconds and not repeat and starts the "walk" animation.</li>
	# Finally we must add a handler in the multiTimerEvent for "STOP":		<li> Finally we must add a handler in the multiTimerEvent for "STOP":
	<pre>		<pre>
	if( id == "STOP" ){		if( id == "STOP" ){
	AniAnim$stop("walk");		AniAnim$stop("walk");
	}		}
	</pre>		</pre></li>
	# Spawn the monster live. Interact with it to see it walk the path that you made and then stop.		<li> Spawn the monster live. Interact with it to see it walk the path that you made and then stop.</li>
			</ol>

	[[Category:Tutorials]]		[[Category:Tutorials]]

Panda at 19:27, 15 April 2024

2024-04-15T19:27:36Z

← Older revision		Revision as of 12:27, 15 April 2024
Line 24:		Line 24:
	# Interacts (E) will only be sent to a script called got LocalConf. But we can add a script alias to our monsterscript. Before #include "got_mods/pandamod/_core.lsl" you must put #define SCRIPT_ALIASES ["got LocalConf"]		# Interacts (E) will only be sent to a script called got LocalConf. But we can add a script alias to our monsterscript. Before #include "got_mods/pandamod/_core.lsl" you must put #define SCRIPT_ALIASES ["got LocalConf"]
	# Find the "// Put your initialization code in here" comment and below it put: Status$monster_overrideDesc("D$Hello!$$STDIN");		# Find the "// Put your initialization code in here" comment and below it put: Status$monster_overrideDesc("D$Hello!$$STDIN");
	# Replace the link message handler with:<pre>		# Replace the link message handler with:
			<pre>
	// Standard in		// Standard in
	#include "xobj_core/_LM.lsl"		#include "xobj_core/_LM.lsl"
Line 51:		Line 52:
	# Rotate the monster and drag it a little bit forward. Then click it again to save that point. The short distance forward is needed because every step will tween both position AND rotation. And that looks bad if it tweens the rotation over the entire distance that it is walking.		# Rotate the monster and drag it a little bit forward. Then click it again to save that point. The short distance forward is needed because every step will tween both position AND rotation. And that looks bad if it tweens the rotation over the entire distance that it is walking.
	# Drag it forward some more and click again. This will be enough points for this tutorial.		# Drag it forward some more and click again. This will be enough points for this tutorial.
	# Say WA in chat to have the path box generate code for you. In my case the output was this:<pre>		# Say WA in chat to have the path box generate code for you. In my case the output was this:
			<pre>
	[		[
	<0,-2.445,0>,NormRot(<0,0,0,1>),2.444,		<0,-2.445,0>,NormRot(<0,0,0,1>),2.444,
Line 59:		Line 61:
	Timeout: 6.178000		Timeout: 6.178000
	</pre>		</pre>
	# We can use the list that it generated to build the path. Let us edit the ms Goblin script in the level again and replace the llOwnerSay("I have been interacted with!"), with the following:<pre>		# We can use the list that it generated to build the path. Let us edit the ms Goblin script in the level again and replace the llOwnerSay("I have been interacted with!"), with the following:
			<pre>
	Status$monster_overrideDesc("");		Status$monster_overrideDesc("");
	llSetKeyframedMotion([		llSetKeyframedMotion([
Line 70:		Line 73:
	</pre>		</pre>
	# This code removes the interact, starts a keyframed motion, sets a timer called "STOP" with data 0 to fire after 6.178 seconds and not repeat and starts the "walk" animation.		# This code removes the interact, starts a keyframed motion, sets a timer called "STOP" with data 0 to fire after 6.178 seconds and not repeat and starts the "walk" animation.
	# Finally we must add a handler in the multiTimerEvent for "STOP":<pre>		# Finally we must add a handler in the multiTimerEvent for "STOP":
			<pre>
	if( id == "STOP" ){		if( id == "STOP" ){
	AniAnim$stop("walk");		AniAnim$stop("walk");

Panda: /* 3. Using the walk helper to create a path for your NPC */

2024-04-15T19:27:11Z

3. Using the walk helper to create a path for your NPC

← Older revision		Revision as of 12:27, 15 April 2024
Line 40:		Line 40:

	== 3. Using the walk helper to create a path for your NPC ==		== 3. Using the walk helper to create a path for your NPC ==
			Monsters walking along a path in GoThongs is done with a monsterscript using llSetKeyframedMotion. But there is a built in walk helper to help you with it!

			# Click the Path button on the dev HUD.
			# Spawn the monster that you want to walk as a dummy, such as the goblin that we created in the previous step.
			# Enter build mode and select the goblin. Copy the position and rotation by clicking the C buttons next to Position and Rotation.
			# Select the path box and paste the position and rotation by clicking the P Button next to Position and Rotation.[[File:Path box.png\|none\|thumb]]
			# Click the path button to set the starting position. It will say in chat "Start pos SET"
			# The next steps are easier to do if you change the axis in the build tools to Local.
			# Drag the monster forward a bit and click the box to save a point.
			# Rotate the monster and drag it a little bit forward. Then click it again to save that point. The short distance forward is needed because every step will tween both position AND rotation. And that looks bad if it tweens the rotation over the entire distance that it is walking.
			# Drag it forward some more and click again. This will be enough points for this tutorial.
			# Say WA in chat to have the path box generate code for you. In my case the output was this:<pre>
			[
			<0,-2.445,0>,NormRot(<0,0,0,1>),2.444,
			<.177,0,0>,NormRot(<0,0,.707,.707>),.178,
			<3.551,0,0>,NormRot(<0,0,0,1>),3.556
			]
			Timeout: 6.178000
			</pre>
			# We can use the list that it generated to build the path. Let us edit the ms Goblin script in the level again and replace the llOwnerSay("I have been interacted with!"), with the following:<pre>
			Status$monster_overrideDesc("");
			llSetKeyframedMotion([
			<0,-2.445,0>,NormRot(<0,0,0,1>),2.444,
			<.177,0,0>,NormRot(<0,0,.707,.707>),.178,
			<3.551,0,0>,NormRot(<0,0,0,1>),3.556
			], []);
			multiTimer(["STOP", 0, 6.178000, FALSE]);
			AniAnim$restart("walk");
			</pre>
			# This code removes the interact, starts a keyframed motion, sets a timer called "STOP" with data 0 to fire after 6.178 seconds and not repeat and starts the "walk" animation.
			# Finally we must add a handler in the multiTimerEvent for "STOP":<pre>
			if( id == "STOP" ){
			AniAnim$stop("walk");
			}
			</pre>
			# Spawn the monster live. Interact with it to see it walk the path that you made and then stop.

	[[Category:Tutorials]]		[[Category:Tutorials]]

Panda at 19:13, 15 April 2024

2024-04-15T19:13:37Z

← Older revision		Revision as of 12:13, 15 April 2024
Line 1:		Line 1:
	Monster scripts are scripts that are injected into monsters on demand inside levels. The monster scripts are custom and stored inside of each level.		Monster scripts are scripts that are injected into monsters on demand inside levels. The monster scripts are custom and stored inside of each level.

			A good template of a monster script can be found in ms MonsterScript which is included with the developer tools.

			You can make a monster script any way you want! The only requirement is that you raise the SCRIPT_INIT event once your script is ready to go. In the template this is added to the state_entry event handler: raiseEvent(evt$SCRIPT_INIT, "");

			== 1. Adding a monster script to the level ==

			# Edit the level and create a new script. To make it easy to distinguish you should start the script name with "ms ". Like "ms Goblin".
			# Set the script to full perm (mod/copy/transfer).
			# Open the script and uncheck the Running box.
			# Copy the contents from ms MonsterScript to your ms Goblin script.
			# In state entry add llOwnerSay("The monster script loaded successfully!");
			# Rez a goblin or some other NPC by saying: spawn Cock Goblin 2
			# Set its description to: $<nowiki>[["SC","ms Goblin"]]</nowiki>
			# Create a spawn entry by saying: add
			# Spawn the monster as live. If you did everything right you will get a chat message saying that the script loaded successfully.
			# What you do with the monster script is up to you. It can interact with all events and run methods on the scripts involved with NPCs. Like got Monster or got Status. The methods and events are defined in the script header files: https://github.com/JasXSL/GoThongs/tree/master/classes

			== 2. Interacting with an NPC ==

			# Let us use a monster script called "ms Goblin". We set the monster description to ''$[["SC","ms Goblin"],[0,8664]]'' You can edit an existing description by finding its id by saying listSpawns. If you created a goblin in the last section you can replace its spawn description by finding its id. In my case the ID of my goblin was 7. So I say ''setSpawnVal 7 4 [["SC","ms Goblin"],[0,8662]]''
			# The 0 task means to set a bitwise combination of monster flags. The flags 8664 Monster$RF_NOAGGRO, Monster$RF_FREEZE_AGGRO, Monster$RF_INVUL, Monster$RF_NO_TARGET, Monster$RF_NO_SPELLS, Monster$RF_ANIMESH. This means that the monster cannot aggro, it is invulnerable, it cannot be targeted by players, it cannot use spells, and it is animesh. The animesh flag is required for animesh monsters because they use X forward instead of the old monsters that use Z forward.
			# Interacts (E) will only be sent to a script called got LocalConf. But we can add a script alias to our monsterscript. Before #include "got_mods/pandamod/_core.lsl" you must put #define SCRIPT_ALIASES ["got LocalConf"]
			# Find the "// Put your initialization code in here" comment and below it put: Status$monster_overrideDesc("D$Hello!$$STDIN");
			# Replace the link message handler with:<pre>
			// Standard in
			#include "xobj_core/_LM.lsl"
			if( method$isCallback )
			return;
			if( METHOD == LocalConfMethod$stdInteract ){
			llOwnerSay("I have been interacted with!");
			}
			#define LM_BOTTOM
			#include "xobj_core/_LM.lsl"
			</pre>
			# Compile the script and spawn your monster live.
			# If you did it correct you can now press E on the monster to interact with it. Doing so will output your "I have been interacted with!" message.
			# You can remove interactivity from a monster by running ''Status$monster_overrideDesc("");''

			== 3. Using the walk helper to create a path for your NPC ==


	[[Category:Tutorials]]		[[Category:Tutorials]]

Panda at 22:39, 14 April 2024

2024-04-14T22:39:08Z

← Older revision		Revision as of 15:39, 14 April 2024
Line 1:		Line 1:
	Monster scripts are scripts that are injected into monsters on demand inside levels. The monster scripts are custom and stored inside of each level.		Monster scripts are scripts that are injected into monsters on demand inside levels. The monster scripts are custom and stored inside of each level.
			[[Category:Tutorials]]

Panda: Created page with "Monster scripts are scripts that are injected into monsters on demand inside levels. The monster scripts are custom and stored inside of each level."

2024-04-14T22:38:56Z

Created page with "Monster scripts are scripts that are injected into monsters on demand inside levels. The monster scripts are custom and stored inside of each level."

New page

Monster scripts are scripts that are injected into monsters on demand inside levels. The monster scripts are custom and stored inside of each level.