Guild Name Permission

Context

I need plus permissions into guild, with the guild name. That would look like this: guild.name.{guildname} .For example if I am in a guild called OKF, I would have a guild.name.okf permission. That would help me a lot. And other people could create many new features with it.

Enyzat

[darbyjack]

It’s funny cause I’m actually the other way around. While I know how to program, I’m only recently new to programming as a whole over the past few years. I’m not that good with coming up with ideas, but I know how to turn ideas into code.

I will make sure to leave this issue open so I remember to check this out from time to time in order to keep it alive and a possibility.

One thing I’ll probably do is look for some kind of software I can use while testing to get some in-depth results on how different methods/functions work for memory and whatnot.

Currently, the way JSON implementation works is that on the startup of the server, the plugin will loop through all the files in the data folder and then we use a library called GSON (developed by Google) to deserialize the files into actual Guild objects. While the server is running, all those objects are constantly being modified via in-game actions such as creating new guilds, members joining, members leaving, and whatnot and so on. Then, when the server shuts down, the plugin will go and grab that list of Guild objects and then save them back into the respective files.

Once I’m able to sit down and do some testing, I’d be able to see how much memory is currently being used and if/how I can optimize it to make it work better on the server.

The good news is I have not heard of any kind of memory leaks so I feel the foundation of data storage is fairly solid right now, but everything can always be improved.

If you or your wife have any suggestions/ideas, I’m 100% open to talking to people who have been doing this longer than I have. I know I have a long ways to go and there are many ways that this plugin could still be optimized.

I’m just trying to give the players the best I can!

[AeSix]

Unfortunately I’m not skilled as a programmer. I could probably do all the work myself, but it’d be Christmas before I got something working lol.

I’ve been around a long time, I understand the concepts and principles. My wife is a developer, has been for 25+ years, and over the last several that we’ve been together, she’s taught me a lot.

I’m better at bash, commandhelper scripts than I am with Java - but even bash and CH can utilize multiple methods of data storage, and so I’ve do a lot of research into that for some projects I’m working on.

What I’ve said could be done over time, even be able to create the guild-members.json file, and just not use it for a few versions, just make sure it’s working properly. Then enable a “experiemental” setting in the config to allow admins to test it for readability at some point. Keep duplicating the data in guilds.json and guild-members.json, as need until the time comes to stop writing members to guilds.json - and just ignore the members that are there (making sure they’ve been added to guild-members.json, of course) That too could be confusing, but if they’re playing with an experimental feature, which could be outlined in comments in the config file, then they should have some understanding of what they’re doing.

As far as more pressing issues, I understand that as well. I feel the route I’ve laid out could be beneficial to both the advent of MySQL storage as well as tertiary features (perms). It could be something done over time, as I pointed out above - but it would be a lot easier to implement when/if the time comes, if decisions going forward keep that route in mind.

Good luck!