Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/26/20 in all areas

  1. There will be a log file generated by the server (even without a crash, it will be in the logs folder, probably called debug.log or latest.log); post that in a github gist or pastebin or something, and link to it here, someone will see it and probably know what's up.
    1 point
  2. Extend that specific mob class but make a new entity type. Boom, no rebuilding and everything remains the same.
    1 point
  3. Yeah I just learned forge coding yesterday so I didn't really know about the mode stuff haha, but thanks alot I put that and it worked, love u ❤️
    1 point
  4. What do you mean you don't know what to put as mode? How would you like the explosion to behave? Destroy blocks: Choose Explosion.Mode.DESTROY Break blocks and drop the block item: Choose Explosion.Mode.BREAK Leave blocks unharmed: Choose Explosion.Mode.NONE
    1 point
  5. Well i agree that solving is the best part, i think it's just that i tried to do too much too fast, i just woke up now and i have been now looking at libraries trying to understand what's left to do for the last hour, also i have to thank you for not just giving me the solution, i just didn't realise because i misread, i really want to learn, i guess i'll just have to brainstorm a lot, so thank you again, i'll give you an update if i can find anything (i'm a bit late now but as you saw, yes, yes it does)
    1 point
  6. To be honest, the most fun and exciting part of modding (and programming in general) is the problem solving part. The joy and excitement you feel when you solve a difficult problem and the whole mod falls into place. I don't want to rob you of that feeling by handing any more code to you. I would rather see that you solve this last part by inspecting vanilla code, looking at online tutorials, and of course by using your own ingenuity. (This is not to say that you should never ask for help on the forums, but I firmly believe that you are smart enough to solve this problem yourself)
    1 point
  7. I know this topic is a bit old, but I just had the same issue and a Google search points here. If your packet is working correctly, and its just the warning in the log, you've likely made the same mistake as me. Inside the "messageConsumer" you provided when registering your packet, you need to set the packet handled flag to true. "context.get().setPacketHandled(true);" If it isn't set to true, NetworkHooks.onCustomPayload will return false, and ClientPlayNetHandler.handleCustomPayload will post the warning
    1 point
  8. To get blockstate use Block#getDefaultState() Block is the block you want to place, you can get it from block list like Blocks class To get block by registry name, try going through ForgeRegistry
    1 point
×
×
  • Create New...

Important Information

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