It includes several bugfixes and new features:
1) Haggle Bug
2) Teleport Self w/ no ports
3) Wand of ice display bug
4) Rangers can no longer use skills while using heavy armor (medium and light is ok)
5) BETA: Targeting is in. (See: http://forums.rohonline.net/topic/1904/) It only works with "kill" right now, and has some extra debugging output that will go away in the future.
6) New command interpreter. I've adjusted the interpreter to (hopefully) more intelligently pick the best match for commands. Commands now have priorities associated with them. The matching order goes like this: Exact match first, better priority second if partial match, if same priority the shorter command wins (no --> nod before noodle because no is a 66% match of nod, and 33% match for noodle) If you notice any command shortcuts going to a different command than it did before, post here and I'll adjust the priorities.
Perhaps some other small items that I've forgotten.
I'm not sure I like some of the single-letter commands... f for fl, r for run, o for osay... you're just not sure what you're going to get. For example, without trying, do you know what "a" will get you?
Heaven doesn't want me and Hell is afraid I'll take over.
I was going to say a for ask, but then I remembered I put in a better priority for Ambush so a --> Ambush. b --> bs. I don't like 'p' --> pw so I'll change that priority.
The great thing is with the priority system, we can now more easily fine tune what commands go where!
Oh yeah. Huk and I have had a few run-ins with the "p" = "change password" thing. If there can be a quick fix (instead of waiting for a next push) for a few of the single-lettered commands, that'd be awesome >.<
I think it's mostly a result of my spammy typing.
I've been loving the targeting though. I'm excited to see what happens next
I haven't been able to reproduce your bug, and my quick look through the logic in the code, doesn't follow what you showed. You didn't happen to do it near midnight when dailies reset did you?
Feel free to show me where in the code it's going wrong, or some other code path it's taking to show that message, but I just don't see it. (I've commented the following code below more explicitly than in the code itself, and it should quite clearly describe the logic)