Lich scripting reference - Revision history

TK-421: StormFront to Wrayth

2022-02-03T21:29:10Z

StormFront to Wrayth

← Older revision		Revision as of 16:29, 3 February 2022
Line 4:		Line 4:
	[http://ruby-gnome2.sourceforge.jp/ GTK bindings] to create GUIs.		[http://ruby-gnome2.sourceforge.jp/ GTK bindings] to create GUIs.

	If you are more comfortable with ~~StormFront~~ and Wizard scripts, Lich can run most of them unaltered, but since Lich is running them, you can have any number of them running simultaneously. Lich is highly compatible with ~~StormFront~~/Wizard scripts, so you can use your existing scripts and scripting experience when writing Lich scripts.		If you are more comfortable with Wrayth and Wizard scripts, Lich can run most of them unaltered, but since Lich is running them, you can have any number of them running simultaneously. Lich is highly compatible with Wrayth/Wizard scripts, so you can use your existing scripts and scripting experience when writing Lich scripts.

	=Running a Script=		=Running a Script=
Line 68:		Line 68:

	=Commands that work in DR=		=Commands that work in DR=
	==~~Stormfront~~-like commands==		==Wrayth-like commands==
	===put===		===put===
	<pre style="overflow:hidden;">		<pre style="overflow:hidden;">
Line 332:		Line 332:
	</pre>		</pre>
	*'''Returns:''' true/false or an integer		*'''Returns:''' true/false or an integer
	*'''Description:''' Only in ~~StormFront~~ (there is no auto-updated stamina tag in Wizard). Given no arguments, returns your current stamina. Given a number, returns true/false based on whether you have at least or more than that number.		*'''Description:''' Only in Wrayth (there is no auto-updated stamina tag in Wizard). Given no arguments, returns your current stamina. Given a number, returns true/false based on whether you have at least or more than that number.

	===watchhealth===		===watchhealth===

LUNARIMP: /* bput */

2020-07-25T16:22:10Z

bput

← Older revision		Revision as of 11:22, 25 July 2020
Line 82:		Line 82:
	*'''Returns:''' the string that was accepted as meaning the action succeeded (see below)		*'''Returns:''' the string that was accepted as meaning the action succeeded (see below)
	*'''Synonyms:''' blocking put		*'''Synonyms:''' blocking put
	*'''Description:''' Part of the common helper ~~fucntions~~ for actions in scripts. It's named 'blocking put' is designed to be a more robust version of fput in situations where you know the desired response from the game. Unlike fput which will resend the same command repeatedly until it sees the desired message first from the game, bput only sends a given command one time (unless round time or type ahead errors occur) and then waits for the desired response. if the desired response isn't seen bput will eventually time out and echo debugging information. The command (fput "forage grass", 'Roundtime') would never work because the game sends a response line "You search around..." before "Roundtime" is encountered. Similarly a command that can only succeed once can cause fput to hang. In this case, you have to deal with the failure case and just spam the command until failure in a noisy room with fput (fput "get box", 'you pick up', 'get what?'). To get around all of this you can use bput to ensure that the command is matching (ex. bput "get box", 'you pick up', 'get what?'). It puts in the command and then waits until a successful match.		*'''Description:''' Part of the common helper functions for actions in scripts. It's named 'blocking put' is designed to be a more robust version of fput in situations where you know the desired response from the game. Unlike fput which will resend the same command repeatedly until it sees the desired message first from the game, bput only sends a given command one time (unless round time or type ahead errors occur) and then waits for the desired response. if the desired response isn't seen bput will eventually time out and echo debugging information. The command (fput "forage grass", 'Roundtime') would never work because the game sends a response line "You search around..." before "Roundtime" is encountered. Similarly a command that can only succeed once can cause fput to hang. In this case, you have to deal with the failure case and just spam the command until failure in a noisy room with fput (fput "get box", 'you pick up', 'get what?'). To get around all of this you can use bput to ensure that the command is matching (ex. bput "get box", 'you pick up', 'get what?'). It puts in the command and then waits until a successful match.

	===fput===		===fput===

LUNARIMP: /* Commands that work in DR */

2020-07-25T16:15:09Z

Commands that work in DR

← Older revision		Revision as of 11:15, 25 July 2020
Line 83:		Line 83:
	*'''Synonyms:''' blocking put		*'''Synonyms:''' blocking put
	*'''Description:''' Part of the common helper fucntions for actions in scripts. It's named 'blocking put' is designed to be a more robust version of fput in situations where you know the desired response from the game. Unlike fput which will resend the same command repeatedly until it sees the desired message first from the game, bput only sends a given command one time (unless round time or type ahead errors occur) and then waits for the desired response. if the desired response isn't seen bput will eventually time out and echo debugging information. The command (fput "forage grass", 'Roundtime') would never work because the game sends a response line "You search around..." before "Roundtime" is encountered. Similarly a command that can only succeed once can cause fput to hang. In this case, you have to deal with the failure case and just spam the command until failure in a noisy room with fput (fput "get box", 'you pick up', 'get what?'). To get around all of this you can use bput to ensure that the command is matching (ex. bput "get box", 'you pick up', 'get what?'). It puts in the command and then waits until a successful match.		*'''Description:''' Part of the common helper fucntions for actions in scripts. It's named 'blocking put' is designed to be a more robust version of fput in situations where you know the desired response from the game. Unlike fput which will resend the same command repeatedly until it sees the desired message first from the game, bput only sends a given command one time (unless round time or type ahead errors occur) and then waits for the desired response. if the desired response isn't seen bput will eventually time out and echo debugging information. The command (fput "forage grass", 'Roundtime') would never work because the game sends a response line "You search around..." before "Roundtime" is encountered. Similarly a command that can only succeed once can cause fput to hang. In this case, you have to deal with the failure case and just spam the command until failure in a noisy room with fput (fput "get box", 'you pick up', 'get what?'). To get around all of this you can use bput to ensure that the command is matching (ex. bput "get box", 'you pick up', 'get what?'). It puts in the command and then waits until a successful match.


	===fput===		===fput===

LUNARIMP: /* Commands that work in DR */

2020-07-25T16:14:52Z

Commands that work in DR

← Older revision		Revision as of 11:14, 25 July 2020
Line 75:		Line 75:
	*'''Returns:''' the string that was sent		*'''Returns:''' the string that was sent
	*'''Description:''' Identical to Wizard.		*'''Description:''' Identical to Wizard.

			===bput===
			<pre style="overflow:hidden;">
			bput "get box", 'you pick up', 'get what?'
			</pre>
			*'''Returns:''' the string that was accepted as meaning the action succeeded (see below)
			*'''Synonyms:''' blocking put
			*'''Description:''' Part of the common helper fucntions for actions in scripts. It's named 'blocking put' is designed to be a more robust version of fput in situations where you know the desired response from the game. Unlike fput which will resend the same command repeatedly until it sees the desired message first from the game, bput only sends a given command one time (unless round time or type ahead errors occur) and then waits for the desired response. if the desired response isn't seen bput will eventually time out and echo debugging information. The command (fput "forage grass", 'Roundtime') would never work because the game sends a response line "You search around..." before "Roundtime" is encountered. Similarly a command that can only succeed once can cause fput to hang. In this case, you have to deal with the failure case and just spam the command until failure in a noisy room with fput (fput "get box", 'you pick up', 'get what?'). To get around all of this you can use bput to ensure that the command is matching (ex. bput "get box", 'you pick up', 'get what?'). It puts in the command and then waits until a successful match.


	===fput===		===fput===

ABSOLON: ABSOLON moved page Lich Scripting Reference to Lich scripting reference

2016-06-04T03:12:23Z

ABSOLON moved page Lich Scripting Reference to Lich scripting reference

← Older revision	Revision as of 22:12, 3 June 2016
(No difference)

ABSOLON at 02:46, 4 June 2016

2016-06-04T02:46:47Z

← Older revision		Revision as of 21:46, 3 June 2016
Line 699:		Line 699:


	{{cat\|Scripts,Lich settings,Lich scripts}}		{{cat\|Settings,Scripts,Lich settings,Lich scripts}}

ABSOLON at 02:44, 4 June 2016

2016-06-04T02:44:17Z

← Older revision		Revision as of 21:44, 3 June 2016
Line 699:		Line 699:


	{{cat\|Scripts,Lich settings}}		{{cat\|Scripts,Lich settings,Lich scripts}}

ABSOLON at 02:41, 4 June 2016

2016-06-04T02:41:01Z

← Older revision		Revision as of 21:41, 3 June 2016
Line 699:		Line 699:


	~~[[Category:~~Scripts]]		{{cat\|Scripts,Lich settings}}

Maintenance script: organized commands by theme, removed duplicate undo_before_dying

2013-08-05T22:54:17Z

organized commands by theme, removed duplicate undo_before_dying

Show changes

Maintenance script: separated commands that don't work in DR

2013-08-01T02:58:23Z

separated commands that don't work in DR

Show changes