I've modified my idoc script so many times since first writing it years ago, It's actually quite fun to look back at each set of changes and see the progression from OK script to one I am happy with. Constantly using the script and tweaking it based on actual idoc outcomes has made it better than I had originally set out to make it but I still want to take the next step and make it work even better in combination with a second account. I think it could be even faster if things processed in one script were not processed redundantly in the second.
Is there any documentation about how to share data from multiple scripts as the scripts run? ie: shared ignore list, shared finditem results etc? so two scripts(or more) can avoid evaluating the same things redundantly? I've seen mention of it in a couple of existing public scripts but would like to fully understand the limits and nuances before I tackle it live. Any reading suggestions? Search wasn't much help unfortunately.
P.S. I am a webmaster and running scripts with a desktop or even a server based SQL database would be trivial to set up, has anyone "gone there" and mind sharing their findings? My goal is to get multiple already fast scripts to work together to make them even more effective.
Stuff that can be eliminated if scripts work together, example:
1 account is on N side of house, other on S side. The 2 accounts are aware of their distance from each other. Account 1 spots an item a G_12 directly in front of it and instantly knows that that location is only G_6 from account 2. The item is "handed off" to account 2 as the top priority and account 1 ignores it and scans again. Account two redirects from an item it spotted at G_6 because this item is better.
The above is one thing I'd test, sort of like a hive mind. Another I'd like to test is perhaps an account that doesn't try to pick things up at all, it simply stands by the sign and does nothing but scan the area to itemize and prioritize targets for the other account(s). No time spent evaluating with the item grabbers or time spent running with the evaluating account. Again, how fast the item evaluation could be made and shared would be critical.
MAYBE, if other idocers welcome the idea, scripts from multiple accounts could tap into the same data and share in the evaluation/priority item processing so that if an item is high on one person's list and is near them the other users would not all make a mad dash for it and would instead find good items near them so that they aren't gone by the time the mad dash is over. Fraps videos show me people running right past things like secret chests, for example, to try and grab a porter tile only for the chest to be gone after they dash back.
I\m gettign ahead of myself maybe, not sure if this is being discussed in the elite section or not, but there seems to be a lot of ways of making things more efficient that would benefit everyone who's on board with it. I hope that wasn't all too confusing.