Our current direction for SourceBans++ is the release of 1.7.0, which is long due since the last version was well over a year ago.
Since the previous release, there have been hundreds of commits to the repository. Thanks to the numerous contributors to the repository.
The primary objective of 1.7.0 release is to rewrite, stabilize, and fix various backend bugs that crippled the full-extent of usage.
It also means that the frontend template rewrite is pushed back to potentially the next minor semver.
Of course, being there's only so much you can do building on the existing old codebase, a rewrite is almost imminent.
This is where we need your feedback and ideas.
Moving away from PHP
We are looking to move away from the PHP stack to potentially Rust/Golang/Nodejs. However, due to a good majority of the population base using shared hosting, which is limited to PHP, we are not confident that this is a feasible transition for many.
One of the many entropies of the original codebase is the utterly bloated core codebase. Hence, it includes features that weren't necessary for the average user but built-into the core.
Our goal for the rewrite is to minimize the amount of code and features within the code. Provide only the essentials but expose a powerful interface for building upon the core.
Related issue: https://github.com/sbpp/sourcebans-p...s-faq/issues/6
Translation and Templating
One of the most significant issues that still reside within v1 is the templating system.
The unnecessary abstraction created by xajax made it quite difficult and tedious to create custom templates/themes; this also hinders the ability to translate the system into another language.
This is on top of the awkward chaining of templates, which made styling difficult.
Plugin-Side of Things
Similar things could be said about the plugin side of things.
While efforts were made during the syntax transition, there are still broken features and entropies.
With that said, we are prepared to rewrite the plugin along with the web panel for SP 1.10+