2.1.0
- Added /recipear command for OP
- **reload** will reload config and send out update to players
- **output** outputs recipe list to *Recipear.log*
- Recipes will be banned when user connects to server
- Updated to IC2 2.1.0-409
- Singleplayer is no longer affected
After updating to the latest version I'm having some issues.
Firstly all banned recipes no longer shows as "This item has been disabled by the server" in it's description.
Then when I tries to install it on a server it causes a extremely severe log spam like this: http://pastebin.com/2rDrMGkh
It goes on and on and my log file reaches a few gigs in a matter of seconds.
Also IC2 build 409 is for MC 1.7, the latest build for 1.6 is #397
The Meaning of Life, the Universe, and Everything.
Join Date:
12/17/2011
Posts:
265
Minecraft:
Nanakisan
Member Details
I was curious. Is there anyway to convince you in using the ForgePerms API so that there can be permission nodes for banned items? MyTown a forge server / mcpc+ mod protection system does some prime work. But i could see your mod benefiting from the forgeperms API. Imagine being able to declare a permission node that locks and unlocks specific items and their recipes. Is this at all possible?
Rollback Post to RevisionRollBack
I am a lunatic wrapped in bacon. Sprinkled with swiss, smoothered in mustard and then buried in lettuce. I'm delicious!
that is the thing, if all the crafting involved going through a event like bukkit does it i could easily intervene and prevent any banned recipe based on user if he had certain permission node or not, sadly this is not the case using forge :/ pretty limited.
okay guys, been a long while now(broke my arm not too long ago and finally got some real coding time back :D)
Recipear 2.2.0 will solve all the issues and make force config update on client side, so whenever a client joins a server using Recipear they will always receive latest update, you can choose whether or not you wanna make the items visible in-game or not through the server config which is entirely reload-able by server OP.
this is something i should have done from the start.
tl;dr = Recipear is entirely server side, if user choose to they can have it client side and server will send config.
okay guys, been a long while now(broke my arm not too long ago and finally got some real coding time back )
Recipear 2.2.0 will solve all the issues and make force config update on client side, so whenever a client joins a server using Recipear they will always receive latest update, you can choose whether or not you wanna make the items visible in-game or not through the server config which is entirely reload-able by server OP.
this is something i should have done from the start.
tl;dr = Recipear is entirely server side, if user choose to they can have it client side and server will send config.
Changelog
- Re-factored a lot of the code
- Config are now only generated on the server side(You can use the
reload command anyway)
- Output is now outputted to Recipear-output.log
- Config is now sent to the players along with the banned recipes
- You can safely delete the Recipear client config
- Output process is much more clean, same with reload.
i tested this very thoroughly, should be fairly stable even on mcpc+
you can choose whether or not you wanna make the items visible in-game or not through the server config
I have to say it was disappointing to find out that doesn't mean "hide the item from NEI and the creative tabs". I was so hopeful, when I read that post and the description for the config option...
There doesn't seem to be a single mod to totally nuke an item from Minecraft. The closest I've come is to remove the recipe and also ban it in NEIserver.cfg which is a pain since it doesn't support item or metadata ranges...
Changelog
- Added Thaumcraft 4 support
- Added NEI support(Remove items from NEI using ITEMID:NEI)
- Added ScrapBox and OreWasher for IC2
- Re-factored a lot of code.
- Should go through recipes a lot faster then 2.2.0
4094
but allow
4094:1
4094:2
We are giving a FREE copy of Arma3 or TITANFALL once or YouTube channel hits 100 subscribers!!!
Awesome thanks!Oh ya, is there a way to reload the BannedRecipes without a server restart?
We are giving a FREE copy of Arma3 or TITANFALL once or YouTube channel hits 100 subscribers!!!
Running a clean (no other mods) MC 1.6.4 with Forge 9.11.1.965
Entered block id 0280 for sticks on a single line in the banned config file.
Also entered true for removing things from inventory.
It says the item is banned but i can still craft it and use it.
The item is neither removed from inventory at login or during gameplay later.
Could you please look into it and make it work for later forge versions for 1.6.4 ?
Best regards
Michael
The recipe removal only works server side.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium- Added /recipear command for OP
- **reload** will reload config and send out update to players
- **output** outputs recipe list to *Recipear.log*
- Recipes will be banned when user connects to server
- Updated to IC2 2.1.0-409
- Singleplayer is no longer affected
Download it @ https://github.com/Silentspy/Recipear2/releases
Firstly all banned recipes no longer shows as "This item has been disabled by the server" in it's description.
Then when I tries to install it on a server it causes a extremely severe log spam like this:
http://pastebin.com/2rDrMGkh
It goes on and on and my log file reaches a few gigs in a matter of seconds.
Also IC2 build 409 is for MC 1.7, the latest build for 1.6 is #397
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI still get the console spam after updating
That is what I was looking for, also would be nice if it removed the recipe from nei too, this would be perfect.
[Don't let the offline notice fool you.]
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumRecipear 2.2.0 will solve all the issues and make force config update on client side, so whenever a client joins a server using Recipear they will always receive latest update, you can choose whether or not you wanna make the items visible in-game or not through the server config which is entirely reload-able by server OP.
this is something i should have done from the start.
tl;dr = Recipear is entirely server side, if user choose to they can have it client side and server will send config.
-
View User Profile
-
View Posts
-
Send Message
ModeratorReally? D: Hope you get better soon!
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttps://www.dropbox.com/s/v42q30k7yb33zl2/2014-03-15 19.11.54.jpg
https://www.dropbox.com/s/kkk1a5tovys36st/2014-03-14 09.18.28.jpg
Either way 2.2.0 is out! dl @ https://github.com/Silentspy/Recipear2/releases
Changelog
- Re-factored a lot of the code
- Config are now only generated on the server side(You can use the
reload command anyway)
- Output is now outputted to Recipear-output.log
- Config is now sent to the players along with the banned recipes
- You can safely delete the Recipear client config
- Output process is much more clean, same with reload.
i tested this very thoroughly, should be fairly stable even on mcpc+
I have to say it was disappointing to find out that doesn't mean "hide the item from NEI and the creative tabs".
There doesn't seem to be a single mod to totally nuke an item from Minecraft. The closest I've come is to remove the recipe and also ban it in NEIserver.cfg which is a pain since it doesn't support item or metadata ranges...
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumbut i could def make this a option!
Yes please.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumChangelog
- Added Thaumcraft 4 support
- Added NEI support(Remove items from NEI using ITEMID:NEI)
- Added ScrapBox and OreWasher for IC2
- Re-factored a lot of code.
- Should go through recipes a lot faster then 2.2.0