Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/05/19 in all areas

  1. So i installed forge for 1.14.4 but when i open my launcher the forge version doesnt appear... Its only showing me simple 1.14.4 without forge.. The forge profile is not there
    1 point
  2. 1 point
  3. I'll try, but it will likely start with the basics ?
    1 point
  4. AnimeFan8888 is right about returning ItemStacks. That would definitely cause an issue like this. You should have getWorkbenchResult() return like this: return ((ItemStack)ent.getValue()).copy(); There's a pretty good chance that will solve your problem. It certainly can't hurt. --- I don't know if it helps because it might be total information overload, but the recipe management system for my mod is here: https://github.com/jaminvanderberg/AdvancedMachines/tree/master/src/main/java/jaminv/advancedmachines/util/recipe. It includes a three-ingredient recipe manager that handles ingredients in any order, ore dictionary, etc. There's a lot there because recipe management can get quite complicated. But if it helps, great.
    1 point
  5. 1 point
  6. Looks like that method is from 1.9.4 so no. Use ItemStack#copy
    1 point
  7. That is strange. It's even more strange that it the count is 1 at first and then changes it to 2. Since the update() routine is never performed on the client, it's likely not a client/server desync at the tile entity. It seems like it's happening somewhere in the container, but I don't see it. Unfortunately, I don't have time to debug through all of your code and I can't really run it yourself. You should trace through it and watch it happening step by step. I suggest subclassing ItemStackHandler and override the onContentsChanged. You can even narrow it down by creating an if (slot == 2) {} statement with a dummy operation in it, and add a breakpoint there. When you hit the breakpoint, you can look at the stack trace and see everything that it causing an update to the slot. @Override protected void onContentsChanged(int slot) { if (slot == 2) { int a = 0; // Breakpoint here } }
    1 point
  8. 1.14.4 Everything is still being implemented so the latest is the best at the moment.
    1 point
  9. One way you could speed up ticks would be to scan the AOE for TileEntities that implement ITickable and then manually call update(). Since update() is also being called by the game tick clock, any additional time you called it would speed up any machines in the area. Obviously, this is basically the definition of a lag machine, so make sure any loop code you add is as lean as possible. I have no idea how you'd slow down tick clocks. You could easily do it for TileEntities that you control by simply skipping update() ticks based on a state. I don't know if there's a way to do it in a general-purpose fashion. I know that there are items in mods that speed up ticks. If their code is public, you could certainly scan through their code and see how they do it. I don't know if there's any objects the slow down ticks. If you know of one, see if you can find code for it. If not, it may not be possible.
    1 point
  10. Like Draco said, the ItemGroup constructor is called before your ItemInit.moditem has even been created. Generally, you can assume that ItemGroups are created before Items are. This is what I do to get around it: public class ModItemGroup extends net.minecraft.item.ItemGroup { private IItemProvider icon; public ModItemGroup(String label, IItemProvider icon) { super(label); this.icon = icon; } @OnlyIn(Dist.CLIENT) @Override public ItemStack createIcon() { return new ItemStack(icon); } } public static final ModItemGroup modItemGroup = new ModItemGroup("ModItemGroup", ()->(ItemInit.moditem)); Normally I would use Supplier<Item> here, but IItemProvider already does the same thing with better integration such as being able to be passed directly to an ItemStack's constructor. This doesn't care whether moditem has already been initialized when modItemGroup is created. It only needs to exist by the time modItemGroup.createIcon() is called. Either way though, static initializers are unpredictable and that's why I personally avoid them wherever possible.
    1 point
  11. i have the same problem. I'm installing it with installer and then i launch the game but there not a 1.14.4 forge version. I try to install manuel with universal but i have the same problem. when i get in to versions there are forge folder but there is not a .jar file there is only a notpad named 1.14.4 forge. I've been trying to install it since 2 days but there is no solution. I tried to delete .minecraft and launch 1.14.4 then install forge and launched again but no surprise, there is no forge version again. There is only a profile with nothing. Pls fix it (forge version is not at the bottom too)
    0 points
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.