@jb_aero As far as I can tell from the DataStore class (that class houses most of the public API), you can currently only get claims by their location (that I’m aware of), and I don’t see any static methods in the Claims class (which is the next place I’d expect such a method to be), but also in searching for that, I’ve gotten curious about another thing.
@BigScary, are you ever going to restructure your plugin classes into more organized classes/packages and potentially break the command listener in the main class into separate classes? It’s current structure makes it somewhat difficult to navigate manually (for me at least). Not to be rude though, I’m aware you are/were a professor, so mostly wondering if there’s some benefit of having a plugin structured as it is, or if it’s just the style you prefer? Your logic otherwise is simple enough and easy to follow thankfully (I took over PopDense for a short while before giving it to RoyalDev)
GP isn’t organized well - that was my mistake, thinking no one else would ever work on it. Didn’t want to spend extra time on coding practices that I didn’t think would pay off. As for the future, it’s very unlikely because I don’t believe in refactoring just for the sake of satisfying principles.
PopDensity was even more poorly organized. Congrats on surviving that.
@BigScary I am using the latest version of GP on Spigot 1.8, and it’s great so far. I have some feature requests if you can please find the time.
We run a family friendly server and it is very important that we have a record of chat logs. I LOVE that GP puts sign text in the admin chat, but I was hoping we had a little more control over it. My requests are thus:
Allow us to configure the format of the sign text. Right now it splits the sign text into four lines, which fills up our chat window quickly. It would be nice if each line could be concatenated with a slash or semi-colon or something else that we can configure. Also allow us to configure the placement of the components of the message. Something like [(type}@{coords} in {world}] - {playername}: {text}
Allow us to add color codes into the line, so that player names could be more visible and we could change the color from gray to something else.
Put items which are named in an anvil into the admin chat. Something like “PlayerX named diamond_sword ‘F U’” or “PlayerY named paper ‘u suck’”
Put book text, sign text, and anvil renaming item text into a separate log file for easier auditing. Allow us to control the formatting of this with variable replacements for type (sign, item, book), name of player, coordinates, world, and the text.
What about players who just need griefprevention for land claim i would rly right now use that one becasue i have no idea if there is any for just the land part.And why do you not take in hand that some people host modded servers that use only armor mods or weapons mods that cant affect land.For me i only use a armor based server but i have no claim plugin and that makes me think how can i stop players from destroying my spawn >< sory for long text but i loved your plugin on Bukkit and it made me happy
Griefprevention, one of the most used plugins on any survival server. I am wondering how is the current state? Has porting to sponge started and can we expect to see any builds at some point?
We will wait patiently until griefprevention is available for sponge and revert to other anti grief methods in meanwhile.
I believe he is no longer porting GP to Sponge. Just way too much work for him to do so and with Sponge no where close to being finished nor useable, I do not blame the author for not wanting to waste his time.
This statement alone proves how little you know about Sponge. The SpongeAPI is reaching its beta phase and the implementation has been usable for awhile now with a good amount of the API implemented.
for simple plugins like the essentials spin offs, but the main ones that really help servers thrive are not ported because of time constrictions or lack of events in the api needed for those plugins
Majority of the events that are in Bukkit are not needed in SpongeAPI as the ones we currently have support far more cases and are not specific to vanilla. A perfect example is ChangeBlockEvent. In Bukkit you have events like BlockBreakEvent, BlockPlaceEvent, BlockIgniteEvent that ONLY support players. In SpongeAPI, ChangeBlockEvent covers ANYTHING that changes a block, not just players. I suggest you read up on our current event system within API before stating things you clearly do not know about.
Why so cynical? This community has worked hard to make Sponge far superior over its predecessor. Yes plugins are currently lacking but Sponge is young and will mature over time. The possibilities far exceed that of Bukkit. I foresee great things coming in the future.
You guys look too far into what I said. I meant this current moment in time, hence why not a lot of the big plugins are being ported at this current moment in time
Odd you say that because it literally took us 8 hours today, with quite a few breaks, to port GriefPrevention to Sponge. We are testing it internally now.
Congrats on surviving that.
. Cant wait for it, keep the good work