This is going to fall under the wishful thinking category in terms of staff work vs. gain since we do have the keyword command, and we've discussed issues with keywords several times in the past, but I thought I'd suggest it anyway.
It'd be really neat to be able to create and assign a personalized keyword priority list for your character and/or account. Higher priority things take precedence over lower priority things. This would apply to keywords for anything, and would ideally include the ability to add/delete things at any time. Bonus points if you can make it add or delete items if they come into or out of your possession. All the bonus points if it allowed multiple keyword combinations and the ability to exclude or prioritize granuarly with these multi-combinations.
I'm not a coder, and have no idea how the codebase works with keywords currently, so have no idea if this is even feasible.
Example:
>edit keywordlist
>add black 1
>add black.sword 2
>add black.beetle 3
>add war.beetle 4
>keywordlist
Your keywords are currently prioritized as follows:
1. black
2. black.sword
3. black.beetle
4. war.beetle
>l
A war beetle is reclining here.
A nifty black sword is on the ground.
A huge black beetle is here about to kill your face.
A black scarf is here.
>get black
You pick up the black scarf.
>kill beetle
You attack the huge black beetle.
I think you could probably do this with alias's or triggers in your client. It would probably be a lot easier and quicker to implement using your client than having it coded on Arm.
Quote from: slvrmoontiger on February 04, 2014, 02:16:13 PM
I think you could probably do this with alias's or triggers in your client. It would probably be a lot easier and quicker to implement using your client than having it coded on Arm.
I do think that using aliases cover some of the issue here, but not all - I don't think there's a way I can use aliases to make one keyword subset lower priority than everything else, for instance, which would be more helpful in a novel or unanticipated situation. Maybe enough coverage there between that and just the liberal use of the keyword command that it'd push things more into the realm of not being worth staff's time I guess though?