Monster Grapples - Revision history

Panda at 21:27, 10 April 2024

2024-04-10T21:27:47Z

← Older revision		Revision as of 14:27, 10 April 2024
Line 144:		Line 144:
	}		}
	</pre>		</pre>
			[[Category:Tutorials]]

Panda: /* Setting up the client */

2024-04-10T21:27:08Z

Setting up the client

← Older revision		Revision as of 14:27, 10 April 2024
Line 101:		Line 101:
	);		);

	</pre>Then you need a grappleOnHookup handler and a grappleOnEnd handler. If your monster should both be able to grapple and hookup, then grappleOnEnd is used for both types of grapples.<pre>		</pre>

			Then you need a grappleOnHookup handler and a grappleOnEnd handler. If your monster should both be able to grapple and hookup, then grappleOnEnd is used for both types of grapples.

			<pre>
	#define grappleOnEnd() grappleOnEnd()		#define grappleOnEnd() grappleOnEnd()
	grappleOnEnd(){		grappleOnEnd(){
Line 123:		Line 127:

	==== Custom conditions: ====		==== Custom conditions: ====
	If you are not content with the built in conditions, you can use the following in the client to test before allowing a grapple:<pre>		If you are not content with the built in conditions, you can use the following in the client to test before allowing a grapple:

			<pre>
	#define grappleOnHupClientTest( poseIndexes ) grappleOnHupClientTest( poseIndexes)		#define grappleOnHupClientTest( poseIndexes ) grappleOnHupClientTest( poseIndexes)
	list grappleOnHupClientTest( list poseIndexes ){		list grappleOnHupClientTest( list poseIndexes ){

Panda: /* Setting up the host */

2024-04-10T21:26:44Z

Setting up the host

← Older revision		Revision as of 14:26, 10 April 2024
Line 65:		Line 65:

	=== Setting up the host ===		=== Setting up the host ===
	The host must be able to do a normal grapple (see above). Once that is setup, the only thing you must setup on the host is a host name for the clients to identify. Something like the following:<pre>		The host must be able to do a normal grapple (see above). Once that is setup, the only thing you must setup on the host is a host name for the clients to identify. Something like the following:
			<pre>
	#define cf$hup$HOST "GOBLIN_BRANDER"		#define cf$hup$HOST "GOBLIN_BRANDER"
	</pre>The client manages the animations and effects of a hookup. But the host has access to a few things if you need them for any reason:<pre>		</pre>

			The client manages the animations and effects of a hookup. But the host has access to a few things if you need them for any reason:

			<pre>
	#define grappleOnClientAnim(npcAnim, playerAnims) grappleOnClientAnim(npcAnim, playerAnims)		#define grappleOnClientAnim(npcAnim, playerAnims) grappleOnClientAnim(npcAnim, playerAnims)
	grappleOnClientAnim(string npcAnim, list playerAnims){		grappleOnClientAnim(string npcAnim, list playerAnims){

Panda at 21:26, 10 April 2024

2024-04-10T21:26:00Z

← Older revision		Revision as of 14:26, 10 April 2024
Line 72:		Line 72:
	// Raised when the client triggers an animation on the host. npcAnim is the host animation.		// Raised when the client triggers an animation on the host. npcAnim is the host animation.
	}		}

	#define grappleOnHookup(hostname) grappleOnHookup(hostname)		#define grappleOnHookup(hostname) grappleOnHookup(hostname)
	grappleOnHookup(str hostname){		grappleOnHookup(str hostname){
Line 78:		Line 77:
	// hostname is empty if we are hosting. Otherwise it is the hostname of the host we are the client for.		// hostname is empty if we are hosting. Otherwise it is the hostname of the host we are the client for.
	}		}


	</pre>		</pre>

Line 118:		Line 115:
	}		}
	}		}


	</pre>		</pre>

Panda at 21:25, 10 April 2024

2024-04-10T21:25:24Z

@@ Line 43: / Line 43: @@
 <pre>
-#define grappleOnStart() grappleOnStart()
+#define grappleOnSeated() grappleOnSeated()
-grappleOnStart(){
+grappleOnSeated(){
-     qd("I have started a grapple!");
+     // Start your animations here and set a timer to damage/arouse player
+}
-</pre>Todo...
+#define grappleOnEnd() grappleOnEnd()

Panda: /* Setting up a grapple */

2024-04-06T00:40:59Z

Setting up a grapple

← Older revision		Revision as of 17:40, 5 April 2024
Line 28:		Line 28:
	#define cf$GRAPPLE_NO_QTE // bool - No QTE. call grappleEnd manually		#define cf$GRAPPLE_NO_QTE // bool - No QTE. call grappleEnd manually
	#define cf$GRAPPLE_FAIL_TIMEOUT // float - On failable grapples, wait this long before unsitting the player.		#define cf$GRAPPLE_FAIL_TIMEOUT // float - On failable grapples, wait this long before unsitting the player.
	</pre>Next you should define event handlers:<pre>		</pre>

			Next you should define event handlers:
			<pre>
	#define grappleOnStart() // A grapple has been started but players may not be seated. You may use this to turn off custom NPC logic.		#define grappleOnStart() // A grapple has been started but players may not be seated. You may use this to turn off custom NPC logic.
	#define grappleOnSeated() // All players are seated. You can now trigger animations! Get the players with gotMonsterGrapple$getTargs()		#define grappleOnSeated() // All players are seated. You can now trigger animations! Get the players with gotMonsterGrapple$getTargs()
Line 35:		Line 38:
	#define grappleOnButton(key victim_hud, bool success) // Used a classic QTE and the player hit a button		#define grappleOnButton(key victim_hud, bool success) // Used a classic QTE and the player hit a button
	#define grappleOnClientAnim(str npcAnim, list playerAnims) // Raised when client triggers an animation on the host. Raised on both host and client.		#define grappleOnClientAnim(str npcAnim, list playerAnims) // Raised when client triggers an animation on the host. Raised on both host and client.
	</pre>A basic way of doing it is something like this<pre>		</pre>

			A basic way of doing it is something like this

			<pre>
	#define grappleOnStart() grappleOnStart()		#define grappleOnStart() grappleOnStart()
	grappleOnStart(){		grappleOnStart(){

Panda: /* Setting up a grapple */

2024-04-06T00:40:31Z

Setting up a grapple

@@ Line 15: / Line 15: @@
 == Setting up a grapple ==
 If you want the monster to grapple one or more players. Note that this step is not needed if you only want your NPC to be a client for hookups.
 <pre>
@@ Line 26: / Line 28: @@
 #define cf$GRAPPLE_NO_QTE				// bool - No QTE. call grappleEnd manually
 #define cf$GRAPPLE_FAIL_TIMEOUT			// float - On failable grapples, wait this long before unsitting the player.
-</pre>
+</pre>Next you should define event handlers:<pre>

Panda: /* Setting up a grapple */

2024-04-06T00:38:05Z

Setting up a grapple

← Older revision		Revision as of 17:38, 5 April 2024
Line 16:		Line 16:
	If you want the monster to grapple one or more players. Note that this step is not needed if you only want your NPC to be a client for hookups.		If you want the monster to grapple one or more players. Note that this step is not needed if you only want your NPC to be a client for hookups.

	<~~code~~>		<pre>
	#define cf$GRAPPLE_FLAGS // int - Grapple settings flags. These are the flags used by got Evts quick time events to set things like left/right events.		#define cf$GRAPPLE_FLAGS // int - Grapple settings flags. These are the flags used by got Evts quick time events to set things like left/right events.
	#define cf$GRAPPLE_DURATION // float - Grapple max duration = 300. Max duration before force releasing the players.		#define cf$GRAPPLE_DURATION // float - Grapple max duration = 300. Max duration before force releasing the players.
Line 26:		Line 26:
	#define cf$GRAPPLE_NO_QTE // bool - No QTE. call grappleEnd manually		#define cf$GRAPPLE_NO_QTE // bool - No QTE. call grappleEnd manually
	#define cf$GRAPPLE_FAIL_TIMEOUT // float - On failable grapples, wait this long before unsitting the player.		#define cf$GRAPPLE_FAIL_TIMEOUT // float - On failable grapples, wait this long before unsitting the player.
	</~~code~~>		</pre>

Panda at 00:37, 6 April 2024

2024-04-06T00:37:46Z

← Older revision		Revision as of 17:37, 5 April 2024
Line 2:		Line 2:
	Here is a primer on how to use the system together with got LocalConf.NPC.template		Here is a primer on how to use the system together with got LocalConf.NPC.template

	Terminology:		=== Terminology ===

			* Grapple: A monster grabs one or more players, forcing them to sit on the object and is usually accompanied by a quick time event and some kind of status effect.
			* Quick time event: The keypad that pops up on your screen. Can be either "tap specific keys" or "tap left-right alternating". The alternating mode can also be set to allow fail.
			* Hookup: A quick time event where two monsters gang up on one player.
			* Hookup Host: The monster that grapples a player (PC) in a hookup.
			* Hookup Client: The monster that joins the host in a hookup.
			* Hostname: A unique identifier for the host that is used by the client to tell if they can join or not.

			Any NPC that should be able to grapple MUST have the optional got MonsterGrapple script in its inventory.

			== Setting up a grapple ==
			If you want the monster to grapple one or more players. Note that this step is not needed if you only want your NPC to be a client for hookups.

			<code>
			#define cf$GRAPPLE_FLAGS // int - Grapple settings flags. These are the flags used by got Evts quick time events to set things like left/right events.
			#define cf$GRAPPLE_DURATION // float - Grapple max duration = 300. Max duration before force releasing the players.
			#define cf$GRAPPLE_PREDELAY // float - Grapple predelay = 0. Time before starting the QTE after grapple starts.
			#define cf$GRAPPLE_BUTTON_DELAY // float - Grapple button delay = 0. Used in normal QTEs to set a delay before buttons.
			#define cf$GRAPPLE_STAGES // int - QTE stages, alternatively speed for quick grapples. = 30
			#define cf$GRAPPLE_MONSTERFLAGS // int - Monster to set when grapple starts and unset when it ends = Monster$RF_IMMOBILE\|Monster$RF_PACIFIED\|Monster$RF_NOROT\|Monster$RF_NO_SPELLS
			#define cf$GRAPPLE_STRIP // bool - Strip clothes during the grapple
			#define cf$GRAPPLE_NO_QTE // bool - No QTE. call grappleEnd manually
			#define cf$GRAPPLE_FAIL_TIMEOUT // float - On failable grapples, wait this long before unsitting the player.
			</code>

Panda: Created page with "GoThongs 2.3 introduced a dedicated grapple handler to help offload the hard-coded monster grapples that already exist. Here is a primer on how to use the system together with got LocalConf.NPC.template Terminology:"

2024-04-06T00:26:42Z

Created page with "GoThongs 2.3 introduced a dedicated grapple handler to help offload the hard-coded monster grapples that already exist. Here is a primer on how to use the system together with got LocalConf.NPC.template Terminology:"

New page

GoThongs 2.3 introduced a dedicated grapple handler to help offload the hard-coded monster grapples that already exist.
Here is a primer on how to use the system together with got LocalConf.NPC.template

Terminology: