My bot

[Blaster_89]

Since I won't be developing it anymore, I decided to release it

Largely based/influenced upon TibiaAPI (as a lot of C# Tibia projects tend to be) and beziak's internal caller

This project was released in an unfinished state, there will be bugs, and ugly and non-commented code,
it'll also be inconsistent in places, as some stuff haven't been updated
Some scripts are also in need of refactoring, as they will try to call outdated (and non-existant) code

Known issues:
Crashes the client randomly, seems to be more likely to happen if you run intensive tasks that
involves sending a lot of packets for prolonged periods
The cavebot's attack will sometimes not attack properly, seems to be a client bug, fixed by running a script

Would not have been possible without TibiaAPI, I learned a great deal from it
Also kudos to klusbert, DarkstaR, Jo3Bingham, Blequi, Farsa, beziak and possibly others

Should be noted that it's designed for a 7.72 OT server with 7.4 item IDs, but it should be easy enough to port to newer versions

https://dl.dropboxusercontent.com/u/...rce%20code.zip
http://austria.christofferforsberg.se/source%20code.zip

github repo: https://github.com/crilleforsberg/bot

[Puterin]

wow, thx for sharing Blaster

P.S. why don't you upload it to a repository like Github, Googlecode, etc? It would be easier to get it, and would live longer I suppose

[XtrmJash]

Thanks for this release, Blaster. It's interesting to me to see how you have structured it considering I am also using C# for JAPI, and yours looks a lot better organised :P

[Blequi]

it contains a lot of code, if it isn't complete, I think it is almost there.

Since my beginning I saw some snippets you posted over the whole tpforums and since there I had curiosity about how you code due your OOP style of coding. Now I'm killing it definitely .

I agree with Puterin, some code repo would be easier to browse code even if HD storage isn't a problem nowadays.

btw, good job and for sure it will be a good and reachable reference from now on for the whole community.

[DarkstaR]

Beziak's caller does not use any thread sync which is 99% what is causing your crashes, if you ever feel like fixing that. I wont lie, it will be a hard fix to accomplish remotely (without injection).

All in all, it looks good. The coding style is something that is definitely a good example. I feel like its much cleaner than a lot of open source software, including TUGBot haha.

[Blaster_89]

Updated first post with link to a github repo
Glad you like it

Beziak's caller does not use any thread sync which is 99% what is causing your crashes, if you ever feel like fixing that. I wont lie, it will be a hard fix to accomplish remotely (without injection).

Yes, that's what I thought after doing some searching
I ended up just writing a script to restart the client and load scripts if it happened

[DarkstaR]

Updated first post with link to a github repo
Glad you like it



Yes, that's what I thought after doing some searching
I ended up just writing a script to restart the client and load scripts if it happened

You can do a freeze of the main client thread, yielding to the thread that Beziaks caller executes. The problem is that a function you call might be using the same memory as the client at the same time, causing problems. There's a few good ways to do this:


Method 1:

• Allocate some memory
• Make a codecave that looks something like this:
  1: MOV eax, DWORD PTR:[someAddressYouAllocated]
  CMP eax, eax
  JNZ 1
  JMP peekMessageAddress
• Stick that codecave in place of the main peekMessage call in Tibia. The goal is to keep busy until [someAddressYouAllocated] has a value of 0, then return execution to peekMessage
• When Beziaks caller creates a codecave, it should set [someAddressYouAllocated] to 1 (This should be done before creating the thread, to allow Tibia time to hit the wait, since there's no reasonable way to ensure it does).
• When Beziaks caller completes, it should set it to 0. This should be done from the codecave to ensure speed.

Method 2:

• Freeze every thread in Tibia
• Make a backup copy of the memory related to the functions
• Execute
• Put old memory back in place
• Unfreeze threads

Method 1 will probably be faster from a completely external standpoint, but will freeze Tibia if the code cave doesn't fully complete. I don't think it will be noticeably slower, either.
Method 2 is what I use in TibiaSock, but will be considerably slower when done externally because there's so much overhead between the processes and threads.

[XtrmJash]

I've compiled it for those who doesn't know how to start it.

*removed*

Call me sceptical but this is your first post on the forums and you're trying to get people to download a precompiled binary... What on earth makes you think anyone here would be willing to download that?

[ruffs]

anyone can help me change to work with custom clients?

[Faun]

Very neat code, thank you