Mud Client Ideas - Revision history

Admin: /* Equipment Damage Tracking */

2024-04-21T13:19:19Z

Equipment Damage Tracking

← Older revision		Revision as of 21:19, 21 April 2024
Line 123:		Line 123:
	}		}
	}		}
	<pre>		</pre>

	So then a trigger for {* get's damaged!!} does something like: foreach item in the 'eqlist' var, regex that item name against the * that got hit, upon match, reduce the items AC by 1, and if AC is now < 3 remove the item by its key word.		So then a trigger for {* get's damaged!!} does something like: foreach item in the 'eqlist' var, regex that item name against the * that got hit, upon match, reduce the items AC by 1, and if AC is now < 3 remove the item by its key word.



	=Map=		=Map=

Admin: /* Autofight */

2023-05-29T07:33:38Z

Autofight

← Older revision		Revision as of 15:33, 29 May 2023
Line 95:		Line 95:
	Making macros for hit, heal, drink spring is really a huge help itself, punching 3 keys as you watch the fight makes things a lot less hectic.		Making macros for hit, heal, drink spring is really a huge help itself, punching 3 keys as you watch the fight makes things a lot less hectic.

	Setting up a trigger on something like your hit message would also work of course, if you are too lazy to punch buttons.		Setting up a trigger on something like your hit message would also work of course, if you are (like me) too lazy to even punch buttons.

	=GUI=		=GUI=

Admin: /* MSDP */

2023-05-29T07:32:03Z

MSDP

← Older revision		Revision as of 15:32, 29 May 2023
Line 71:		Line 71:
	=MSDP=		=MSDP=

	Use a modern client that can receive MSDP variables from the mud. You will automatically have variables for your hp, room names, stats, everything. It makes it very easy to script stuff based on all those values.		Use a modern client that can receive MSDP variables from the mud. You will automatically have variables for your hp, room names, stats, everything. It makes it very easy to script stuff based on all those values.

			I use tintin++ and have a MSDP script for that here: [[MSDP Script]]

	=Autofight=		=Autofight=

Admin at 13:37, 28 December 2022

2022-12-28T13:37:17Z

← Older revision		Revision as of 21:37, 28 December 2022
Line 1:		Line 1:
	So you think you're some kinda Power User huh? More like Power Loser amiright?!?!?!?!		So you think you're some kinda Power User huh? More like Power Loser amiright?!?!?!?!

	This page is meant to give new players an idea of the scope of what~~'s needed to really play the game well~~.		This page is meant to give new players an idea of the scope of what people are actually doing client-side.

	I have a buddy who says 'So that game sucks and before you can play it you first have to play the game of 'how do I code my client to make this actually playable'. He's kinda not wrong.		I have a buddy who says 'So that game sucks and before you can play it you first have to play the game of 'how do I code my client to make this actually playable'. He's kinda not wrong.

Admin: Admin moved page Power User Guide to Mud Client Ideas

2022-12-28T13:36:28Z

Admin moved page Power User Guide to Mud Client Ideas

← Older revision	Revision as of 21:36, 28 December 2022
(No difference)

Admin at 13:34, 28 December 2022

2022-12-28T13:34:58Z

← Older revision		Revision as of 21:34, 28 December 2022
Line 3:		Line 3:
	This page is meant to give new players an idea of the scope of what's needed to really play the game well.		This page is meant to give new players an idea of the scope of what's needed to really play the game well.

	~~Here~~'~~s things~~ the ~~uber-nerds who play this~~ game ~~all day every day are doing, most~~ of ~~which is based in~~ client~~-side scripting~~.		I have a buddy who says 'So that game sucks and before you can play it you first have to play the game of 'how do I code my client to make this actually playable'. He's kinda not wrong.


	~~=Potions & Stuff=~~
	~~A full supply of all the potions, scrolls, items, that are useful, on hand, on every char, all the time~~.

Admin at 13:32, 28 December 2022

2022-12-28T13:32:51Z

← Older revision		Revision as of 21:32, 28 December 2022
Line 5:		Line 5:
	Here's things the uber-nerds who play this game all day every day are doing, most of which is based in client-side scripting.		Here's things the uber-nerds who play this game all day every day are doing, most of which is based in client-side scripting.

	~~=Characters=~~
	~~Have tons of characters. Tons of characters.~~

	~~Definitely a well dressed run char of every class.~~

	~~Multiple sets of spell bots.~~

	~~Storage characters.~~

	~~Other utility characters to do dedicated tasks to make your life easier. Guys planted permanently in places to unlock doors, for example.~~

	=Potions & Stuff=		=Potions & Stuff=

Admin at 13:26, 28 December 2022

2022-12-28T13:26:55Z

← Older revision		Revision as of 21:26, 28 December 2022
Line 6:		Line 6:

	=Characters=		=Characters=
	Have tons of characters. Definitely a well dressed run char of every class.		Have tons of characters. Tons of characters.

			Definitely a well dressed run char of every class.

	Multiple sets of spell bots.		Multiple sets of spell bots.

			Storage characters.

	Other utility characters to do dedicated tasks to make your life easier. Guys planted permanently in places to unlock doors, for example.		Other utility characters to do dedicated tasks to make your life easier. Guys planted permanently in places to unlock doors, for example.

			=Potions & Stuff=
			A full supply of all the potions, scrolls, items, that are useful, on hand, on every char, all the time.

Admin at 13:24, 28 December 2022

2022-12-28T13:24:18Z

← Older revision		Revision as of 21:24, 28 December 2022
Line 1:		Line 1:
	So you think you're some kinda Power User huh? More like Power Loser amiright?!?!?!?!		So you think you're some kinda Power User huh? More like Power Loser amiright?!?!?!?!

			This page is meant to give new players an idea of the scope of what's needed to really play the game well.

	Here's things the uber-nerds who play this game all day every day are doing, most of which is based in client-side scripting:		Here's things the uber-nerds who play this game all day every day are doing, most of which is based in client-side scripting.

			=Characters=
			Have tons of characters. Definitely a well dressed run char of every class.

			Multiple sets of spell bots.

			Other utility characters to do dedicated tasks to make your life easier. Guys planted permanently in places to unlock doors, for example.


	=Quick Prep=		=Quick Prep=

	Code your own spell ~~bots~~ and bring ~~them~~ with you on runs.		Code your own spell bot script and bring your bots with you on runs.

	Have an alias to quaff a tank set.		Have an alias to quaff a tank set.
Line 22:		Line 30:
	A full reset alias is helpful, that can be broken down into this component aliases you can fire individually if necessary as well:		A full reset alias is helpful, that can be broken down into this component aliases you can fire individually if necessary as well:

	'''repair''' - an alias to run you to your preferred repair mob, remove all, repair all, wear all, recall.		'''repair''' - an alias to run you to your preferred repair mob, remove all, repair all, wear all, recall.
	'''refavor''' - an alias to run to a'enari/vl'aresch to refavor back to praised, and recall.		'''refavor''' - an alias to run to a'enari/vl'aresch to refavor back to praised, and recall.
	'''restock''' - an alias to buy you heals/manas and restock tank pots from a donation shelf.		'''restock''' - an alias to buy you heals/manas and restock tank pots from a donation shelf.

	If you've done a kill on something and people say 'reset', its realllll nice to just type 'recall... reset' and then go get a drink while that all happens.		If you've done a kill on something and people say 'reset', its realllll nice to just type 'recall... reset' and then go get a drink while that all happens.

	~~You can also get even more tricksy and make it recall you, reset you, and return you to wherever you were.~~

	The restocking alias is the one that takes the most scripting. You'll need to establish a variable that keeps your desired stock levels of stuff, then, also set up a trigger that can be enabled when you examine your containers that will catch all the potion names and record how many you have into a 'current stock' variable. Then, the restock alias just uses some math to compare your desired levels to your actual current levels and gets the difference from your potion shelf.		The restocking alias is the one that takes the most scripting. You'll need to establish a variable that keeps your desired stock levels of stuff, then, also set up a trigger that can be enabled when you examine your containers that will catch all the potion names and record how many you have into a 'current stock' variable. Then, the restock alias just uses some math to compare your desired levels to your actual current levels and gets the difference from your potion shelf.
Line 82:		Line 88:
	In any case, SOME level of fight assistance is going to be basically required. You'll want it to try to handle a bunch of conditions, such as:		In any case, SOME level of fight assistance is going to be basically required. You'll want it to try to handle a bunch of conditions, such as:

	*Healing (~~heal to full or heal to a value you can specify on the fly by having an alias~~ set a ~~variable~~)~~. Account for stomach fullness:~~		*Healing (set a threshold at which to begin healing)
	*Stomach fullness and spring drinking (also usage of spells like salinate, or custom spring names)		*Stomach fullness and spring drinking (also usage of spells like salinate, or custom spring names)
	*truesight/blindness/cure-blindness		*truesight/blindness/cure-blindness
Line 105:		Line 111:
	To prevent equipment from scrapping in a fight, you'll want to set up triggers to track hits to your gear and auto-remove gear that is down to 2 or 3 hits remaining.		To prevent equipment from scrapping in a fight, you'll want to set up triggers to track hits to your gear and auto-remove gear that is down to 2 or 3 hits remaining.

	This can be done ~~by creating~~ a local client-side ~~variable(s)~~ that ~~stores your eq names, keywords, and AC values~~. Then, a trigger on the 'gets damaged' message can be used to regex whatever got hit against your locally stored information and adjust the AC variable. Include an #IF check to consult that AC value and if < 3 remove the item.		This can be done in a number of ways. Be aware of the game's 'survey' command to review your equipment conditions. You can scrape data from that rather easily and store it in a local client-side var that is hella useful.

			Then, have a trigger on the 'gets damaged' message can be used to regex whatever got hit against your locally stored information and adjust the AC variable. Include an #IF check to consult that AC value and if < 3 remove the item. Alternatively, trigger a 'survey' and have some code look for the worst condition names, and remove gear if it sees those.

	Here's an example snippet of my 'eqlist' variable that includes all wear slots, here is what one individual wear slot looks like:		Here's an example snippet of my 'eqlist' variable that includes all wear slots, here is what one individual wear slot looks like:
Line 122:		Line 130:
	<pre>		<pre>

	So then a trigger for {* get's damaged!!} does something like: foreach item in the 'eqlist' var regex that item name against the * that got hit, upon match, reduce the items AC by 1, and if AC is now < 3 remove the item by its key word.		So then a trigger for {* get's damaged!!} does something like: foreach item in the 'eqlist' var, regex that item name against the * that got hit, upon match, reduce the items AC by 1, and if AC is now < 3 remove the item by its key word.


Line 138:		Line 146:
	=Mob Tracking=		=Mob Tracking=

	MSDP sends you ever mob name and level, along with room name and room area, so its super easy to just start saving those into a huge searchable var.		MSDP sends you ever mob name and level, along with room name and room area, so its super easy to just start saving those into a huge searchable var that's basically a database.

	Every time I fight something I save that data, and also a mob keyword. So, ~~when I do get into a~~ fight~~, this list is consulted~~ so ~~my hit aliases/macros/triggers~~ can ~~be targeted to~~ the ~~correct~~ keyword~~. For example, I~~'m fighting ~~'Ratboy' and I just punch F3 which is a macro that issues the alias 'hit' which is scripted to search my mob db for the current msdp mob name to find his keyword and then does "$hit rat"~~		Every time I fight something I save that data, and also a mob keyword. Its then easy to write an alias that searches those lists, so you can easily find mobs by name, level, etc. Useful for finding mobs to try to level off, or for quests regarding certain mobs (find all dragons, etc). Also useful for any fight automation you might have so it can find the target keyword for a mob you're fighting.

	Small example of a search of my mob db:		Small example of a search of my mob db:
Line 151:		Line 159:
	The Warehouse Inside a Filthy Bathroom boy 4 an obnoxious boy		The Warehouse Inside a Filthy Bathroom boy 4 an obnoxious boy

	Given that the map function can auto-run us to any room name, you can also create an alias to run to a mob ~~that will search the mob list here for the term you enter to find his spawn room then move you right there~~. For example 'run Ratboy' would run my char right to his room, from anywhere in the game.		Given that the map function can auto-run us to any room name, you can also create an alias to run to a mob with this. For example 'run Ratboy' would run my char right to his room, from anywhere in the game.

Admin: /* Quick Prep */

2022-07-08T09:46:59Z

Quick Prep

← Older revision		Revision as of 17:46, 8 July 2022
Line 13:		Line 13:
	Have an alias to apply any class-specific skills/spells you get.		Have an alias to apply any class-specific skills/spells you get.

	When its time to prep for a run, get all spells from your bots, quaff a tankset, apply anything else, and then log off. Your ~~guys is~~ 100% ready to rock and offline.		When its time to prep for a run, get all spells from your bots, quaff a tankset, apply anything else, and then log off. Your guy should be 100% ready to rock and offline.

	Have an alias to do all this for you:		Have an alias to do all this for you: