Jump to content

Prompt for TinTin++


jibber

Recommended Posts

Aside from the rolling script that I've already mentioned here before, I've been messing around with a little prompt with tintin and have been able to customize it to my heart's content. Of course, if any of you know me in real life (I think two of you do) you all know I'm sort of a perfectionist when it comes to 'the look' of things.

Anyhow, take a look at what it looks like, and let me know what you all think, any other features that might/could be added, and I'll touch it up. For any who actually care and like it, I'll post the code for you if you ask for it.

prompt.png

Link to comment
Share on other sites

Aside from the previous (simple) prompt, I've created a few other additions. Color substitution is one (further determine who does what damage) and a bar/color prompt which automatically does a "where pk" every 5 or so seconds (which is gagged) and prints who is nearby in your PK range.

hpbar.png

Link to comment
Share on other sites

I removed it last night. Here's why:

It would spam where;#cr every 20 seconds. That's all good and dandy, but I had to gag the where output for a 10th of a second and output everything onto the bar. Problem was, if you're lagging, you kept seeing 'where', or blank lines, being that #gag {^$} wasn't an exact science.

You couldn't repeat enter commands. This means you couldn't type 'north', then press 12 times to go north 13 times. Every time you did a where, it'd become the last sent command and you'd send that again with the repeat enter. I couldn't figure out how to prevent that.

Sleeping. You'd continue to try to where when you slept. I could have easily set an #unticker command to when you went to sleep but it didn't take into effect that you might get attacked or how you might wake up. Seemed to be way too bug to try anything in this category.

Training: Yeah, good luck. As nice as it is to see your where pk posted every 20 seconds on your bar, training was too much of a hassle to work around that obvious #ticker which did a where and gagged most of your stuff. It lagged you a lot, too, so if you're trying to run, and you put in that then you just might die.

Disabling the #ticker: Easily done, but more of a hassle than a godsend. I'd have to write code to re-enable it with an alias (no problem) but most players (ME!!!) would forget to once I'm in safety or done doing whatever I'm doing.

All in all, the project died. Regardless, I do have a location of files:

www.forsakenlands.net/repo

Link to comment
Share on other sites

#ticker {where} {#if {$prefs[where] > 0} {#if {$where > 0} {where}}} {20}

#action {^You go to sleep.$} {#var where 0}

#action {^You wake {and stand up|up and start resting}.$} {#var where 1;where}

If I'd play something else than Merchant, I'd have the time set to 10 seconds.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...