Text (Asset) - Revision history

JasX at 13:28, 8 August 2025

2025-08-08T13:28:40Z

← Older revision		Revision as of 13:28, 8 August 2025
Line 317:		Line 317:

	== Using mathVars in texts ==		== Using mathVars in texts ==
	For non-player specific math vars, such as numbers, you just prepend the math var label with @. Note ~~that~~ only ~~global math vars are available~~ in the text itself, you ~~can still~~ use ~~player specific ones in conditions~~.		For non-player specific math vars, such as numbers, you just prepend the math var label with @.

			* ''Note: Using @ to refer to a math var is only used in the text itself. Inside of formulas, you should just use the math var as is, without prefixing @.''

	If you need player-specific math vars, then see [[Math]] for a primer on the FQ math system.		If you need player-specific math vars, then see [[Math]] for a primer on the FQ math system.

JasX at 13:18, 8 August 2025

2025-08-08T13:18:48Z

← Older revision		Revision as of 13:18, 8 August 2025
Line 320:		Line 320:

	If you need player-specific math vars, then see [[Math]] for a primer on the FQ math system.		If you need player-specific math vars, then see [[Math]] for a primer on the FQ math system.

			== Using formulas in texts ==
			Use the syntax <code>@{formula}</code>. Such as <code>@{d_dungeonName_dungeonVar*3}</code>.

JasX: /* Using mathVars in texts */

2025-03-25T12:18:59Z

Using mathVars in texts

← Older revision		Revision as of 12:18, 25 March 2025
Line 317:		Line 317:

	== Using mathVars in texts ==		== Using mathVars in texts ==
	~~See~~ [[Math]] for a primer on the FQ math system~~. You can use mathvars in texts~~.		For non-player specific math vars, such as numbers, you just prepend the math var label with @. Note that only global math vars are available in the text itself, you can still use player specific ones in conditions.

			If you need player-specific math vars, then see [[Math]] for a primer on the FQ math system.

JasX at 14:09, 22 March 2025

2025-03-22T14:09:09Z

← Older revision		Revision as of 14:09, 22 March 2025
Line 33:		Line 33:
	\|Tags		\|Tags
	\|Sets temporary tags on a the recipient of the text. These will be wiped on the player's next turn. Can be used to add texts that refer to previous texts. Such as if a text triggers that bends the target over, you can set the tt_bent_over text, and then use a condition in the other text such as "ttBentOver" to add a text that assumes that the player was already bent over. It's a bit complicated, and not frequently used. Turn tags start with tt_		\|Sets temporary tags on a the recipient of the text. These will be wiped on the player's next turn. Can be used to add texts that refer to previous texts. Such as if a text triggers that bends the target over, you can set the tt_bent_over text, and then use a condition in the other text such as "ttBentOver" to add a text that assumes that the player was already bent over. It's a bit complicated, and not frequently used. Turn tags start with tt_
			\|-
			\|Target Tags
			\|Tags
			\|'''Used in RP only.''' Tags applied to the text target while on a roleplay stage. Can be used to trigger facial expressions and such. Checking persistent persists the tags until the next time a stage text with at least 1 Target Tags is set, or the roleplay ends. Note that Persistent OVERWRITES previously persistent tags, it's not additive.
			\|-
			\|
			\|
			\|Same as target tags, but for the sender(s).
	\|-		\|-
	\|Meta Tags		\|Meta Tags

JasX at 12:54, 20 February 2025

2025-02-20T12:54:38Z

← Older revision		Revision as of 12:54, 20 February 2025
Line 1:		Line 1:
			This is the asset reference, you can find a tutorial [[Creating a Text\|here]].
	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+

JasX: /* Using mathVars in texts */

2025-02-18T00:06:05Z

Using mathVars in texts

← Older revision		Revision as of 00:06, 18 February 2025
Line 308:		Line 308:

	== Using mathVars in texts ==		== Using mathVars in texts ==
			See [[Math]] for a primer on the FQ math system. You can use mathvars in texts.

JasX at 00:00, 18 February 2025

2025-02-18T00:00:16Z

Show changes

JasX at 23:05, 17 February 2025

2025-02-17T23:05:32Z

@@ Line 72: / Line 72: @@
 |Int
 |Nr of minimum extra senders that need to match extra sender conditions in order for this text to be triggered.
 |}

JasX at 22:56, 17 February 2025

2025-02-17T22:56:38Z

@@ Line 36: / Line 36: @@
 |Tags
 |These tags describe the text (generally for the victim). And are mainly used in kinks and for NPC speech. Go through the list and tag anything you feel applies.
 |-
 |Armor Slot

JasX at 22:49, 17 February 2025

2025-02-17T22:49:26Z

← Older revision		Revision as of 22:49, 17 February 2025
Line 1:		Line 1:
	~~Todo~~.		{\| class="wikitable"
			\|+
			!Field
			!Type
			!Description
			\|-
			\|Text
			\|String
			\|The text to generate. See below for tags you can use.
			\|-
			\|Enabled
			\|Boolean
			\|Only affects texts in the texts database (so not RP etc). Required checked if you want the text to be included in the combat log.
			\|-
			\|Nr Targets
			\|Int
			\|Nr targets REQUIRED to trigger this text. Generally used in custom texts with abilities that can have multiple targets. When making combat texts, make sure there's at least one 1 target text. Conditions are checked against ALL targets and must match. Use -1 for ANY amount of target. -1 is mainly useful for AoE where you only want to have one text.
			\|-
			\|Weight
			\|Float
			\|Lets you increase the chance of a text to show up. If you have a lot of conditions, you may want to increase it. Otherwise I suggest simply leaving it at default (in the middle).
			\|-
			\|Conditions
			\|[[Condition (Asset)]]
			\|Conditions required to trigger this text.
			\|-
			\|Condition Templates
			\|N/A
			\|You can use this to quickly add commonly used conditions. Such as if you want your text to be output when an action is used, and if the action was used by a humanoid on a humanoid you can click Humanoid on Humanoid to quickly add the: actionHit, eventIsActionUsed, senderNotBeast, and targetNotBeast conditions.
			\|-
			\|Turn Tags
			\|Tags
			\|Sets temporary tags on a the recipient of the text. These will be wiped on the player's next turn. Can be used to add texts that refer to previous texts. Such as if a text triggers that bends the target over, you can set the tt_bent_over text, and then use a condition in the other text such as "ttBentOver" to add a text that assumes that the player was already bent over. It's a bit complicated, and not frequently used. Turn tags start with tt_
			\|-
			\|Meta Tags
			\|Tags
			\|These tags describe the text (generally for the victim). And are mainly used in kinks and for NPC speech. Go through the list and tag anything you feel applies.
			\|-
			\|Armor Slot
			\|String
			\|If your attack targets armor, mark that here. It's used to trigger the correct sounds, for an instance a clunk if the victim takes a punch to the chest while wearing plate armor.
			\|-
			\|Audio Kits
			\|[[Audio Kit (Asset)]]
			\|Plays audio when the text is triggered. Note: HitFX includes audio. Only pick Audio Kits here if you want to add additional sounds to a HitFX object, or if you want to play audio without triggering a HitFX.
			\|-
			\|HitFX
			\|[[HitFX (Asset)]]
			\|Selected HitFX will be triggered when the text triggers.
			\|-
			\|Debug
			\|Boolean
			\|Outputs logging information into the console whenever the text's conditions are checked. Leave it unchecked unless you're working on a fork of FQ.
			\|-
			\|Extra senders
			\|[[Condition (Asset)]]
			\|If left empty, extra senders are ignored. This is if you want to include another player as an extra "attacker" in your text. These extra attackers get the tags %A, %A2... Any players that match the specified conditions will be put into a list, and the first min_extra_senders nr of players will be used. Can be used for texts where two enemies double team a player. Consider not using this for player on NPC attacks. Also note that this is only for flavor, the extra sender doesn't affect combat at all. Click the Add Defaults button to add some suggested conditions.
			\|-
			\|Min extra senders
			\|Int
			\|Nr of minimum extra senders that need to match extra sender conditions in order for this text to be triggered.
			\|}