• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

Help Needed - Community Group to make compilation tutorials and guides for OTC

_ferrari_

Well-Known Member
Joined
Sep 17, 2011
Messages
119
Reaction score
56
i-want-you-giwy.jpg


Introduction

Most people who have worked with OTC before might have come across general lack of direction and information regarding pretty much everything - modules, sources, graphics, etc.. These hinder the growth of the OTC users and developers. This is because OTC tends to be difficult to work with, which keeps away developers, and prone to bugs and unexpected behavior, which makes users dislike it.
Even with these problems making OTC's life difficult, it is still a very solid project, and I strongly believe it has the potential of being the next big thing it our little world right here. This thread is meant to address one of the two major problems with OTC in my opinion, compilation, the other being deficiency of a good cryptography support.

Objectives

The objectives of this thread are gathering information and making a community effort to:
  1. Formulate a solid, easy to follow, foolproof compilation tutorial for major systems, compilers and IDEs;
  2. When possible, provide a pack with materials needed for compilation, such as libraries;
  3. Address common problems during compilation.

Motivation
The tutorials on the OTC github don't work properly, requiring multiple workarounds. One example of this on Linux is this issue Unable to compile on Ubuntu 15 x64 · Issue #726 · edubart/otclient · GitHub where a dependency requires the user to download a lib's sources, cmake, make, install and finally move the lib to the otclient folder (phew!). Furthermore, OTC is practically impossible to compile on Windows, where most libs are outdated and complicated to obtain, and the tutorial from github is of no help.
On Windows systems, multiple of the #ifdef preprocessor definitions are stated as #ifdef WIN32, where it should have been _WIN32 when using Code Blocks (I'm not sure about Visual Studio though). Obtaining all the dependencies and linking them with the OTC object files to produce a binary file is an extremelly difficult task overrall and is one of the main motivations of this thread.

Plan of Action
In the event of more people being interested in working with this, I will manage the people and produce all the text and tutorials to comply with the objectives. The people involved will follow the errors and fix one by one until a compilable and linkable configuration is obtained.
From this successful run, the whole setup will be analyzed and a tutorial for that system will be made available for the public. The experience obtained with the work will be very useful in order to make progress on other systems. In the end, a complete tutorial will be made available to major IDEs and systems, with a pack of libraries needed when applicable, as stated in the Objectives session.

How to Participate
Leave a message in this thread or send me a private message. I will do my best to manage the people and delegate tasks, possibly using a discord channel or any other means of communication necessary (mailing lists or whatever).

Conclusion
I hope people are interested in this to the point of joining and contributing. This is to everyone's gain and this forum is absolutely filled with compilation problems regarding OTC, and still nobody has done anything about it - as far as I know.

Thanks for taking the time to read the thread :) I hope to hear from you.
 
Yes, it would be amazing if someone could update the info about otclient.

Some problems I encountered waas that: I did try to make use of it and managed to compile it and everything, but also all tools to edit .dat and .spr seemed outdated so I ended up giving up on otclient. I've also heard that there's some performance issues with otclient (but for me personally it has always run good). Servers like medivia I feel like has perfected otclient (it feels a lot better than the regular tibia client, there's much more quality of life options etc) but to me it seems to require a lot of knowledge in programming to get otclient into such a state. I even tried the new archlight server because they had added interesting things to the client but to me in the end their edits was atrocious for me, it seemed to just be a regular otclient but with tons of extra tiles.
 
Back
Top