Jump to content

crdlpls

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by crdlpls

  1. I'll take a look, if so that makes what I'm trying to do a lot easier, thanks! Hadn't thought about it that way, forge is a very different beast to anything I've worked with before. I'm gonna have a deeper look into the actual sever/client code and see what I can get heads and tails of. Thanks!
  2. Hi there, I've just started learning about forge and how it works (Java's not an issue), reading as many tutorials as I can but also trying to go 'off book' so to speak. One thing has always been nagging at me that I really can't seem to find an answer for. I get that some things are "client only" and "server only", and that you need to send packets between the two. My issue comes with distinguishing when I need to keep something side-specific, and when things will just work without needing to manually send packets between the two. An example being lets say I write a handler (not copied from anything so it might be wrong, if so please correct me) : @SubscribeEvent public static void onEntityJoin(EntityJoinWorldEvent event){ Entity entity = event.getEntity(); if (entity instanceof IMob && entity instanceof EntityLivingBase) { entity.setCustomNameTag("Boss"); entity.getEntityAttribute(SharedMonsterAttributes.MAX_HEALTH).setBaseValue(100); entity.setHealth(100); } } That makes sense to be executed on both client & server to me, as both the client and the server need to know about these changes for HP tracking etc, but I don't know if I'm thinking about it the wrong way. My issue comes basically from knowing what code is executed on the client side vs the server side (for example, would something like the snippit above i.e. event handlers execute on both sides?). Sorry if it's a really stupidly obvious question, I don't want to just be writing code just because that's how the docs are written, but I really want to understand how everything works. There's a lot of "just do this" in tutorials, but not so much why.
×
×
  • Create New...

Important Information

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