Thanks for the update. Things I'd like to see in the future:
- OXTools Auto Update
- Start with Windows option
Printable View
Thanks for the update. Things I'd like to see in the future:
- OXTools Auto Update
- Start with Windows option
great work @jo3bingham
A quick note:
I absolutely love this program, I was using windaddons (strictly for the cpu saver, not for that shitty ass bot) and making a ton of test characters (2-3 characters a day) and getting deleted within 4 hours of creating it.. I became curious and kept going to figure out why they were being deleted, tweaking slight things, including IP, way they are created, proxies etc. I'm happy to see and say, that I've used OX Tools for about 3 days now without a single deletion. I remember seeing a post by DarkstaR about windaddons not doing exactly what it said, so I'm curious if they left something in their that may be significantly more detectable when standing still.
Now for the main reason of this post:
I used the original release, v1.0.0.0 and just tried out the newest release, v1.1.0.0, and just a heads up, the newest release eats my CPU. When I run the v1.0.0.0 each tibia client uses about .3 - 1.2% and OXTools uses about 5%, however, with the v1.1.0.0 the tibia clients still use .3 - 1.2% but the OXTools uses roughly 80% to run 12 clients. So as the number of clients goes up, OXTools is starting to take more. Not sure if anyone has a crappier computer like mine so figured I'd just give you the heads up that this is happening :) (I've reverted back to the v1.0.0.0 release for now, it works flawlessly for me as of right now :D)
And a little tip:
Also if anyone is wondering/noticing their clients freezing (mentioned in the original post that this can happen), from what I noticed its caused by when you close out of OXTools (I closed it out to try the newer version)
As he mentioned, the clients still are running, you just cant see it
Once again, thanks for this, amazing job
This is legit. Thanks team
I'll add these to my to-do list.
Thanks!
I didn't change anything in the code that would cause a noticeable CPU usage difference between v1.0.0.0 and v1.1.0.0, but I'll recheck my code. There's obviously something going on because you're not the only person with a "crappy" computer that has mentioned this. Hopefully I can fix it.
OXTools should re-enable every client's drawing when closed, but I also noticed this issue so I'll try to fix it as well.
Thanks for the post.