• 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!
  • 2026 staff recruitment is open! Check it out and consider applying!

BlackTek-Server Development Thread

Unfortunate language barrier that escalated to a conflict... 😟
Dw, good job to both of you, what matters is progressing forward.
I'm not so certain.

Sure the language barrier made it worse, but it is fairly silly go to into the discussion thread of another server and state "We did that first!"
Doesn't really matter what the context is, the intent is clear. "Hey look at my server instead of this one!"

Either way, discussing this any further would take away from the actual discussion of Blacktek.
 
Update for those who are following this thread:

I have integrated a new class in the sources for creating "point based stats" for any creature or item, and built a lua API for it, as well as handled serialization and deserialization for players and items.

You may find yourself asking, what is a "point based stat" exactly? Well what are health points? What are mana points? A stat with a current and max value of "points" right? That's what the point based stats are, and they have a unique built in support for handling "modifiers" which affect the "max" of the stat... like a multiplier or a flat increase, division or subtraction type, you can add any of them to the stat and it will apply automagically.

The class is called Stat in lua (as the userdata) and here is a look at some internal source code to give you an idea of the methods available for use in the API:

1768944401842.webp1768944419106.webp1768944433745.webp

After this update, this puts blacktek in a state pretty much ready for the next release, which I am also happily announcing today that it will be officially versioned as BlackTek 2.0. The official date is still unknown, but the only things left for this development cycle is to cleanup all the rest of the xml usage (excluding monsters and npcs), and to provide offline documentation with the server.. that's it, that's all that is left! We have made a great many big and small changes to this version during this cycle, hence the reason we decided increasing the version number another "minor" increment to simply be inadequate, especially since we started introducing backwards breaking changes this cycle... anyways, keep on the lookout, BlackTek 2.0 coming soon šŸ˜Ž
 
Update: Documentation (front end api part at least) is completed and in need of review!

I am looking for help on verifying accuracy of the documentation I have (had) created for blacktek's front end (mostly the lua api), so if someone cares to just read it over for me, and give me feedback on accuracy of the docs (rather than what is missing or could be improved upon) I would very much appreciate it, as the plan is to include this documentation along with the server for offline viewing as well.

Welcome to BlackTek (https://black-tek.github.io/blacktek/welcome/)

PS. I'm only concerned about the "Server" section right now, the compiling and getting started pages are yet to come
 
Update: We are at 556 commits right now. The in-game account manager also just got some love and is worth checking out.

TFS averages about 326 commits a year for it's life span, with 167 different accredited contributors.

BlackTek has an average of like 276 commits a year for it's life span, and only 27 accredited contributors (and a significant portion of those are simply because I put them as a co-author when I farmed their code change from another repo)

So all in all, we have significantly less man power but are still outputting nearly the same amount of work.

I just thought it was worth mentioning for people who are only barely keeping an eye on this project... since the release of 2.0 is coming up really really soon, you might want to take a closer look at the things happening over at BlackTek right about now :)
 
Update: We are at 556 commits right now. The in-game account manager also just got some love and is worth checking out.

TFS averages about 326 commits a year for it's life span, with 167 different accredited contributors.

BlackTek has an average of like 276 commits a year for it's life span, and only 27 accredited contributors (and a significant portion of those are simply because I put them as a co-author when I farmed their code change from another repo)

So all in all, we have significantly less man power but are still outputting nearly the same amount of work.

I just thought it was worth mentioning for people who are only barely keeping an eye on this project... since the release of 2.0 is coming up really really soon, you might want to take a closer look at the things happening over at BlackTek right about now :)

556 commits are alot in that short of time (my opinion)
Will BlackTek continue to use the CIP client, or will it switch to OTC later? (as main client)
 
556 commits are alot in that short of time (my opinion)
Will BlackTek continue to use the CIP client, or will it switch to OTC later? (as main client)
BlackTek will continue to use cipsoft client until I have provided a client for BlackTek.

The replacement will be written from scratch, in C++, and in no way shape or form will it be another OTC variant.
 
BlackTek 2.0 (Rise After Midnight) has been released

Big thanks to all who contributed and helped make this happen! The main change and full change log can be found in the release description. It has been a long journey and we have achieved many great things. I don't plan on opening a discussion thread about this specific release unless there is a high demand for it, so, we can just discuss anything about it you wish, here.

Special Note: (For those who plan to compile this release)
I forgot to exclude project files from being compressed by script for release, so if you plan to compile, please ensure you follow the compile guide step for step and don't just open the .sln file and try to compile IT WILL FAIL, because that solution file was generated on a github runner, not your home environment. So delete the .sln, .vcproj and .pdb files on windows, and the .make file on linux if you plan to compile and then generate your own project files using the premake (which comes provided in the release) with the command for your desired configuration.

Thanks again to all contributors, I appreciate you much more than I am capable of showing!
 
Back
Top