Sightglass at 07:39, 14 March 2024

2024-03-14T07:39:19Z

← Older revision		Revision as of 07:39, 14 March 2024
Line 1:		Line 1:
	LT's parser takes in text from mods and resource files, executes scripts to perform game actions or retrieve information, applies formatting, and outputs text marked up with html to display onto the game screen.		LT's parser takes in text from mods and resource files, executes scripts to perform game actions or retrieve information, applies formatting, and outputs text marked up with html to display onto the game screen.

			Modders will definitely want to read the [[#Scripting]] section.

	''See also for reference: [[Parser Command Reference]] and [[Parser Target and Binding Reference]]''		''See also for reference: [[Parser Command Reference]] and [[Parser Target and Binding Reference]]''

Sightglass: Add see-also

2024-03-14T07:36:03Z

Add see-also

← Older revision		Revision as of 07:36, 14 March 2024
Line 1:		Line 1:
	LT's parser takes in text from mods and resource files, executes scripts to perform game actions or retrieve information, applies formatting, and outputs text marked up with html to display onto the game screen.		LT's parser takes in text from mods and resource files, executes scripts to perform game actions or retrieve information, applies formatting, and outputs text marked up with html to display onto the game screen.

			''See also for reference: [[Parser Command Reference]] and [[Parser Target and Binding Reference]]''

	== In-Game Guide ==		== In-Game Guide ==

Sightglass: Prepare headings for scripting section

2024-03-14T07:34:20Z

Prepare headings for scripting section

← Older revision		Revision as of 07:34, 14 March 2024
Line 53:		Line 53:
	Dialogue written by Innoxia for <i>Lilith’s Throne v0.4.9</i>		Dialogue written by Innoxia for <i>Lilith’s Throne v0.4.9</i>
	</p>		</p>
			== Scripting ==
			=== Flow Control ===
			=== Using var ===
	[[Category:Modding Guides]]		[[Category:Modding Guides]]

Sightglass: Added contents of in-game guide

2024-03-14T07:32:25Z

Added contents of in-game guide

← Older revision		Revision as of 07:32, 14 March 2024
Line 1:		Line 1:
	~~[WIP: Primer on how~~ LT's parser works]		LT's parser takes in text from mods and resource files, executes scripts to perform game actions or retrieve information, applies formatting, and outputs text marked up with html to display onto the game screen.

			== In-Game Guide ==
			'''''The following is taken from the parser help scene in the game's debug menu:'''''
			<h4 style="text-align:center; font-size:1.4em;">
			Innoxia’s super fun and interesting guide to parsing
			</h4>
			<p style="text-align:center;">
			<i>You put in the input, and it returns a nice output!</i>
			</p>
			<p>
			<h6>
			Input:
			</h6>
			<br/>Everything is parsed using square brackets, split into the following pattern:<br/>[<i style='color:#72cfe3;'>target</i>.<i style='color:#f4b3f4;'>command</i>]<br/>or, for the few special commands that require arguments:<br/>[<i style='color:#72cfe3;'>target</i>.<i style='color:#f4b3f4;'>command</i><i style='color:#e2c360;'>(arguments)</i>]<br/>or, for parsing as a script:<br/>[#<i style='color:#f4b3f4;'>command</i>]<br/>or, for parsing as a script which suppresses output:<br/>[##<i style='color:#f4b3f4;'>command</i>]<br/><i>(This means that the command will be executed, but no String output will be displayed.)</i>
			</p>
			<p>
			An example of use in a sentence would be:<br/><br/><i>As you start to read Innoxia’s tedious parsing documentation, [lilaya.name] steps up behind you and wraps [lilaya.her] [lilaya.tail+] around your [pc.leg]. Leaning in over your shoulder, [lilaya.she] groans, [lilaya.speech(Oh my God. This is so boring, [#pc.getName(true)]!)]’</i><br/><br/>parses to:<br/><br/>As you start to read Innoxia’s tedious parsing documentation, Lilaya steps up behind you and wraps her thick tail around your legs. Leaning in over your shoulder, she groans, <span class="speech" style="color:#ff66a3;">Oh my God. This is so boring, Vivian!</span>
			</p>
			<br/>
			<h6>
			<b style='color:#72cfe3;'>Target</b> <b>tag:</b>
			</h6>
			<p>
			The target of a command is an NPC’s name, or ‘pc’ for the player character. Target tags are <b>case-insensitive.</b> (i.e. pc is treated the same as PC, pC, or Pc)<br/> If an unrecognised name is passed, the output will read ‘INVALID_TARGET_NAME’.<br/> Currently accepted target tags can be viewed in the ‘Targets’ page.<br/>e.g.:<br/>[<i style='color:#72cfe3;'>lilaya</i>.command]<br/>[<i style='color:#72cfe3;'>pc</i>.command(arguments)]<br/>[<i style='color:#72cfe3;'>npc</i>.command]
			</p>
			<br/>
			<h6>
			<b style='color:#f4b3f4;'>Command</b> <b>and</b> <b style='color:#e2c360;'>argument</b> <b>tags:</b>
			</h6>
			<p>
			Command tags determine what output is returned. They come in two varieties; with and without arguments.<br/>Arguments are passed inside brackets that follow the command, ignoring any spaces that you may insert.<br/>i.e. [pc.command(arguments)] is the same as [pc.command (arguments)].<br/>Command tags are <b>only case-sensitive for the first letter</b>. (i.e. command is treated the same as cOMMAND, cOmMaNd, or commanD)<br/>Arguments are specific to each command, and you’ll have to refer to the command documentation to find out what arguments a command takes. (Don’t worry, there aren’t many that take arguments.)<br/>e.g.:<br/>[pc.speech<i style='color:#e2c360;'>(Hello reader!)</i>] outputs <span class="speech" style="color:#ff85ff;">Hello reader!</span>
			</p>
			<p>
			<b>Command modifier (a_ an_)</b><br/>You may insert ‘a_’ or ‘an_’ to automatically generate the appropriate pronoun before an argument. (It’s your choice if you prefer a_ or an_, they both work in exactly the same way.)<br/>e.g.:<br/>[npc.<i style='color:#f4b3f4;'>height</i>] outputs ‘tall’<br/>[npc.<i style='color:#f4b3f4;'>a_height</i>] outputs ‘a tall’<br/>[npc.<i style='color:#f4b3f4;'>an_height</i>] <b>also</b> outputs ‘a tall’<br/><br/>For some body part names, this provides a little more complexity.<br/>e.g.:<br/>[npc.<i style='color:#f4b3f4;'>arms</i>] outputs ‘wings’<br/>[npc.<i style='color:#f4b3f4;'>a_arms</i>] outputs ‘a pair of wings’<br/>[npc.<i style='color:#f4b3f4;'>an_arms</i>] <b>also</b> outputs ‘a pair of wings’<br/><br/>
			</p>
			<p>
			<b>Command modifier (Capitalisation)</b><br/>Most commands are able to apply capitalisation. The ones that don’t, such as numeric output commands, will still happily take a capitalised command, but capitalisation won’t be applied.<br/>To capitalise an output, all you have to do is capitalise <b>the first letter</b> of the command name.<br/>e.g.:<br/>[npc.<i style='color:#f4b3f4;'>height</i>] outputs ‘tall’<br/>[npc.<i style='color:#f4b3f4;'>hEIGHT</i>] <b>also</b> outputs ‘tall’ (I’m sure nobody would ever do this…)<br/>[npc.<i style='color:#f4b3f4;'>Height</i>] outputs ‘Tall’<br/>[npc.<i style='color:#f4b3f4;'>a_height</i>] outputs ‘a tall’<br/>[npc.<i style='color:#f4b3f4;'>A_height</i>] outputs ‘A tall’<br/>[npc.<i style='color:#f4b3f4;'>a_Height</i>] <b>also</b> outputs ‘A tall’<br/><br/>
			<p>
			<b>Command modifier (+ D)</b><br/>Most commands that return a name are able to apply additional <b>randomised descriptors</b>. (You can check to see what commands accept ‘+’ and ‘D’ modifiers in the ‘Commands’ page.)<br/>To apply additional descriptors to the returned output, all you have to do is add a ‘+’, ‘d’, or ‘D’ to the end of the command.<br/><b>This works in combination with ‘a_ an_’ and ‘Capitalisation’ modifiers.</b><br/>e.g.:<br/>[npc.<i style='color:#f4b3f4;'>arms</i>] outputs ‘wings’<br/>[npc.<i style='color:#f4b3f4;'>arms+</i>] outputs ‘feathered wings’<br/>[npc.<i style='color:#f4b3f4;'>armsD</i>] <b>also</b> outputs ‘feathered wings’<br/>[npc.<i style='color:#f4b3f4;'>armsd</i>] <b>also</b> outputs ‘feathered wings’<br/>[npc.<i style='color:#f4b3f4;'>ArmsD</i>] outputs ‘Feathered wings’<br/>[npc.<i style='color:#f4b3f4;'>a_arms+</i>] outputs ‘a pair of feathered wings’<br/>[npc.<i style='color:#f4b3f4;'>A_arms+</i>] outputs ‘A pair of feathered wings’<br/><br/>Some outputs have more randomisation than others.<br/>e.g.:<br/>[npc.<i style='color:#f4b3f4;'>pussy</i>] outputs ‘slit’<br/>[npc.<i style='color:#f4b3f4;'>pussy</i>] outputs ‘cunt’<br/>[npc.<i style='color:#f4b3f4;'>pussy+</i>] outputs ‘wet pussy’<br/>[npc.<i style='color:#f4b3f4;'>pussy+</i>] outputs ‘tentacle-lined twat’<br/>
			</p>
			<h6>
			Conclusion:
			</h6>
			<p>
			<b>Valid</b> command syntax:<br/>[<i style='color:#72cfe3;'>target</i>.<i style='color:#f4b3f4;'>command</i>]<br/>or<br/>[<i style='color:#72cfe3;'>target</i>.<i style='color:#f4b3f4;'>command</i><i style='color:#e2c360;'>(arguments)</i>]<br/><br/><br/>
			<h6>
			Examples:
			</h6>
			<br/>[<i style='color:#72cfe3;'>brax</i>.<i style='color:#f4b3f4;'>name</i>] leans back in [<i style='color:#72cfe3;'>brax</i>.<i style='color:#f4b3f4;'>his</i>] chair, wondering what happened to [<i style='color:#72cfe3;'>arthur</i>.<i style='color:#f4b3f4;'>name</i>] after [<i style='color:#72cfe3;'>brax</i>.<i style='color:#f4b3f4;'>he</i>] handed [[<i style='color:#72cfe3;'>arthur</i>.<i style='color:#f4b3f4;'>him</i>]] over to Scarlett.<br/>outputs:<br/>‘Brax leans back in his chair, wondering what happened to Arthur after he handed him over to Scarlett.’<br/><br/>[<i style='color:#72cfe3;'>rose</i>.<i style='color:#f4b3f4;'>name</i>] leans back in [<i style='color:#72cfe3;'>rose</i>.<i style='color:#ea5d76;'>herHuis</i>] chair, letting out a sigh as [<i style='color:#72cfe3;'>rose</i>.<i style='color:#ea5d76;'>shyeHe</i>] takes a sip of [<i style='color:#72cfe3;'>rose</i>.<i style='color:#f4b3f4;'>name</i>] coffee.<br/>outputs:<br/>Rose leans back in <i style='color:#ea5d76;'>command_unknown</i> chair, letting out a sigh as <i style='color:#ea5d76;'>command_unknown</i> takes a sip of Rose coffee.<br/><b>Note:</b> <i style='color:#ea5d76;'>Typos</i> will cause the parsing system to return an invalid command string, whereas <i style='color:#f4b3f4;'>incorrect commands</i> (such as typing .name instead of .herHis) will not throw an error!<br/><br/>[<i style='color:#72cfe3;'>lilaya</i>.<i style='color:#f4b3f4;'>name</i>] storms up to [<i style='color:#72cfe3;'>innoxia</i>.<i style='color:#f4b3f4;'>name</i>], shouting angrily in response to finding out that [<i style='color:#72cfe3;'>lilaya</i>.<i style='color:#f4b3f4;'>her</i>] sex scenes haven’t been fixed yet, [<i style='color:#72cfe3;'>lilaya</i>.<i style='color:#f4b3f4;'>speech</i><i style='color:#e2c360;'>(What the hell are you doing Innoxia?! You said my scenes were going to be re-written weeks ago!)</i>]<br/>outputs:<br/>‘Lilaya storms up to Innoxia, shouting angrily in response to finding out that her sex scenes haven’t been fixed yet, <span class="speech" style="color:#ff66a3;">What the hell are you doing Innoxia?! You said my scenes were going to be re-written weeks ago!</span>’
			</p>
			<p style="text-align:center;font-size:0.6em;color:#777;">
			Dialogue written by Innoxia for <i>Lilith’s Throne v0.4.9</i>
			</p>

	[[Category:Modding Guides]]		[[Category:Modding Guides]]

Sightglass: Add Modding Guide category tag

2024-02-21T05:43:59Z

Add Modding Guide category tag

← Older revision		Revision as of 05:43, 21 February 2024
Line 1:		Line 1:
	[WIP: Primer on how LT's parser works]		[WIP: Primer on how LT's parser works]
			[[Category:Modding Guides]]

Sightglass: Page created

2024-02-21T05:38:32Z

Page created

Páàjì titun