Hello! I'd like to request a variable to use alongside "expanding" in passing along to verb argument procs called "final" that is set to 1 when the arguments are being checked the final time because the command has been sent/submitted, rather than when they're merely being entered/expanded.
This would be useful for server-side error catching. Example: in a MUD, you're getting ye flask at the same time thy dungeonman is. You both type"get ye-flask" and the command line takes this because ye-flask is showing up in your gettable() proc. But thy dungeonman is quicker on the draw, so by the time you hit enter, the valid entry of "get ye-flask" is invalid and you get an ugly and off-brand error message.
But if we could do get(item as anything in gettable(final)), the gettable proc could choose to accept that unacceptable entry, with the get verb then giving a graceful, in-game feedback explaining the how and why of you can't get ye flask as it doesn't show up in gettable(), only gettable(final=1).
If this can be done and the other bugs/omissions I've reported fixed, it officially replaces my request for a server-side error handling proc, as it would let me handle those things at the specific object/verb level, where BYOND does things best.
Mar 22 2018, 5:57 am (Edited on Mar 22 2018, 8:23 am)