Explanation about OTClient taken from this thread: Introduction to OTClient. (https://otland.net/threads/introduction-to-otclient.163300/)
"What is it?
Okay, so OTClient is an open source alternative to the tibia client. OTClient works with a modular system, this means that each functionality is a separated module, giving the possibility to users modify and customize anything easily.
Users can also create new mods and extend game interface for their own purposes. OTClient is written in C++2011, the upcoming C++ standard and heavily scripted in lua."
And regarding to run Elfbot in OTClient, no I don't think you can simply run Elfbot on it. But since OTC is written in C++ (which I think Elfbot is written in too), then I guess it should be possible to fiddle with the OTC source so the bot works with it too, however, I think you need to know how Elfbot is programmed in order for that to work. So you probably would have to study Elfbot's code.
But I think it would be a much faster process for you to learn how to code in lua, since all modules in OTC are written in lua, and you can make your own things (even bots) and add them as mods to the OTC. There are even a few bots created in OTC already, so you could even tinker with them instead.
Otherwise, if you really "got to" or want to stick with Elfbot, then the easiest is to simply use it on Cipsoft clients, as it is intended for.
If both Elfbot and OTC would be written in the same language, then there would be no need to translate from one to another, making the process of coding whichever or whatever to make Elfbot work on OTC much easier, but if they are made in different languages, then the whole process would be more complicated, at least if the person/people working on it would have next to no knowledge of the other language.The current C++ is standard is C++ 17. I also don't see how Elfbot's incompatibility is related to the language it and OTClient are written in.
Only thing I can come up with, is that you might have to download their custom client in order to be able to properly play on their server.Uhm hi again!
I put .dat and .spr into folder but it isnt work. But first i want just try login to server then ill think about changing tibia.dat etc.
The wono-cj.net has also other server on the same ip (dbko.net). To login on dbko or wono i need to put same ip but change ports. I was trying now to login into wono and dkbo through "normal" otclient and... I did it! i can login into dbko. Also i can login through normal 8.54 client. But when i was trying to do the same thing to login WoNo i cant. When im putting passwords into normal 8.54 client i got debug before character select. But when im doing same thing into "normal" otclient at 8.54 protocol i can login into account(i see my character)! but i cant login into game Do you know maybe why?
i put screens from wireshark when im loggin through "normal" otclient and through their custom otclient
It isn't true, when writing bot's programing language doesn't matter at all because you end up working with assembly output, source code only helps with searching for specific functions and to know exact parameters of functions instead of guessing everything from the assembly.If both Elfbot and OTC would be written in the same language, then there would be no need to translate from one to another, making the process of coding whichever or whatever to make Elfbot work on OTC much easier, but if they are made in different languages, then the whole process would be more complicated, at least if the person/people working on it would have next to no knowledge of the other language.
Then I think reverse engineering would be the easiest way to go about it, aside from getting a person with knowledge of the other language in then of course.
Alright, actually good to know and thanks for giving some explanation too!It isn't true, when writing bot's programing language doesn't matter at all because you end up working with assembly output, source code only helps with searching for specific functions and to know exact parameters of functions instead of guessing everything from the assembly.
Even if you have elfbot written in C++11 you'll not rewrite it easily to work with OtClient at all because you'll need to rewrite all functions that works on internal client function to work with OtClient framework not the Cipsoft one.
fun fact:
Even if you somehow manage to have 8.54,8.60(whatever) source of Cipsoft clients after compile bots will not be working because you will get different assembly due to using different compiler version, different version of libraries or different project options than Cipsoft used.
If both Elfbot and OTC would be written in the same language, then there would be no need to translate from one to another, making the process of coding whichever or whatever to make Elfbot work on OTC much easier, but if they are made in different languages, then the whole process would be more complicated, at least if the person/people working on it would have next to no knowledge of the other language.
Then I think reverse engineering would be the easiest way to go about it, aside from getting a person with knowledge of the other language in then of course.
Yeah, I see what you mean now, I just re-read what you wrote first and finally understood it.What you're saying is entirely different. I was talking about the incompatibility issues. They are not related to the programming language.