Bukkit

@Curtis4321

Could you be more specific. As far as I'm aware, except the bug discussed below in this comment, floAuction is fully compatible with 1.4.5.

@Grave9912

I don't know what "old" ways you're talking about in regards to this. As long as floAuction has existed, the time has been after the min increment. Anyways, I know what you want, and I'm taking it into consideration with floAuction3. I'm hoping to actually get to work on this while everyone else is celebrating holidays that I don't celebrate.

@EatingEmoKids

I'm not seeing exactly this problem but I am seeing a stacking issue. Every time I auction anything I've tried I'm getting them returned (when I cancel) in proper stack amounts. I've been having a difficult time trying to figure out the stacking issue, but your info about a full inventory has been very helpful. It seems that "player.getWorld().dropItemNaturally(player.getLocation(), itemStack);" is now dropping a single entity of the item type and not checking the stack max when they pick the item up. Who knows how long this has been going on? It's easy enough to work around as I can just loop through and drop naturally stacks with the max stack size (or less). I'll get that in 2.7.2 tonight.

@Grave9912

Don't take this the wrong way, obviously you can run your server the way you want to, but it sounds like you're underestimating the intelligence of your players. A bid increment of 200 could be extremely high or extremely low depending on the currency value and item(s) being auctioned. Allowing the auctioneer to set a minimum increment lets him provide more flexibility to the potential buyers by being able to set the starting bid lower initially with the hopes of drawing in a crowd.

Say, hypothetically, I was on a server where a diamond sold for, idk, $1 (I've never seen a currency with a base unit this low relative to a diamond, btw) and I wanted to auction a whole stack of diamond blocks. First, I have to take into account that in such mass, people expect wholesale prices so I have to lower the starting bid from $576 to $400 in order to guarantee a starting bid. Since I know most people use /bid by itself to bid, (and for this example, let's say everyone is) if there are 10 bids, the ending price would be $409. In order to get closer to the actual worth, I'd have to start the bidding at $500 which may be more than what will garner the initial bid (that first bid is the hardest to get). But, if I were able to (as the auctioneer) make it such that the bids have to go up by $10 instead, then I can have a bit more guarantee that I will get a proper return on my material and therefore be more likely to actually start the auction. While there may only be 7 bids instead of 10, $460 is a sight better than $409.

Because of this, forcing the bid increment to always be $1 (or whatever your base unit is, $.01 is common too) limits your players in what they can auction reasonably. Someone probably will not want to auction an enchanted diamond pickaxe with the best possible enchantments if they can't be guaranteed a competitive market. By limiting what your players are willing to auction, you limit what they are able to buy (this should be obvious) and therefore are inhibiting your economy.

The config option, max-bid-increment, in such a situation where a diamond is worth only $1, should probably be between $20 and $50. But even the default value for that is $100 so with a fresh config file your players would never see a $200 bid increment.

There's a dual concern here for me, one, that limiting your auctioneers to the extreme of allowing only $1 increments decreases the game value to your players, making your server less worthwhile but probably to a negligible degree; but also that doing so gives your players a false impression of how flexible floAuction is, though probably also to a negligible degree.

My main point in writing all this is to hope that you will consider returning the flexibility inherent in the bid increment feature ultimately for the sake of your players. But it also gives me the idea to make a quibid style auction mode. I'm gonna have to start a wiki for all these features, it's getting much to complex to be a list.

@mrcashking228

Any additional information would be great. I might recommend downloading a fresh copy of CraftBukkit and see if that helps. This, "java.lang.NoClassDefFoundError: org/bukkit/craftbukkit/inventory/CraftItemStack" is saying it can't find part of CraftBukkit. I'm not sure what would be causing that unless you are trying to use this without CraftBukkit somehow, or you have a bad download. But honestly, I have never seen this error before and can't be positive.

@CipherMagi

Thanks for the encouragement.

@DrPhil111

As kbryantLA24 said, there's a language.yml file. It has all the text that floAuction outputs EXCEPT item names which are operated by WhatIsIt and come from the names.yml file from that plugin. If you want a particular line to not display, set it to empty (that's two apostrophe's (') next to each other. The line you're looking for is "chat-prefix."

@kbryantLA24

Good to hear it. Much of that code came directly from CraftBukkit. I mainly made it use my item comparison instead of theirs which ignored the head owner value. I'm guessing that Minecraft server itself is operating the picking up and getting items from chests and stuff at a lower level than the public function Bukkit has.

@kbryantLA24

2.7.1 should fix your head issue.

@kbryantLA24

It depends on the min bid increment as well. If the min bid increment is 20, one person bids 100 and has a max bid of 140, then the next person bids 130, the max bid will do nothing because the next possible bid is 150. Also, check your config to make sure you didn't turn that feature off.

About the heads...I was out of town and then things have been busy since I got back. I'd probably take a look right now, but Minecraft login server are down.

@kbryantLA24

Try what deaddude22 said. Let me know if that doesn't fix it (it should).

@WayGroovy

Thanks man!

@Bobacadodl

I appreciate the thought.

@deaddude22

Thanks man :).