Crystal Server

[Tryller]

I'm here to invite you to collaborate with the Crystal Server.

Crystal Server has been back for some time now, built upon the Canary base. I believe Canary had great potential, but unfortunately, its developers started selling features and bug fixes they created themselves.

I invite everyone who truly loves OpenTibia and wants to keep it free—as it has always been—rather than turning it into a marketplace, to join and contribute to Crystal Server on GitHub.

I'm currently working on the project alone, and despite that, I have already:

• Fixed many bugs that Canary's developers have yet to address
• Added new features

Thank you to everyone who took the time to read this. See you on the Crystal Server GitHub!

Crystal Server GitHub

 

[EduardoDantas]

The Canary project is open-source, and over the years, it has become the most active and modern OpenTibia engine, powering the largest number of servers and online players. With an engaged community and active support, our Discord has over 2,000 members, and every month, more than 50 issues are resolved and around 100 pull requests are merged, ensuring a constantly evolving and stable codebase.

Currently, Canary has over 1,977 commits, 2,274 closed pull requests, and 998 resolved issues, making it the most actively developed OpenTibia engine. Its success is built on the contributions of a strong and committed community that has been maintaining and improving it for over five years.

Interestingly, in the post, Canary is mentioned almost as many times as the fork itself, which only exists because of Canary. In reality, 99% of its code comes directly from Canary, and most of its fixes and commits are taken from Canary as well. That makes the argument feel contradictory and somewhat questionable—not as someone genuinely looking to contribute but as someone with ulterior motives.

If someone wants to fork and create their own path, that's fine—OpenTibia has always been about collaboration and freedom. However, it's important to remain transparent and acknowledge the hard work of a community that has been building and strengthening this project for years.

 

[Terotrificy]

The Canary project is open-source, and over the years, it has become the most active and modern OpenTibia engine, powering the largest number of servers and online players. With an engaged community and active support, our Discord has over 2,000 members, and every month, more than 50 issues are resolved and around 100 pull requests are merged, ensuring a constantly evolving and stable codebase.

Currently, Canary has over 1,977 commits, 2,274 closed pull requests, and 998 resolved issues, making it the most actively developed OpenTibia engine. Its success is built on the contributions of a strong and committed community that has been maintaining and improving it for over five years.

Interestingly, in the post, Canary is mentioned almost as many times as the fork itself, which only exists because of Canary. In reality, 99% of its code comes directly from Canary, and most of its fixes and commits are taken from Canary as well. That makes the argument feel contradictory and somewhat questionable—not as someone genuinely looking to contribute but as someone with ulterior motives.

If someone wants to fork and create their own path, that's fine—OpenTibia has always been about collaboration and freedom. However, it's important to remain transparent and acknowledge the hard work of a community that has been building and strengthening this project for years.
View attachment 90601

Having over 50 issues monthly doesn't really seems good tho.

 

[StreamSide]

dont you ever try to write about the greatness and immaculate canary server, you can not see the work these people are doing? you silly
trying to talk about the one and only canary, shut your mouth you scum
anyways good luck trying to make that thing work (and do not ever write about canario again)

 

[JeiDi]

Currently, Canary has over 1,977 commits, 2,274 closed pull requests, and 998 resolved issues, making it the most actively developed OpenTibia engine. Its success is built on the contributions of a strong and committed community that has been maintaining and improving it for over five years.

"making it the most actively developed OpenTibia engine" - You forgot to add Open Source*. It might be the most actively developed Open Source engine, but for sure not the most actively developed engine overall.



Moreover, 50 issues resolved per month and 100 new pull requests per month sounds like a big, big, big red flag.

Interestingly, you say that 99% of some fork code comes from Canary... Why didn't you mention that 99% of Canary code comes from TFS and its forks xD

Unfortunately, the attached screen only shows how unpopular the engine is. 106 servers with 1321 players show 12 players per canary server. Well, that's not bad, but it's definitely not something to be proud of. Even the last entry on that list has better results.

 

[Tryller]

Quantity is not synonymous with quality.

 

[Codinablack]

Quantity is not synonymous with quality.

Bro, you did 600 commits in 3 months? Are you even testing anything that you have changed at all?

 

[Felipe93]

The Canary project is open-source, and over the years, it has become the most active and modern OpenTibia engine, powering the largest number of servers and online players. With an engaged community and active support, our Discord has over 2,000 members, and every month, more than 50 issues are resolved and around 100 pull requests are merged, ensuring a constantly evolving and stable codebase.

Currently, Canary has over 1,977 commits, 2,274 closed pull requests, and 998 resolved issues, making it the most actively developed OpenTibia engine. Its success is built on the contributions of a strong and committed community that has been maintaining and improving it for over five years.

Interestingly, in the post, Canary is mentioned almost as many times as the fork itself, which only exists because of Canary. In reality, 99% of its code comes directly from Canary, and most of its fixes and commits are taken from Canary as well. That makes the argument feel contradictory and somewhat questionable—not as someone genuinely looking to contribute but as someone with ulterior motives.

If someone wants to fork and create their own path, that's fine—OpenTibia has always been about collaboration and freedom. However, it's important to remain transparent and acknowledge the hard work of a community that has been building and strengthening this project for years.
View attachment 90601

where's the repo anda canary forum?

 

[Codinablack]

where's the repo anda canary forum?

GitHub - opentibiabr/canary: Canary Server 13.x for OpenTibia community.

Canary Server 13.x for OpenTibia community. . Contribute to opentibiabr/canary development by creating an account on GitHub.

github.com

 

[Felipe93]

"making it the most actively developed OpenTibia engine" - You forgot to add Open Source*. It might be the most actively developed Open Source engine, but for sure not the most actively developed engine overall.

View attachment 90623

Moreover, 50 issues resolved per month and 100 new pull requests per month sounds like a big, big, big red flag.

Interestingly, you say that 99% of some fork code comes from Canary... Why didn't you mention that 99% of Canary code comes from TFS and its forks xD

Unfortunately, the attached screen only shows how unpopular the engine is. 106 servers with 1321 players show 12 players per canary server. Well, that's not bad, but it's definitely not something to be proud of. Even the last entry on that list has better results.

canary has evolved a lot in it's structure i wont day that is using tfs codeee

I'm here to invite you to collaborate with the Crystal Server.

Crystal Server has been back for some time now, built upon the Canary base. I believe Canary had great potential, but unfortunately, its developers started selling features and bug fixes they created themselves.

I invite everyone who truly loves OpenTibia and wants to keep it free—as it has always been—rather than turning it into a marketplace, to join and contribute to Crystal Server on GitHub.

I'm currently working on the project alone, and despite that, I have already:

• Fixed many bugs that Canary's developers have yet to address
• Added new features

Thank you to everyone who took the time to read this. See you on the Crystal Server GitHub!

Crystal Server GitHub

is this based off canary or what? apart from name what are the main deferences?

 

[Marko999x]

The Canary project is open-source, and over the years, it has become the most active and modern OpenTibia engine, powering the largest number of servers and online players. With an engaged community and active support, our Discord has over 2,000 members, and every month, more than 50 issues are resolved and around 100 pull requests are merged, ensuring a constantly evolving and stable codebase.

Currently, Canary has over 1,977 commits, 2,274 closed pull requests, and 998 resolved issues, making it the most actively developed OpenTibia engine. Its success is built on the contributions of a strong and committed community that has been maintaining and improving it for over five years.

Interestingly, in the post, Canary is mentioned almost as many times as the fork itself, which only exists because of Canary. In reality, 99% of its code comes directly from Canary, and most of its fixes and commits are taken from Canary as well. That makes the argument feel contradictory and somewhat questionable—not as someone genuinely looking to contribute but as someone with ulterior motives.

If someone wants to fork and create their own path, that's fine—OpenTibia has always been about collaboration and freedom. However, it's important to remain transparent and acknowledge the hard work of a community that has been building and strengthening this project for years.
View attachment 90601

106 servers with overall 1321 players is pretty bad

 

[Codinablack]

"making it the most actively developed OpenTibia engine" - You forgot to add Open Source*. It might be the most actively developed Open Source engine, but for sure not the most actively developed engine overall.

View attachment 90623

Moreover, 50 issues resolved per month and 100 new pull requests per month sounds like a big, big, big red flag.

Interestingly, you say that 99% of some fork code comes from Canary... Why didn't you mention that 99% of Canary code comes from TFS and its forks xD

Unfortunately, the attached screen only shows how unpopular the engine is. 106 servers with 1321 players show 12 players per canary server. Well, that's not bad, but it's definitely not something to be proud of. Even the last entry on that list has better results.

how much does one have to pay to get a gander at that source code XD

 

[fridai]

i wont say bad things purely because i dont want to discourage engine development in tibia community regardless of its quality, tibia is too important for me to produce negative feedback for people who are actually trying to change something for better.

 

[Beatss]

We, from the OpenTibiaBR community and the Canary project, have noticed your recent actions, including cloning our repository and attempting to attract contributors while criticizing our image. As someone actively involved in the project (I’m Beats, by the way), I would like to address this directly and based on facts.
First, the Canary project is a collective effort, built on clear guidelines that exist to ensure quality, consistency, and respect for the work of everyone involved. These rules are not arbitrary; they reflect years of experience and adjustments to keep the project sustainable and useful for the community. Your decision to ignore these guidelines and create a fork without seeking dialogue or alignment goes against the spirit of collaboration that open source represents.

Second, cloning a repository is a right granted by the open source license, and we have no problem with that — it’s part of the freedom we defend. However, using this to try to compete unfairly, attracting contributors with vague promises while denigrating our team’s work, is at least unethical. If you have criticisms or suggestions, the correct path would be to open a discussion in our official repository, such as an issue or pull request, so we could evaluate and improve together. Opting for public attacks instead of collaboration only weakens the community as a whole.

Finally, I want to remind you that Canary is not “ours” in the sense of ownership, but rather belongs to the community that sustains it. We have dozens of active contributors, regular commits, and a solid history of deliveries — all documented and transparent on GitHub. If your goal is truly to contribute to the OpenTibia ecosystem, why not join forces instead of dividing? Otherwise, your approach only raises doubts about your intentions.

I invite you to reconsider this stance and seek an open dialogue with us. The door is open for those who want to build, not destroy. If you prefer to continue with your clone, I wish you luck, but I hope it is done with respect and without trying to erase the work of those who came before.

Best regards,
Beats
OpenTibiaBR - Canary Project

 

[Nekiro]

We, from the OpenTibiaBR community and the Canary project, have noticed your recent actions, including cloning our repository and attempting to attract contributors while criticizing our image. As someone actively involved in the project (I’m Beats, by the way), I would like to address this directly and based on facts.
First, the Canary project is a collective effort, built on clear guidelines that exist to ensure quality, consistency, and respect for the work of everyone involved. These rules are not arbitrary; they reflect years of experience and adjustments to keep the project sustainable and useful for the community. Your decision to ignore these guidelines and create a fork without seeking dialogue or alignment goes against the spirit of collaboration that open source represents.

Second, cloning a repository is a right granted by the open source license, and we have no problem with that — it’s part of the freedom we defend. However, using this to try to compete unfairly, attracting contributors with vague promises while denigrating our team’s work, is at least unethical. If you have criticisms or suggestions, the correct path would be to open a discussion in our official repository, such as an issue or pull request, so we could evaluate and improve together. Opting for public attacks instead of collaboration only weakens the community as a whole.
Finally, I want to remind you that Canary is not “ours” in the sense of ownership, but rather belongs to the community that sustains it. We have dozens of active contributors, regular commits, and a solid history of deliveries — all documented and transparent on GitHub. If your goal is truly to contribute to the OpenTibia ecosystem, why not join forces instead of dividing? Otherwise, your approach only raises doubts about your intentions.
I invite you to reconsider this stance and seek an open dialogue with us. The door is open for those who want to build, not destroy. If you prefer to continue with your clone, I wish you luck, but I hope it is done with respect and without trying to erase the work of those who came before.

Best regards,
Beats
OpenTibiaBR - Canary Project

I'm sorry, but I can't stand hypocrisy, where is the credits for TFS team (the past and present), because you largely based your engine off tfs? I see not a single mention in the readme. Unless you no longer consider yourself based off tfs, if so you are delusional.

Also your license doesn't prohibit anyone from forking your repos, that's normal in open source space that people fork and create their own things, no one is stealing your work, because you published it freely.

'It is a fork of the OTServBR-Global project.' fork of what? This repository doesn't even have any server source code.

 

[Beatss]

I'm sorry, but I can't stand hypocrisy, where is the credits for TFS team (the past and present), because you largely based your engine off tfs? I see not a single mention in the readme. Unless you no longer consider yourself based off tfs, if so you are delusional.

Also your license doesn't prohibit anyone from forking your repos, that's normal in open source space that people fork and create their own things, no one is stealing your work, because you published it freely.

'It is a fork of the OTServBR-Global project.' fork of what? This repository doesn't even have any server source code.

Before, it had all the mentions, but let's renew it because like you and those from TFS, you always only criticized but I don't remember seeing even one pull back from you... And at no point did I say that he couldn't clone the project and run it as he saw fit... And you talk about hypocrisy too? Spare me

 

[Tryller]

I didn't know that canaries cried.
Long live OpenTibia and Open Source
Thanks to all TFS developers for keeping EVERYTHING Open Source

 

[Beatss]

I didn't know that canaries cried.
Long live OpenTibia and Open Source
Thanks to all TFS developers for keeping EVERYTHING Open Source

You accuse us of selling things and fixing bugs that we implemented ourselves but we can't defend ourselves??? You're such a hypocrite, it's more like a joke.

You and the others, what do you do to help? You just want fame. Success to you and everyone involved, oh before I forget success to TFS.

 

[Tryller]

Bro, you did 600 commits in 3 months? Are you even testing anything that you have changed at all?

I can assure you that everything that has been changed/added/or modified in Crystal Server is tested before making commis and/or approving PR.

Post automatically merged: Mar 1, 2025

You accuse us of selling things and fixing bugs that we implemented ourselves but we can't defend ourselves??? You're such a hypocrite, it's more like a joke.

You and the others, what do you do to help? You just want fame. Success to you and everyone involved, oh before I forget success to TFS.

Fame? really?
You can see all branche from TFS Old SVN?

Branches · otland/tfs-old-svn

TFS repository once kept private, converted from SVN - Branches · otland/tfs-old-svn

github.com

tfs-old-svn/definitions.h at tryller · otland/tfs-old-svn

TFS repository once kept private, converted from SVN - otland/tfs-old-svn

github.com

tfs-old-svn/definitions.h at 0.5 · otland/tfs-old-svn

TFS repository once kept private, converted from SVN - otland/tfs-old-svn

github.com

#define STATUS_SERVER_DEVELOPERS "Tryller, Talaturen, Dalkon and Kornholijo"


I don't need Fame everyone who is from the time of 2012 to 2014 remembers me

 

[Beatss]

I can assure you that everything that has been changed/added/or modified in Crystal Server is tested before making commis and/or approving PR.

Post automatically merged: Mar 1, 2025

Fame? really?
You can see all branche from TFS Old SVN?

Branches · otland/tfs-old-svn

TFS repository once kept private, converted from SVN - Branches · otland/tfs-old-svn

github.com

tfs-old-svn/definitions.h at tryller · otland/tfs-old-svn

TFS repository once kept private, converted from SVN - otland/tfs-old-svn

github.com

tfs-old-svn/definitions.h at 0.5 · otland/tfs-old-svn

TFS repository once kept private, converted from SVN - otland/tfs-old-svn

github.com

#define STATUS_SERVER_DEVELOPERS "Tryller, Talaturen, Dalkon and Kornholijo"


I don't need Fame everyone who is from the time of 2012 to 2014 remembers me

Just because my name isn't in the canary files I have no relevance whatsoever, sorry little grasshopper

Post automatically merged: Mar 1, 2025

It looks like we’ve got a troubling pattern here. He implements half-baked solutions full of issues, then we have to scramble to fix everything on our end, only for him to copy the improvements. Check out these examples: commit cb87ea6 and commit 7c93fd4 show poorly executed changes that needed follow-up fixes, and then commit 5c1262b and commit 5dc827c pop up as if he “solved” something that was already broken because of him in the first place.<br><br>Even worse, he takes PRs in draft—ones that are obviously buggy, like this commit 1dee569—and throws them straight into his base. Where’s the testing for all this? Are you the one putting buggy code into your base because you don’t validate anything, or is it us, who are trying to work properly and then see our efforts copied without any discernment?<br><br>And there’s more: he keeps cherry-picking stuff from Canary, like in commit 809baa3 and commit a74f85f, takes the credit, and pushes it forward as if he knows what he’s doing. It’s pretty clear he has no clue what’s going on and just wants to reap what we sow. How is this sustainable for anyone?