Jump to content

Distinguishing between Client & Server


crdlpls

Recommended Posts

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.

Edited by crdlpls
Link to comment
Share on other sites

48 minutes ago, crdlpls said:

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.

I think that entity attributes are synced between the server and the client automatically(see NetHandlerPlayClient#handleEntityProperties).

 

48 minutes ago, crdlpls said:

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?).

The snipped above would be executed on both sides. You can trace the call hierarchy of any method using your IDE to see where it is called from. For example EntityJoinWorldEvent here is fired in World#spawnEntity. And World#spawnEntity is called from both WorldServer and WorldClient. So what I am trying to say is - use your IDE to answer questions like this. Either trace the call hierarchy or just place a breakpoint and see which side it is triggered on.

 

48 minutes ago, crdlpls said:

when I need to keep something side-specific

If anything is marked as @SideOnly at any point - that is a strong indicator to keep things side specific. Apart from that all logic should run on the server, the client should do as little as possible. The client's job is to render things and accept input. Mostly everything else should be handled on the server.

Link to comment
Share on other sites

4 minutes ago, V0idWa1k3r said:

I think that entity attributes are synced between the server and the client automatically(see NetHandlerPlayClient#handleEntityProperties).

I'll take a look, if so that makes what I'm trying to do a lot easier, thanks!

5 minutes ago, V0idWa1k3r said:

So what I am trying to say is - use your IDE to answer questions like this. 

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!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • They were already updated, and just to double check I even did a cleanup and fresh update from that same page. I'm quite sure drivers are not the problem here. 
    • i tried downloading the drivers but it says no AMD graphics hardware has been detected    
    • Update your AMD/ATI drivers - get the drivers from their website - do not update via system  
    • As the title says i keep on crashing on forge 1.20.1 even without any mods downloaded, i have the latest drivers (nvidia) and vanilla minecraft works perfectly fine for me logs: https://pastebin.com/5UR01yG9
    • Hello everyone, I'm making this post to seek help for my modded block, It's a special block called FrozenBlock supposed to take the place of an old block, then after a set amount of ticks, it's supposed to revert its Block State, Entity, data... to the old block like this :  The problem I have is that the system breaks when handling multi blocks (I tried some fix but none of them worked) :  The bug I have identified is that the function "setOldBlockFields" in the item's "setFrozenBlock" function gets called once for the 1st block of multiblock getting frozen (as it should), but gets called a second time BEFORE creating the first FrozenBlock with the data of the 1st block, hence giving the same data to the two FrozenBlock :   Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=head] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@73681674 BlockEntityData : id:"minecraft:bed",x:3,y:-60,z:-6} Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=3, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=2, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} here is the code inside my custom "freeze" item :    @Override     public @NotNull InteractionResult useOn(@NotNull UseOnContext pContext) {         if (!pContext.getLevel().isClientSide() && pContext.getHand() == InteractionHand.MAIN_HAND) {             BlockPos blockPos = pContext.getClickedPos();             BlockPos secondBlockPos = getMultiblockPos(blockPos, pContext.getLevel().getBlockState(blockPos));             if (secondBlockPos != null) {                 createFrozenBlock(pContext, secondBlockPos);             }             createFrozenBlock(pContext, blockPos);             return InteractionResult.SUCCESS;         }         return super.useOn(pContext);     }     public static void createFrozenBlock(UseOnContext pContext, BlockPos blockPos) {         BlockState oldState = pContext.getLevel().getBlockState(blockPos);         BlockEntity oldBlockEntity = oldState.hasBlockEntity() ? pContext.getLevel().getBlockEntity(blockPos) : null;         CompoundTag oldBlockEntityData = oldState.hasBlockEntity() ? oldBlockEntity.serializeNBT() : null;         if (oldBlockEntity != null) {             pContext.getLevel().removeBlockEntity(blockPos);         }         BlockState FrozenBlock = setFrozenBlock(oldState, oldBlockEntity, oldBlockEntityData);         pContext.getLevel().setBlockAndUpdate(blockPos, FrozenBlock);     }     public static BlockState setFrozenBlock(BlockState blockState, @Nullable BlockEntity blockEntity, @Nullable CompoundTag blockEntityData) {         BlockState FrozenBlock = BlockRegister.FROZEN_BLOCK.get().defaultBlockState();         ((FrozenBlock) FrozenBlock.getBlock()).setOldBlockFields(blockState, blockEntity, blockEntityData);         return FrozenBlock;     }  
  • Topics

×
×
  • Create New...

Important Information

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