General Overview - Revision history

Admin: /* Very Important Point */

2017-08-23T11:48:28Z

Very Important Point

@@ Line 237: / Line 237: @@
   With no welcome screen, nothing triggers, nothing loads.
   So, MAKE SURE, you ALWAYS quit properly, or when you re-connect you will be without ANY of the things setup in this package.
 =Speech Logging=

Admin: /* A good habit */

2017-08-23T11:45:38Z

A good habit

← Older revision		Revision as of 19:45, 23 August 2017
Line 278:		Line 278:
	=A good habit=		=A good habit=
	Check your character's specific config file every once in awhile to see if you've accidentally saved anything in there that should actually be in some other config		Check your character's specific config file every once in awhile to see if you've accidentally saved anything in there that should actually be in some other config

			If you find stuff in there that you think some other characters might want, this about where that should go instead.

	=Finding where stuff is set=		=Finding where stuff is set=

Admin: /* Very Important Point */

2017-08-23T11:44:24Z

Very Important Point

← Older revision		Revision as of 19:44, 23 August 2017
Line 234:		Line 234:
	This is because it all gets loaded by triggers setup on the Welcome screen.		This is because it all gets loaded by triggers setup on the Welcome screen.

	Turns out, if you dump out of realms without actual 'quit'ing, then the next time you connect, you skip the Welcome screen, nothing triggers, nothing loads.		Turns out, if you dump out of realms without actual 'quit'ing, then the next time you connect, you skip the Welcome screen.
			With no welcome screen, nothing triggers, nothing loads.
	So, MAKE SURE, you ALWAYS quit properly, or when you re-connect you will be without ANY of the things setup in this package.		So, MAKE SURE, you ALWAYS quit properly, or when you re-connect you will be without ANY of the things setup in this package.

Admin: /* Heal/Hit Triggers */

2017-08-23T11:43:16Z

Heal/Hit Triggers

← Older revision		Revision as of 19:43, 23 August 2017
Line 213:		Line 213:
	What the 'fighton' script really does is setup a trigger on all the attack messages "you stun" "you smash" "your circle" etc, which issues another 'ver'		What the 'fighton' script really does is setup a trigger on all the attack messages "you stun" "you smash" "your circle" etc, which issues another 'ver'
	This create a loop. ver -> heal -> ver -> (once healed) $hit $target -> (hit message) -> ver.... repeats forever.		This create a loop. ver -> heal -> ver -> (once healed) $hit $target -> (hit message) -> ver.... repeats forever.
	It's the hit message trigger that 'fighton' is enabling. Otherwise it stops ~~at that point~~.		It's the hit message trigger that 'fighton' is enabling. Otherwise the hit messages triggers nothing, and the loop stops.

	Sometimes it gets wonky and starts issuing too many 'version' commands to the mud. If things start to run-away from you, spam 'fightoff' until it stops.		Sometimes it gets wonky and starts issuing too many 'version' commands to the mud. If things start to run-away from you, spam 'fightoff' until it stops.

Admin: /* Heal/Hit Triggers */

2017-08-23T11:41:47Z

Heal/Hit Triggers

← Older revision		Revision as of 19:41, 23 August 2017
Line 176:		Line 176:

	Finally, also in basic_utilities.tin is the rudiment of my fight/heal triggers. These presume you use the same prompt as me:		Finally, also in basic_utilities.tin is the rudiment of my fight/heal triggers. These presume you use the same prompt as me:
	* Really all that matters is that the first portion is the same ((Dymrex) 1703/1703hp) after that can be your own custom ~~setup~~*		* Really all that matters is that the first portion is the same ((Dymrex) 1703/1703hp) after that can be your own custom prompt*
	Non-fighting prompt:		Non-fighting prompt:
	(Dymrex) 1703/1703hp 645/645mv $12,328,042 1000 HY		(Dymrex) 1703/1703hp 645/645mv $12,328,042 1000 HY
Line 187:		Line 187:

	If the alias 'fighton' is entered, it loads similar scripting (/newtin/scripts/fighton.tin) which fires on the fprompt		If the alias 'fighton' is entered, it loads similar scripting (/newtin/scripts/fighton.tin) which fires on the fprompt
	***again, only the first bit actually matters to trigger things after (Dymrex)F 1703/1703hp do what you want.		***again, only the first bit actually matters to trigger things after (Dymrex)F 1703/1703hp do what you want with your prompt.
	Fighting Prompt:		Fighting Prompt:
	(Dymrex)F 1703/1703hp 645/645mv $12,328,042 1000 HY		(Dymrex)F 1703/1703hp 645/645mv $12,328,042 1000 HY

Admin: /* Heal/Hit Triggers */

2017-08-23T11:41:30Z

Heal/Hit Triggers

← Older revision		Revision as of 19:41, 23 August 2017
Line 176:		Line 176:

	Finally, also in basic_utilities.tin is the rudiment of my fight/heal triggers. These presume you use the same prompt as me:		Finally, also in basic_utilities.tin is the rudiment of my fight/heal triggers. These presume you use the same prompt as me:
			* Really all that matters is that the first portion is the same ((Dymrex) 1703/1703hp) after that can be your own custom setup*
	Non-fighting prompt:		Non-fighting prompt:
	(Dymrex) 1703/1703hp 645/645mv $12,328,042 1000 HY		(Dymrex) 1703/1703hp 645/645mv $12,328,042 1000 HY
Line 186:		Line 187:

	If the alias 'fighton' is entered, it loads similar scripting (/newtin/scripts/fighton.tin) which fires on the fprompt		If the alias 'fighton' is entered, it loads similar scripting (/newtin/scripts/fighton.tin) which fires on the fprompt
			***again, only the first bit actually matters to trigger things after (Dymrex)F 1703/1703hp do what you want.
	Fighting Prompt:		Fighting Prompt:
	(Dymrex)F 1703/1703hp 645/645mv $12,328,042 1000 HY		(Dymrex)F 1703/1703hp 645/645mv $12,328,042 1000 HY

Admin: /* Important Usages when connected as such */

2017-08-23T11:38:30Z

Important Usages when connected as such

← Older revision		Revision as of 19:38, 23 August 2017
Line 90:		Line 90:

	All other scripst that get loaded or read will have headers/footers that do so under the "nowrite" class, so they don't get written out upon quit.		All other scripst that get loaded or read will have headers/footers that do so under the "nowrite" class, so they don't get written out upon quit.
	i.e. they stay in their original script, and don't end up in a specific char/class config.		i.e. they stay in their original script, and don't end up in a specific char/class config.

			Also, I never got the #split command to work correctly to give you a clean line to enter new text upon at the bottom of the terminal.
			If you see a bunch of #split stuff in scripts, it's all me attempting to put that at various points to make it work, and none of them work.
			So, I setup an alias 'line' you can use to give yourself a clean input line.
			However, a new problem is that this screws up the heal/hit triggers because it overwrites the prompt that stuff works upon.
			Solution is to actually switch to using the tintin prompt instead of the realms prompt. Kinda started that, but not ready yet.

	=Modules=		=Modules=

Admin: /* Heal/Hit Triggers */

2017-08-23T11:25:00Z

Heal/Hit Triggers

← Older revision		Revision as of 19:25, 23 August 2017
Line 197:		Line 197:
	I also have the actual text "SMAUG 2.1" replaced with 'AUTOFIGHTING' so I know this is enabled and working.		I also have the actual text "SMAUG 2.1" replaced with 'AUTOFIGHTING' so I know this is enabled and working.

	Upon printing the smaug version to screen, that triggers a fight/heal check that basically says:		Upon printing the output of 'ver' (smaug version) to screen, that triggers a fight/heal check that basically says:
	If damage is > 100, take a heal and rerun ver to check again.		If damage is > 100, take a heal and rerun ver to check again.
	If damage is < 100, issue $hit to $target.		If damage is < 100, issue $hit to $target.

	The $target variable is setup by either typing "k mob" "kil mob" or ~~trying~~ "targ MOBNAME" or upon someone in the room saying "targ MOBNAME"		The $target variable is setup by either typing "k mob" "kil mob" or typing "targ MOBNAME" or upon someone in the room saying "targ MOBNAME"
	The $hit variable is ~~contaned~~ in each CLASS config file.		The $hit variable is contained in each CLASS config file.

			What the 'fighton' script really does is setup a trigger on all the attack messages "you stun" "you smash" "your circle" etc, which issues another 'ver'
			This create a loop. ver -> heal -> ver -> (once healed) $hit $target -> (hit message) -> ver.... repeats forever.
			It's the hit message trigger that 'fighton' is enabling. Otherwise it stops at that point.

	Sometimes it gets wonky and starts issuing too many 'version' commands to the mud. If things start to run-away from you, spam 'fightoff' until it stops.		Sometimes it gets wonky and starts issuing too many 'version' commands to the mud. If things start to run-away from you, spam 'fightoff' until it stops.

			It's also IMPORTANT to note that the 'ver' trigger is ALWAYS ON.
			That means that at ANY POINT if you run ver, your character is going to check it's HP and either heal or $hit $target.
			However, it will not LOOP and continue hitting/healing unless you run 'fighton' first. But so, it's always available as a 'one-off'.
			(Make sure you've setup $hit, $target, $pot_con variable or this will just error a bunch and may runaway)


Line 213:		Line 222:
	Char2: say 'fightoff'		Char2: say 'fightoff'
	(Char1 disables fight triggers, and stops healing/hitting)		(Char1 disables fight triggers, and stops healing/hitting)


	=Very Important Point=		=Very Important Point=

Admin: /* Things you need to set for this to run properly */

2017-08-23T11:20:26Z

Things you need to set for this to run properly

← Older revision		Revision as of 19:20, 23 August 2017
Line 248:		Line 248:
	pot_con		pot_con
	(new scripting needs written for non-dragonslayer containers/heals/recalls... or manually set)		(new scripting needs written for non-dragonslayer containers/heals/recalls... or manually set)
			#var item_con CONTAINER
			#var pot_con CONTAINER
			(Obviously, you might use the same container for both things, that's fine)
	hit		hit
	(this is written into newtin/classes/CLASSNAME_classconfig.tin)		(this is written into newtin/classes/CLASSNAME_classconfig.tin)

Admin: /* Things you need to set for this to run properly */

2017-08-23T11:19:33Z

Things you need to set for this to run properly

← Older revision		Revision as of 19:19, 23 August 2017
Line 242:		Line 242:

	=Things you need to set for this to run properly=		=Things you need to set for this to run properly=
			PASSWORD: set your password inside newtin/main.tin (you must use the same pword for ALL characters)

	Variables:		Variables:
Line 255:		Line 256:
	(upon quitting that variable gets written to your class config and you shouldn't have to set it again. Can always reset/change it with the 'hitis X' alias.		(upon quitting that variable gets written to your class config and you shouldn't have to set it again. Can always reset/change it with the 'hitis X' alias.
	charwrite (re-open character specific class, my preferred default setup)		charwrite (re-open character specific class, my preferred default setup)


	=A good habit=		=A good habit=