Show Posts
151
Stealth Snippets\Library / Re: [C#, Bot] Combot - responsive multi-botting (pre-alpha)
« on: April 29, 2015, 07:46:51 AM »
OK I'm too a point where I think I can call this a release candidate, but not 100% stable yet.
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 it's 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.
Exception Catching:
Added try/catches almost everywhere.
WTF!?! COLORS IN MY CONSOLE!
I added a function to handle writing to the console in colors. Combot.consoleMessage()
I'm close to making that video to go over all this... stuff
EDIT: I casted Explo/FS/Poison on 1 character with 3 clients connected. One client cast cleanse, one client cast close wounds, the other used a bandage - and they figured it out allll by themselves Pretty sweet
**EDIT2: Took out the call to notify from the rejection procedure. In one second the server cycled a rejected job through 3 clients 12 times! What I mean is, Clients: A, B and C each rejected the same job consecutively, 4 times each, in one second lol... I had to put a stop to this because it was ending in a semi-endless loop to which the job would just keep getting cycled until someone picked it up. So I changed it to when all the clients have rejected the job, the job is removed from the Queue... if it needs to be done again the server will issue it from the server routine.
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 it's 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.
Exception Catching:
Added try/catches almost everywhere.
WTF!?! COLORS IN MY CONSOLE!
I added a function to handle writing to the console in colors. Combot.consoleMessage()
I'm close to making that video to go over all this... stuff
EDIT: I casted Explo/FS/Poison on 1 character with 3 clients connected. One client cast cleanse, one client cast close wounds, the other used a bandage - and they figured it out allll by themselves Pretty sweet
**EDIT2: Took out the call to notify from the rejection procedure. In one second the server cycled a rejected job through 3 clients 12 times! What I mean is, Clients: A, B and C each rejected the same job consecutively, 4 times each, in one second lol... I had to put a stop to this because it was ending in a semi-endless loop to which the job would just keep getting cycled until someone picked it up. So I changed it to when all the clients have rejected the job, the job is removed from the Queue... if it needs to be done again the server will issue it from the server routine.
