github push 3/9/20:
- The egg finder worker thread is disabled and copied into the flute routine
- Scans for greater cures and smoke bombs are only done once at initialization
- Added 250ms delays after every scan to ensure accuracy - this should be way more than needed because it takes around 2 seconds to search and parse 50 items in a container.

It appears after moving the methods that use the FindType function to one thread has fixed the nil index errors which means that this function most likely cannot be used concurrently in multiple threads.  Stat reports to follow...

EDIT: 13 eggs in about an hour

Hello, welcome back!  I can't begin to imagine what you've been through but I'm glad you made out well!

Basically Discord is the equivalent to a forum with voice chat - a platform for communication which is actually built on Google Chromium (among other frameworks)

Also, I have two scripts you may be interested in, however, if you are unfamiliar with Stealth UO client you may need some help to get up and running.
I do believe there is a decent amount of existing information on posts, but I don't mind helping in addition.

EggFarmer - http://www.scriptuo.com/index.php?topic=13165.0
Actively working on this right now.  Is it perfect?  No.  Rarely some odd occurrences happen like it'll miss an egg or not enough snakes around.  Once it comes back through the rail though it'll pick that egg up fo sho.  I'm talking this project down a bit because it's not fully optimized, but it does actually work pretty nicely at the moment.

LootLogger - http://www.scriptuo.com/index.php?topic=15645.0
I noticed you had interest in finding something that would log every item in your house.  This app does something similar and can be extended upon easily.  At the moment, it will go through every container in your house and log all your Armor, Weapons, Jewelry and Shields - but you can add more item types if you want.  There are functions to extract this data to an XML file.

OK well we're mostly functioning over here...

EggFarmer.cs line 136 - currently commented out.
Stealth.Client.Buff_DebuffSystem += onBuff;

This line causes an exception "Error, packet parsed incorrectly!" - Unfortunately this means ScriptSDK needs to be updated, which I'm capable of doing, but not knowledgeable enough to figure out how to fix.

As of right now, there is no method to cure yourself if you're poisoned.

I spoke with Vizit0r, he may be helping me out later this evening!

Welcome back!

UO is one of those games you can pick up and put down any time and not feel like you're obligated to login.

I'm back from playing a game that promoted AFK gameplay and rewarded players for logging in after amount of timed play each day.

Combot

What?
Combot is a system for handling multiple concurrent Stealth profiles capable of communicating with each other.

Why?
If you have a script that checks for information from UO and does something based on that information....  then you take that script and you multiply it by how many profiles you're running it on.  If the profiles could share information with each other, they would not all need to request information from Stealth.  This makes it more efficient by having the scripts share information with between profiles.  Combot is also capable of client cross-communication.

Examples of usage:
You have a group of profiles existing in the same space (shard, screen) and they are fighting some monster together.  If you're running the same script through Stealth for each profile to check one another's health and heal them when they need it, then all your profiles will always try and heal the same person at the same time.  If another profile was damaged, it wouldn't get a heal until all the profiles finished healing someone else.    Combot's job priority system can be used to delegate tasks, such as healing, to each profile that it's connected to.  Instead of all the profiles trying to heal the same person, the Combot hub (server) will assign each profile with a different healing job.

How?
Combot makes it so only one profile is requesting data from Stealth while the other profiles feed off that data over TCP/IP.  This system is broken down into three parts (two of which are only important) - Client, Server, Data.  First, you run the Server on the profile that you want to act as the "hub" for all other bots.  This will collect any data from Stealth that all the other bots need - such as checking player health.  That runs in something called a "Routine" which I'll talk more about later.  The Server Routine collects data and issues Jobs to the JobQueue based on that criteria.  When a new Job is added on the Server, it will notify each client that is connected - this can also be set up to only notify certain Clients based on criteria (like if it's a bandage job, don't notify clients who don't have healing.)  As the server starts notifying Clients, if a Client is not busy with another Job it will accept it and notify the Server that the Job is now assigned so that Clients aren't don't pick up the same Job.  Once the Client is finished with the Job, it notifies the Server that the Job is complete and the Server removes the Job from the JobQueue.  You can run the Client on as many Stealth profiles as you desire.

Structure:
I'm going to have to write up a lot more documentation on this, but I'm going to give you guys all the need-to-knows now.

Routines - Both the Client and the Server have Routines.

The Server Routine contains the checks to Stealth that you want to also share with the Clients.  It also assigns jobs to the JobQueue based on the checks that you have done in the Server Routine.

The Client Routine contains what you want the client to do on its own - like making sure you're staying within range of the Leader (the Server.)  You can add your own routines; right now both the Client and the Server have example routines named "Combat."  The Client also has a routine named Job - this defines how Jobs should be handled on the Client-side.  For example, the Server sends a Client a Job to bandage someone, the Client runs the JobHandler in the Job Routine to check what type of job it is and calls a method in the Routine to handle the Job.



Files:
https://github.com/unisharpUO/Combot

If you want to get this set up and running in its current state, download the entire solution and open it up in Visual Studio 2019 (free community edition can be downloaded.)

Requirements:
https://github.com/Crome696/ScriptSDK
https://github.com/unisharpUO/XScript

Server\Routine\Combat.cs
You'll see there's a GroupList - this is a list containing all the player IDs who are to be checked (for health.)  Add/Remove as many as you like and remember to change the number to whatever ID your character is.

Client\Client.cs
Line 68 - set this to your machine's local network IP.

Startup Stealth and connect with a profile that you want to act as a hub.  Compile and start the Server.  Use Stealth to connect another profile that you want to act as a client.  Compile and start the client.

This post is also a work in progress.

Added job rejection:
Jobs now have a new property - a list of clients who rejected the job. When the server receives a job rejection packet, the client is added to the Rejectors property of the Job object. The server then calls a notify. The Queue notify function has been updated, it now checks if a job has any rejectors and if so, doesn't notify them again. If all clients connected to the server reject the job, the list of rejectors is reset and the job goes back into the queue.

Clients can add jobs now too:
I have a poison check in my server routine, but I couldn't pass on having the clients add themselves when they get a buff/debuff event. So not only does the server check for poisoned characters, but clients will be adding themselves if they are poisoned.

Thread locking and Added Exception Catching for the Job Queue:
There are circumstances when the server will be notifying clients about jobs, and a job will be completed in that process. This will cause an Exception and usually cause the program to crash. We now catch the exceptions so the program can continue doing its job. I added thread locking to all the functions that deal with modifying the jobqueue in hopes that this wouldn't happen again, but it still did. So I ended up removing the locks, for now, may end up putting them back once I find a solution. The locker object still exists under the queue class, it's just not used.

Jobs moved to Server.Data:
I had to move the Job class into the data section because I wanted to serialize a job and send it through a packet and just moving the class was less work.

*While this project might not be completely useful to everyone, there are examples in here on how to utilize ScriptSDK (with XScript extension) to quickly and easily evaluate and filter loot.

**This is not a compiled project, this is source code.  If you want to compile the project yourself you can download Visual Studio 2019 Community Edition for free and compile it along with the required references posted below.

LootLogger
This project was started in order to assist me in finding specific pieces of gear to build the perfect suit.  You can either log one container or log every container in your entire house with the click of a button.  Saving the log will save your data in an XML file which you can then use something to parse/display/sort/filter.  I'll be adding methods of parsing data in the next post below this one.

If you look at Form1.cs the are two methods called SaveFiles()  one is commented, the other isn't.  The new method that is not commented out is working but not complete as far as message postbacks.  The old commented method works and is complete.  The difference between the two functions is the way the output is formatted.  The commented way formats the XML file in a Parent->Child format, and the new uncommented method formats the XML file with element properties formatting.

What works:
Search Container, Search All Containers, Save Log, Fetch

Not working at the time of this post:
Load log - I haven't written a new loading method now that I've reformatted the XML output.
SQL connectivity - don't hit anything on the "Settings" tab as it will not work at the moment.


Requirements:
ScriptSDK - https://github.com/Crome696/ScriptSDK
XScript - https://github.com/unisharpUO/XScript

Usage:
Compile and launch, a character must be connected, in-game and in your house.  Choose to search through a container or search through all containers in your house.  Your character will path to containers out of reach.  After the worker thread is complete an autosave is called.

Missing Items:
If a container with items that don't match what's in our item bases, then it will be defined as missing.  Missing items tooltips will be posted in the message output box for debugging.



Source:
https://github.com/unisharpUO/LootLogger

Happy to be back again 

Working on converting some of my old C# projects to python.