Im guessing you became busy or are waiting on a certain part of the API?
at this time i make the random and i fix some little bug and when all it’s okay i make the update
hows this coming along? would like to give a little donation soon as you keep working on the plugin
Sorry i have some little probleme my GF is in hospital i need to be with her
New update 2.0 Who add keys system and a random give with percentage
New config for new update
Can you update the new config? Also can you put keys to use as example? And we will edit it
example
LootCrate {
LootCrate {
Crate1 {
description=“its the description of the Crate”
# you can use to replace by the player who use the crate
list=[
“give stone 10 5”,
“give stone 10”
]
random=true
# You can choose between item or command for the value
system=command
key=true # this line is a new line to add for set if you use key or not
}
}# you have to add LootKey and in LootKey put a container named the name of your crate in this case Crate1
LootKey {
Crate1 {
}
}
}
i’m going to make a version for API 4.0
Oh so the new version is still on the old api then sir?
Yes of course because i have No time to update now in 4.0
Any way to possibly make this open source so others can update or help out? Because as of right now, it doesnt even work. Generates no new config and if you paste in the new one, it throws errors when reloading and clears out the config again.
send me you’r config i look and modiy it to make it compatible with new update
Thats the problem, it generates a blank one
what’s you’r version of sponge
The latest. Believe it was 1215 as it fixed an inventory issue that they were having.
the probleme is the plugin was not compatible to API 4.0 for the moment
If you do not have the time to update the plug in for the new API can you open source the project or send the people who would like to use it so they can update it themselves? I really would love to be able to use this with the new API so I do not have to downgrade.
I m updating to new api but i have some trouble with config i m going to solve it
New update 3.0 For API 4.0.1