-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix item duplication if possible #7
Comments
I did deal with the plate duplication bug. Are there any others we should worry about? |
Well there is the sandstone duplication thing. |
We might be able to fix that if we register the recipes with reduced grinding time, but I haven't tested it yet. |
I tested your example for clearing the zinc plate recipe for the Elepower compressor, but it didn't work. I can't clear the grinding recipe either. None of the other recipes I tested were cleared. Are you sure you tested both the recipe clearing functions you made? |
Yes, I tested them. I tried clearing them again in a new download of the repo and it didn't work for some reason, but I fixed it in pull request #17 as well as some other improvements. Remember when using the elepower_clear_recipe function the item string that you are trying to clear needs to be exactly the same as what it is registered as. For example, if you wanted to clear the recipe for silver_sand you would need to do it like the below example because in the elepower table that the recipe is in has the item output number in it.
There is another issue we need to address too. If any code is below the abms for replacing the ores with stone, it won't run for some reason, and this may be an issue with minetest but I am not completely sure. To avoid this problem, I have put the abms in their own file called ore_overrides.lua. |
Because of having elepwer and technic together, some infinite item duplication methods are possible. If possible, we should find a way to get rid of that so that the modpack is able to be used on public servers at some point.
The text was updated successfully, but these errors were encountered: