Priority Queing - An idea.
Execution problems come when too many tasks are trying to be completed at the same time, or a high number of useless tasks are using hardware resources, stopping the important tasks from executing . An idea I would like to bring to RSPS is priority queing. High priority actions such as eating, fighting and walking will be executed before low priority actions such as trading and potion making. Although the difference will not be necessarily noticable (remember this all takes place in millionths of a second), it will help to ensure all high prority actions are carried out when they are supposed to, as many problems derive from un-responsive, usually important actions.
There will be two pools of data. Lets call one pool HP and the other LP, standing for high and low priority respectively. Execution from the HP pool will always come before that of the LP pool. Meaning for an LP task to be executed, all HP tasks will need to have been completed before hand. This may cause 'delays' in LP execution, however, this method ensures all HP tasks will run as promptly and efficiently as is physically possible.
Discuss, preferably comments from those with networking and extensive programming knowledge.