Howdy, Stranger!
Categories
- 6.2K All Categories
- 3.1K Everything Achaea
- 1.5K North of Thera
- 26 Archives of the Terraformer
- 257 The Matsuhama Arena
- 885 The Golden Dais of Creation
- 299 The Scarlattan Theatre
- 149 The Blank Canvas
- 2K Getting Help
- 412 General Questions
- 258 Quick Class Questions
- 1.3K Tech Support
- 313 Client Help
- 486 Curing Systems and Scripts
- 841 Off-Topic
- 255 The Wander Inn
- 586 The Universal Membrane
- 298 Class Discussions
- 298 Individual Class Sections
- 20 Alchemist
- 9 Apostate
- 30 Blademaster
- 9 Depthswalker
- 14 Druid
- 4 Infernal
- 20 Jester
- 19 Magi
- 34 Monk
- 11 Occultist
- 8 Paladin
- 7 Priest
- 29 Runewarden
- 18 Sentinel
- 26 Serpent
- 20 Shaman
- 9 Sylvan
Can I create a script to identify sigils in a room?
I am currently running mudlet, and would like to create a script to be able to identify what sigils are in a room, how many, and how long before they disintegrate. How would I go about doing it? I'll admit I'm a noob when it comes to mudlet, I was better with zmud, but after an 8 year hiatus from the realms, I found myself applying for a position where a script like this would be fantastic and faster even. If anyone has some sort of ideas how to go about doing this, please let me know! Please remember I am virtually a noob at doing this, but after seeing some of the scripting just for an auto-clotter, I am confident that there is a way to do this.
0
Answers
You'd need an alias that does IH (or you could just use GMCP if you know how to do that), which enables a trigger (you probably don't want this to go off when you just do IH normally) that fires on each sigil line of IH and saves each one to a table. Then you need to loop over the table to send a PROBE for each sigil in the table, and those probes will be used by another trigger that looks for the decay times and saves the decay times to the/another table. You probably want to gag the IH and all of this probing too so you don't get spammed too hard. Then you need to print it all to the screen somehow, clear the tables, and disable the triggers again.