Bukkit

@Wannab007

Well that's why. It doesn't automatically make potions stackable. You have to add the id or name to defaultItems.yml or a player/group config.

By default, it sets the 'All items Max' node to -1 which is saying to use default values. If you want to override all items, you could change that to 64 and all items will stack up to 64. If you just want potions, you can add a line '373: 64' without quotes.

@Wannab007

I need to know what your defaultItems.yml looks like as well as any other plugins you are using as those stack just fine for me.

@KnightsOfTables

That is not too surprising, but should be easily fixable. It does seem odd that you can use a single sign to do that though. Thanks for the report. I'll test it out tonight and see what's going on.

@piousminion Commands are planned for the very near future and a reload will be easy to add with them. I do not run a large production server, so I do not come across this. This is why I released it with basic functionality early to get feedback and comments about it.

@HavenOfKairos

That is the first thing on the Todo/Ideas list above so it is known. I attempted to fix this before the last update, but ended up reverting it due to it being inconsistent, unreliable, and occasionally duplicated items. I'll be taking another look at before the next update, but I cannot promise anything.

@ZarethD

It's impossible for me to tell when you post it in a line like that, try using code tags. They look about like this: <<code>><</code>>

My guess would be that it's not valid yaml. Try running it through an online parser, such as this

Also, check out the plugin's wiki if you still need help.

@ZarethD

That depends on what permissions plugin you are using. I only have experience with PEX, but it should be similar for the others.

You should just need to add the '- stackableitems.stack' node under the group or player node you wish to have this.

@ZarethD

I changed the files around a few versions ago when adding stuff, so config.yml was where everything was held. It is now in defaultItems.yml and any custom file names you make associated with permissions.

@ZarethD

First of all, if you were supposed to delete the files in the config after you installed it, that wouldn't really make much sense. It may not be the clearest thing though, and I'll try to see what I can do about that in the future. The files each have their purpose and if you delete them, they'll just get remade anyway.

For gold ingots, you can use either GOLD_INGOT, gold_ingot, or 266. If you are unsure of what something is called, you can use the id or look it up here: http://jd.bukkit.org/doxygen/d7/dd9/namespaceorg_1_1bukkit.html#ab7fa290bb19b9a830362aa88028ec80a

I'm not sure why you would think deleting a line in a file would be your best option. Virtual Items is a feature that is not fully implemented that you are free to set to true if you wish. It just could cause duplication of items, or loss of items in the current state.

You can ignore config, customTools, and defaultTools as they won't apply to you. What you need to edit is defaultItems.yml or see above for permission based files.

The proper use then is:

All items Max: -1
GOLD_INGOT: 100

Yes, you do need to do something with permissions. Any person or group that you want to be affected should have the permission node listed above.