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

Resource management #106

Closed
Protonull opened this issue Jan 17, 2021 · 1 comment · Fixed by #302
Closed

Resource management #106

Protonull opened this issue Jan 17, 2021 · 1 comment · Fixed by #302
Labels
enhancement New feature or request

Comments

@Protonull
Copy link
Contributor

What would you like added/changed?

It would be great if extensions had access to an established resource management API. What do I mean by that? Take Bukkit/Spigot/Paper for example and how it handles plugin configs, where config files are stored within the plugin jar and can be saved into the plugin's data folder, and when loading the config, the plugin prefers the data file rather than the internal resource. Though if added, it would be great if this were expanded to any arbitrary file rather than just a specific config file.

Why do you think this is a good addition/alteration?

It would establish a standard within extensions (that can be made specifically thread safe if necessary) meaning reduced duplicate code, as well as explicit support for data files, particularly human readable data files.

Why do you want this to be added?

So I can just save / load config files and other such things and get on with making my extension.

@KrystilizeNevaDies
Copy link
Contributor

Currently working on an api using MAML, a new file format similar to ini and json, for this.

Although using arbitrary files is simple enough to do without an api, is it not?

@KrystilizeNevaDies KrystilizeNevaDies added this to Low priority in Issue Priority Mar 3, 2021
@kezz kezz added the enhancement New feature or request label Apr 1, 2021
Issue Priority automation moved this from Low priority to Closed May 21, 2021
FrederikHeinrich pushed a commit to FrederikHeinrich/Minestom that referenced this issue Jan 26, 2024
* upgrade: infinite potion duration

* fix: no more aqgit

---------

Co-authored-by: mworzala <mattheworzala@gmail.com>
mworzala pushed a commit that referenced this issue Feb 9, 2024
* upgrade: infinite potion duration

* fix: no more aqgit

---------

Co-authored-by: mworzala <mattheworzala@gmail.com>
(cherry picked from commit bb4d925)
mworzala pushed a commit that referenced this issue Feb 9, 2024
* upgrade: infinite potion duration

* fix: no more aqgit

---------

Co-authored-by: mworzala <mattheworzala@gmail.com>
(cherry picked from commit bb4d925)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

3 participants