Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Electric Update #92

Closed
8 tasks
fynntimes opened this issue May 7, 2018 · 3 comments
Closed
8 tasks

The Electric Update #92

fynntimes opened this issue May 7, 2018 · 3 comments
Assignees
Labels

Comments

@fynntimes
Copy link
Member

The next major release of Prison, the Electric Update (API 4), will contain massive overhauls to the code structure.

Main goals

  • Remove Prison's multi-platform support, which caused a lot of unnecessary overhead and code jumbling without multiple platforms to, well, support.
  • Remove Prison's third-party module system, since third-party features can be added via another Spigot plugin anyway (no need for our own API).
  • Revamp the storage and localization systems (since these data are now static and not dynamically defined).
  • Use lucko's fantastic helper system to reduce the footprint of our codebase and make things easier.

This is a primarily structural release, but user-facing features are planned as well!

  • Implement scoreboard support.
  • Implement GUI menus.
  • Make mine and rank data fully editable in-game.
  • Expand integrations for permissions and economy systems.

Current target release date is sometime in August 2018.

@Perksey
Copy link
Contributor

Perksey commented May 7, 2018

Remove Prison's third-party module system, since third-party features can be added via another Spigot plugin anyway (no need for our own API).

Why? The module system is a clean way to implement third party modules! I don’t see why we should remove it...

@fynntimes
Copy link
Member Author

@DylanFPS I'm going to sit down and take a look at the current architecture of the plugin and see how it can be optimized further. The goal is to get rid of as many bloated features as possible. If the module system is actually optimal, then it'll stay!

@Perksey
Copy link
Contributor

Perksey commented May 7, 2018

Alright. In my opinion, we should keep the module system, but if the enable/disable system is still in there remove it as that's bloated.

@Perksey Perksey closed this as completed Jul 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants