Bukkit

Hello everybody! Another exciting update for you all.

So after going over MineReaper v1.4, I realized that given the direction MineReaper is heading, and what it is capable of in it's current state, needs alot of work. This was my first plugin as a Bukkit developer, and as I usually code in C# and not Java, many mistakes were made during the learning process. Some of those you all experienced, others I personally experienced while developing. For that I apologize, but I have a solution to this problem.

I have decided to cancel MineReaper v1.4 to work on MineReaper version 2.0! The current version of MineReaper appears to be very stable, and I think it is a great jumping off point for this endeavor. This way I can be less focused on fixing current version bugs, and more feature oriented for the new version.

What does this mean to you as users? It means that the next release will take some serious time, less depending on how much I put in to it. How long is long? A month, maybe less. BUT, MineReaper v2.0 will come loaded with features. I know some of you may find this disheartening, but it will give me a chance to do what needs to be done now, so that it does not become a problem later.

The way MineReaper is set up right now, group discounts are flat out improbable, and that is unacceptable. Which means we are already encountering issues, and the base issue must be addressed immediately to alleviate future issues.

With all that having been said, here is a write-up of the features I am hoping to implement in MineReaper version 2.0 (including current features) all of which are optional.

• Custom Death Messages which can be enabled on a per player, group, world basis
• Custom death taxing which can be set on a per player, group, world basis
• Player ability to opt in/out of using MineReaper death taxing
• Player ability to temporarily insure themselves at a lower rate, for a limited period of time
• The ability for players to insure themselves using a command
• The ability for players to insure themselves using a sign
• The ability to cast MineReaper permissions onto WorldEdit regions
• The ability to use MineReaper as your permissions manager (instead of PEX, bPerms, etc.)
• The ability to allow users to only keep their items or only their experience on death
• Allow every MineReaper command to linked to a permission in case you don't want your admins to have access to ALL of the MineReaper commands.
• More descriptive configuration files and plugin.yml
• The ability to make players, groups, worlds exempt from the death tax
• The ability to make pvp kills exempt from the death tax
• more secret additions that you will just have to wait to see!

Needless to say, the feature expectations are a bit...ambitious. So we will see if we can't fit them all in there, but needless to say it is a new major version, and as such will need to be packed with new features.

Have fun using MineReaper, and I once again thank you all for your continued interest in MineReaper!

@Kalorte

I suppose I could add such a feature, I never considered the fact that somebody would want to do that. Although it will have to come in a later release as this one is booked.

Hello everybody! I hope you are all enjoying MineReaper version 1.3. As you have noticed I have slowed the rate in which releases come out. I know many of you are eager for features, but simply put I have received a few complaints about the rapidity of my releases. So I have agreed to slow the releases to a week in between, unless there is a catastrophic bug of some sort in the current version, in which case I will post a fixed revision ASAP. In the meantime, MineReaper v1.3 appears to be doing excellent, so with that said I am looking to v1.4 being released soon.

As mentioned in a previous post, version 1.4 will include the long awaited group discounts and rates. To shadow these we will see a flux of new permissions, configuration options and commands. Normally since I am waiting a week in between releases, I would release more features, but honestly I spent the last 5 days trying to conceptualize how I am going to achieve group discounts and rates to themselves. Believe it or not, it is a massive undertaking when you have to consider the shear number of permissions, commands and configuration options that will be added. But, I think I have decided on a plan of action, and will be getting started on v1.4 immediately.

@Snirtzoh

If percent rate is false, then it is a flat fee, otherwise it is a % of their current balance. YOU are the one who chooses whether they can keep their experience, items, or both. If you want them to keep experience only, then add the permission minereaper.use.exponly to that player or group. They will be charged, their items will drop on the floor, but they can keep their experience. If you do not want them to be charged, but keep their experience, use minereaper.exempt.exponly. It works the same as the previous, but with no charge. Other than that, the player has no choice in the matter, a feature I am looking into adding in an upcoming version.

@Shirou7000

That is not a bug, it is because minereaper does not support * permissions. When you type minereaper.use.*, it will look, see the permission, grant you usage, tax you if necessary, then check to see if minereaper.use.exponly is true. Normally this would be false, but since you specificied minereaper.use.* as true, therefore, minereaper.use, minereaper.use.exponly & minereaper.use.itemsonly are all true. Checking for EXP only is just the first item it comes to, and therefore because of * evaluates to true, saves your experience, and then exits. If you want them to keep items & experience, use minereaper.use

As far as OP goes, MineReaper is not setup for OPs, as I cannot get this feature to work for the life of me. It is something I plan to correct in the near future, but I have been sidetracked by other minereaper projects for the time being.

@Valon750

So after looking it over carefully, I do not see that this is possible with WorldEdit, because of how WorldEdit is designed. WorldEdit is not designed to define regions where you can add permissions to them. However, if you have a plugin (and I know there are a few out there), that allows you to add permissions to regions, then in that case yes it will work. I found this plugin: http://dev.bukkit.org/server-mods/rsp-region-specific-permissions/ that allows you to add that feature for WorldEdit. What it does is create a group specific for the region, and does it's magic that way. You will have to look it over and decide, but if you do use it then MineReaper should work by adding the appropriate permissions to your defined region group's permissions.

But that was just after my 20-30 minute endeavor with WorldEdit, so I could be wrong. If you can add permissions to a specific region, then yes MineReaper is supposed to work there, is the short answer. Long answer above.

@Valon750: Go

Actually, it might be possible if your server is already setup to use permissions in areas. As the player moves in and out of those regions they temporarily gain/lose permissions associated with that world, group, player, etc. I would imagine its the same for regions, so in that case it may work. I will look in to this.

@Dyspen: Go

And this bug is related to MineReaper? There are two things I know about plugins, one is that they are completely independent of each other and supposed to be unable to interfere. The second is that a bad programmer can make it interfere by getting too creative with their code. But MineReaper doesn't at all get creative, only makes use of what is already there, which makes me wonder how Mob Arena works.

I haven't used mob arena before. What does the player do with their gear when they go in to the arena? Do they still have it but can't use it? Do they stash it? Does Mob Arena temporarily remove it from them until they leave the arena? Let me know how Mob Arena works on your server, in the meantime I will set it up on mine and do a little bit of testing.

@DeadDragons

Yeah I am sorry buddy, but there is a very narrow margin of people having this issue, and I have already done the very most I can to resolve it. Most everybody else seems to have it working just fine, so at this point I am going to have to say it is something on your end, and from that view I have no idea what the problem is. I am afraid I just cannot help you any further, sorry =\

So, I wanted to give everybody an update on how MineReaper development is going. Version 1.3 and 1.4 development is underway and I must say after looking at what I have for everybody, I hope you are prepared.

Get ready for a massive change in the way MineReaper operates on your server, and a boatload of new feature permissions and commands. MineReaper 1.3 will see an overhaul to the current permissions. Most of the old permissions have been eliminated, and in their place you will see many new permissions for pin point accuracy on how MineReaper interacts with your players. The new version will also see numerous bug fixes.

Version 1.4 will see more permissions, commands and configuration options designed specifically for group rates and discounts.

The reaping is at hand ladies and gentlemen, are you ready?

• EDIT* Pushing v1.3 for approval now, have fun everybody.

@Cypho342

That I can and will do. I will throw minereaper.itemsonly and minereaper.exponly into the next version.

@Steelsouls

Okay, so after hearing about your error what I did is I went in to the system and added a check to the player quit event, that checks if they are in the saved items tables, at which point it restores their items. I had to change quite a bit around, but that works fine. We will see those changes in 1.21b The reason this was happening is because when a player dies, their items are saved in something called a Map, which maps the player to a copy of their old inventory. However, when the player logs out, then back in, they are a different instance of player, if that makes any sense. So the player in the Map, is not the same player as the one logging back in, thus items lost. I managed to fix this by linking the player's name to their inventory instead of the player object itself.

Also, I am not experiencing the issue you are with the experience loss though. When the player is covered on the tax, MineReaper sets the experience loss value to false, so they never actually lose it. It does not at any point take it away or give it back at any point, it just sets player.lostexpondeath = false. What it DOES do though, is set your dropped experience and items to 0, otherwise the player would drop duplicates. I struggled alot with this while building MineReaper, the way experience works for MineReaper is the only possible way any plugin could do it on Bukkit. Have you tried removing MineReaper and seeing if the experience issue persists?