Imagine:
>stat
You are not resisting arrest. You are not intentionally failing at climbing.
You are not resisting magick spells. You are not resisting psionic abilities.
You are not resisting mundane skills.
You are not resisting subdue attempts. You are not resisting theft attempts.
(see help Nosave for more info)
You are not being merciful. (Mercy Off)
You aren't watching anything in particular.
Your Relationship to the land is neutral.
Your encumbrance is heavy, but manageable. You are standing.
Your ldesc is: (see help ldesc for more info)
code generated long description
Your mood is: (see help mood for more info)
neutral.
You are currently speaking sirihish with a northern accent.
You are affected by:
Psionic Barrier
>stat
You are resisting arrest. You are intentionally failing at climbing.
You are resisting magick spells. You are resisting psionic abilities.
You are resisting mundane skills.
You are resisting subdue attempts. You are resisting theft attempts.
(see help Nosave for more info)
You are being merciful. (Mercy On)
You are watching the effeminate, pompadoured fellow
Your Relationship to the land is neutral.
Your encumbrance is light. You are resting.
Your ldesc is: (see help ldesc for more info)
The figure in a dusty dust-coloured, brown hooded duster sits at the bar,
relaxing and looking bored.
Your mood is: (see help mood for more info)
neutral.
You are currently speaking sirihish with a northern accent.
You are affected by:
Psionic Barrier
I think that would be a lot easier for new players to understand the different options, as well as for old players to have the nosave in the stat with more descriptive of what is nosaving.
Also, I think the ldesc should be added to the stat command, as well as keeping it in the score.
Also, I think that ldesc should echo exactly what the code generated long description is, instead of having a line that says, "code generated long description".
I think these subtle changes would be good.
Quote from: mansa on December 15, 2008, 12:00:47 PM
Also, I think that ldesc should echo exactly what the code generated long description is, instead of having a line that says, "code generated long description".
Totally this. Wherever it is that the ldesc is echoed.
Stat needs to give listen/scan status too, maybe even guard status if it doent' already.
I know this is a bit old but wanted to bring it up again. What Mansa posted is an awesome idea and prevents players from having to type a multitude of commands to check all these things.
Quote from: UnderSeven on December 15, 2008, 01:51:58 PM
Stat needs to give listen/scan status too, maybe even guard status if it doent' already.
Also THIS ^^^It already shows:
You aren't watching anything in particular.So why not add Scan, Listen and Guard to it as well? I for instance use an alias called "status" to do 4 commands using "<command> status" to see what I'm doing when all this could really just be added to the "stat" command.
I sort of like the idea of seeing your listen/scan status but I really don't think this is necessary because I personally notice that the status has changed when my maximum stun goes back (or closer to) normal, know that typing listen/scan on has no lag if it is already on, and don't mind spending 1 second doing this.
Nor do I care to see a spam of nosave statuses when I type stat. That's a -lot- of stuff that I and not used to seeing. I don't need that.
However, this idea deserves merit and, as Mansa suggests, will probably help newer players be more aware of their character. So, in addition to this idea I'd like to suggest "stat brief" to toggle a brief mode of the stat display to turn on or off. Brief mode would display what we currently see while the default mode would display some adaptation of Mansa's extended TM version.
Another idea for listen and scan would be this:
You are currently speaking sirihish with a northern accent.
You are affected by:
Psionic Barrier, Listen, Scan
just add everything into stat, and then let us ask for just the pieces we want back like we can with skills.
skills weapons returns just the weapon skills.
stat affected should return just what you are affected by.
i would love just an 'affects' command that reads out what you are affected by.
Can affects be put into your prompt? Cause they should.
Quote from: RogueGunslinger on April 27, 2009, 08:18:11 PM
Can affects be put into your prompt? Cause they should.
That sounds like a great idea. I'd like to have a command to see affects or leave them in stat though because having 10+ affects in the prompt would make certain classes awfully spammy to play.
Yeah, but those classes could just not put it into their prompt.
Quote from: Agent_137 on April 24, 2009, 04:51:47 PM
just add everything into stat, and then let us ask for just the pieces we want back like we can with skills.
skills weapons returns just the weapon skills.
stat affected should return just what you are affected by.
I like this idea.
Stat would be the new score with these options.
Love it.