I'd like to suggest adding in the ability to execute scripts without being required to connect to a specific server.
This primarily comes from the new chat scripting, which I have an interest of maintaining in it's own 'world' screen. But I have seen some use for it in the past when I wanted to look at some data I had available through scripting that didn't send anything directly to the server.
I'd guess this would require the check for disconnect from just typing something in the input box on the world screen to actually sending data to the server (world.send, etc), but I'm sure it's at least 12 times more difficult. ;)
This should probably incorporate all aliases, aliases calling scripting, and pure scripting calls. Only when there is a direct request to send information to the server should it check for connection status and determine what to do at that point. If the command type is causing just processing, or only echoing data to the local screen, then it shouldn't require the reconnect.
This primarily comes from the new chat scripting, which I have an interest of maintaining in it's own 'world' screen. But I have seen some use for it in the past when I wanted to look at some data I had available through scripting that didn't send anything directly to the server.
I'd guess this would require the check for disconnect from just typing something in the input box on the world screen to actually sending data to the server (world.send, etc), but I'm sure it's at least 12 times more difficult. ;)
This should probably incorporate all aliases, aliases calling scripting, and pure scripting calls. Only when there is a direct request to send information to the server should it check for connection status and determine what to do at that point. If the command type is causing just processing, or only echoing data to the local screen, then it shouldn't require the reconnect.