Jump to content

Trouble Communicating Between Sides


Tablock_

Recommended Posts

I am trying to make any LivingEntity that collides with a custom projectile ride the player. However after some testing, Projectile$onHitEntity(EntityHitResult entityHitResult) is client-side only, and both the client and the server need to be notified that an entity is riding another. Is there a way to comminate to the server?

public class Carrier extends Snowball
{
	private LivingEntity player;
	
	public Carrier(Level level, LivingEntity player)
	{
		super(level, player);
		
		this.player = player;
	}
	
	@Override
	protected void onHitEntity(EntityHitResult entityHitResult)
	{
      		//client-side only
		entityHitResult.getEntity().startRiding(player);
	}
}
Link to comment
Share on other sites

Ok, I didn't think about how that variable caused a memory leak. I used getOwner() instead but get the same result.

public class Carrier extends Snowball
{
	public Carrier(Level level, LivingEntity player)
	{
		super(level, player);
	}
	
	@Override
	protected void onHitEntity(EntityHitResult entityHitResult)
	{
		getOwner().playSound(SoundEvents.BREWING_STAND_BREW, 0.5F, 0.4F / (level.getRandom().nextFloat() * 0.4F + 0.8F));
		
		entityHitResult.getEntity().startRiding(getOwner());
	}
}

EDIT: I meant to say server side only in my previous message

Edited by Tablock_
Link to comment
Share on other sites

11 hours ago, diesieben07 said:

getOwner can return null. You must handle this.

Got it

11 hours ago, diesieben07 said:

Yes, that is correct. You want it server side only.

Ok, I want an entity that comes in contact with the projectile to ride the player. I do this by calling entityHitResult.getEntity().startRiding(getOwner()) (assume getOwner() is handled). But when I run the game, only the server believes that the entity is riding the player. I know this because the entity still appears in the same location when hit, but its drops spawn above the player's head when killed. I must somehow tell the client that the entity is riding the player too. 

Edited by Tablock_
Link to comment
Share on other sites

I do not have a git repo, unfortunately. That is a good idea though, I will be creating one in the future. But since I'm running low on time at the moment I will give you it here directly. Note that ID$newItemProperties() just returns new Item.Properties().tab(Main.MOD_TAB).

public class EntityCarrier extends Item
{
	public EntityCarrier()
	{
		super(ID.newItemProperties());
	}
	
	@Override
	public InteractionResultHolder<ItemStack> use(Level level, Player player, InteractionHand interactionHand)
	{
		ItemStack itemStack = player.getItemInHand(interactionHand);
		
		player.playSound(SoundEvents.BONE_BLOCK_PLACE, 0.5F, 0.4F / (level.getRandom().nextFloat() * 0.4F + 0.8F));
		
		if(!level.isClientSide)
		{
			Carrier carrier = new Carrier(level, player);
	        
			carrier.setItem(itemStack);
			carrier.shootFromRotation(player, player.getXRot(), player.getYRot(), 0.0F, 1.5F, 1.0F);
			
			level.addFreshEntity(carrier);
		}
		
		return InteractionResultHolder.consume(itemStack);
	}
}

public class Carrier extends Snowball
{
	public Carrier(Level level, LivingEntity player)
	{
		super(level, player);
	}
	
	@Override
	protected void onHitEntity(EntityHitResult entityHitResult)
	{
		entityHitResult.getEntity().startRiding(getOwner());
	}
}

And if you need it, this is how I am registering EntityCarrier:

public static final RegistryObject<Item> ENTITY_CARRIER = Main.ITEMS.register("entity_carrier", () -> new EntityCarrier());

Do you think this isn't working because I need to create my own entity type? I'm stumped. If you would like anything else please let me know.

Link to comment
Share on other sites

I have tried to follow what you have asked of me, but I get this error:

Cannot invoke "net.minecraft.client.renderer.entity.EntityRenderer.shouldRender(net.minecraft.world.entity.Entity, net.minecraft.client.renderer.culling.Frustum, double, double, double)" because "entityrenderer" is null

 

I have registered a new entity like so:

public static final RegistryObject<EntityType<Carrier>> CARRIER = ENTITIES.register("entity_carrier", () ->
EntityType.Builder.<Carrier>of(Carrier::new, MobCategory.MISC).sized(0.25F, 0.25F).clientTrackingRange(4).updateInterval(10).build("entity_carrier"));

Please disregard how messy this is. I would like to get it working first. This is my custom entity class:

public class Carrier extends ThrowableItemProjectile
{
	public Carrier(EntityType<Carrier> entityType, Level level)
	{
		super(entityType, level);
	}
	
	public Carrier(Level level)
	{
		super(Main.CARRIER.get(), level);
    	}
	
	@Override
	public Packet<?> getAddEntityPacket()
	{
		return NetworkHooks.getEntitySpawningPacket(this);
	}
	
	@Override
	protected void onHitEntity(EntityHitResult entityHitResult)
	{
		entityHitResult.getEntity().startRiding(getOwner());
	}

	@Override
	protected Item getDefaultItem()
	{
		return ID.ENTITY_CARRIER.getItem();
	}
}

And if you need it, my item class:

public class EntityCarrier extends Item
{
	public EntityCarrier()
	{
		super(ID.newItemProperties());
	}
	
	@Override
	public InteractionResultHolder<ItemStack> use(Level level, Player player, InteractionHand interactionHand)
	{
		ItemStack itemStack = player.getItemInHand(interactionHand);
		
		player.playSound(SoundEvents.BONE_BLOCK_PLACE, 0.5F, 0.4F / (level.getRandom().nextFloat() * 0.4F + 0.8F));
		
		if(!level.isClientSide)
		{
			Carrier carrier = new Carrier(level);
			
			carrier.setItem(itemStack);
			carrier.shootFromRotation(player, player.getXRot(), player.getYRot(), 0.0F, 1.5F, 1.0F);
			
			level.addFreshEntity(carrier);
		}
		
		return InteractionResultHolder.consume(itemStack);
	}
}

 

18 hours ago, diesieben07 said:

I would recommend keeping a DeferredRegister and its entries in the same class. The DeferredRegister field should just be private. This ensures the proper initialization of things, which you must otherwise achieve in other way uglier ways.

My entries will be in the same class and be private. I am trying to get it working first then clean up. No I didn't handle getOwner() yet. I also didn't make a git repo yet, I understand how much easier that will make this. I will try to set it up before you hear back from me.

Edited by Tablock_
Link to comment
Share on other sites

That makes sense. I did that and the Carrier entity renders correctly with no error now. However, entities still do not ride the player correctly after being hit with the Carrier projectile. Again, the server knows that the entity is riding the player, but the client is clueless. I created a github repository, here it is: https://github.com/Tablocked/MyFirstMod. Hopefully you can see it with no issues. I set up my entity renderer in a class named Client. I already showed you every other class that you should need.

Edited by Tablock_
Link to comment
Share on other sites

16 hours ago, diesieben07 said:

The root of your Git repo should be at your project root (where your build.gradle is).

Got it, its changed now.

16 hours ago, diesieben07 said:

What the heck is this?

This was to load the ID class so that all of those static fields were initialized before I called DeferredRegister$register(IEventBus bus). I removed that now and replaced it with a new method I created: ID$init().

17 hours ago, diesieben07 said:
if (!level.isClientSide && getOwner() != null) {
	entityHitResult.getEntity().startRiding(getOwner());
	if (getOwner() instanceof ServerPlayer ownerPlayer) {
		ownerPlayer.connection.send(new ClientboundSetPassengersPacket(ownerPlayer));
	}
}

This did it! But I have a couple questions on why this works.

  • Why do I need to check if its server side? Isn't it already server side only?
  • What exactly is ServerPlayer? I see that it extends Player, but what's the difference?
  • Is ClientboundSetPassengersPacket telling the client that the entity is riding the player?

Thanks as always.

Link to comment
Share on other sites

22 hours ago, diesieben07 said:

If you didn't use that ass-backwards way of registering things, you would not need hacks like this.

This is not true, Class$forName has nothing to do with the way I registered things. It has to do with the fact that I did not call DeferredRegister$register in the ID class. I could have also made the DeferredRegister fields private in the ID class. Anyway, thank you for answering all of my questions and giving me all of your help.

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.



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • rp.crazyheal.xyz mods  
    • I'm developing a dimension, but it's kinda resource intensive so some times during player teleporting it lags behind making the player phase down into the void, so im trying to implement some kind of pregeneration to force the game loading a small set of chunks in the are the player will teleport to. Some of the things i've tried like using ServerLevel and ServerChunkCache methods like getChunk() dont actually trigger chunk generation if the chunk isn't already on persistent storage (already generated) or placing tickets, but that doesn't work either. Ideally i should be able to check when the task has ended too. I've peeked around some pregen engines, but they're too complex for my current understanding of the system of which I have just a basic understanding (how ServerLevel ,ServerChunkCache  and ChunkMap work) of. Any tips or other classes I should be looking into to understand how to do this correctly?
    • https://mclo.gs/4UC49Ao
    • Way back in the Forge 1.17 days, work started for adding JPMS (Java Platform Module Support) to ModLauncher and ForgeModLoader. This has been used internally by Forge and some libraries for a while now, but mods (those with mods.toml specifically) have not been able to take advantage of it. As of Forge 1.21.1 and 1.21.3, this is now possible!   What is JPMS and what does it mean for modders? JPMS is the Java Platform Module System, introduced in Java 9. It allows you to define modules, which are collections of packages and resources that can be exported or hidden from other modules. This allows for much more fine-tuned control over visibility, cleaner syntax for service declarations and support for sealed types across packages. For example, you might have a mod with a module called `com.example.mod` that exports `com.example.mod.api` and `com.example.mod.impl` to other mods, but hides `com.example.mod.internal` from them. This would allow you to have a clean API for other mods to use, while keeping your internal implementation details hidden from IDE hints, helping prevent accidental usage of internals that might break without prior notice. This is particularly useful if you'd like to use public records with module-private constructors or partially module-private record components, as you can create a sealed interface that only your record implements, having the interface be exported and the record hidden. It's also nice for declaring and using services, as you'll get compile-time errors from the Java compiler for typos and the like, rather than deferring to runtime errors. In more advanced cases, you can also have public methods that are only accessible to specific other modules -- handy if you want internal interactions between multiple of your own mods.   How do I bypass it? We understand there may be drama in implementing a system that prevents mods from accessing each other's internals when necessary (like when a mod is abandoned or you need to fix a compat issue) -- after all, we are already modding a game that doesn't have explicit support for Java mods yet. We have already thought of this and are offering APIs from day one to selectively bypass module restrictions. Let me be clear: Forge mods are not required to use JPMS. If you don't want to use it, you don't have to. The default behaviour is to have fully open, fully exported automatic modules. In Java, you can use the `Add-Opens` and `Add-Exports` manifest attributes to selectively bypass module restrictions of other mods at launch time, and we've added explicit support for these when loading your Forge mods. At compile-time, you can use existing solutions such as the extra-java-module-info Gradle plugin to deal with non-modular dependencies and add extra opens and exports to other modules. Here's an example on how to make the internal package `com.example.examplemod.internal` open to your mod in your build.gradle: tasks.named('jar', Jar) { manifest { attributes([ 'Add-Opens' : 'com.example.examplemod/com.example.examplemod.internal' 'Specification-Title' : mod_id, 'Specification-Vendor' : mod_authors // (...) ]) } } With the above in your mod's jar manifest, you can now reflectively access the classes inside that internal package. Multiple entries are separated with a space, as per Java's official spec. You can also use Add-Exports to directly call without reflection, however you'd need to use the Gradle plugin mentioned earlier to be able to compile. The syntax for Add-Exports is the same as Add-Opens, and instructions for the compile-time step with the Gradle plugin are detailed later in this post. Remember to prefer the opens and exports keywords inside module-info.java for sources you control. The Add-Opens/Add-Exports attributes are only intended for forcing open other mods.   What else is new with module support? Previously, the runtime module name was always forced to the first mod ID in your `mods.toml` file and all packages were forced fully open and exported. Module names are now distinguished from mod IDs, meaning the module name in your module-info.java can be different from the mod ID in your `mods.toml`. This allows you to have a more descriptive module name that doesn't have to be the same as your mod ID, however we strongly recommend including your mod ID as part of your module name to aid troubleshooting. The `Automatic-Module-Name` manifest attribute is now also honoured, allowing you to specify a module name for your mod without needing to create a `module-info.java` file. This is particularly useful for mods that don't care about JPMS features but want to have a more descriptive module name and easier integration with other mods that do use JPMS.   How do I use it? The first step is to create a `module-info.java` file in your mod's source directory. This file should be in the same package as your main mod class, and should look something like this: open module com.example.examplemod { requires net.minecraftforge.eventbus; requires net.minecraftforge.fmlcore; requires net.minecraftforge.forge; requires net.minecraftforge.javafmlmod; requires net.minecraftforge.mergetool.api; requires org.slf4j; requires logging; } For now, we're leaving the whole module open to reflection, which is a good starting point. When we know we want to close something off, we can remove the open modifier from the module and open or export individual packages instead. Remember that you need to be open to Forge (module name net.minecraftforge.forge), otherwise it can't call your mod's constructor. Next is fixing modules in Gradle. While Forge and Java support modules properly, Gradle does not put automatic modules on the module path by default, meaning that the logging module (from com.mojang:logging) is not found. To fix this, add the Gradle plugin and add a compile-time module definition for that Mojang library: plugins { // (...) id 'org.gradlex.extra-java-module-info' version "1.9" } // (...) extraJavaModuleInfo { failOnMissingModuleInfo = false automaticModule("com.mojang:logging", "logging") } The automatic module override specified in your build.gradle should match the runtime one to avoid errors. You can do the same for any library or mod dependency that is missing either a module-info or explicit Automatic-Module-Name, however be aware that you may need to update your mod once said library adds one. That's all you need to get started with module support in your mods. You can learn more about modules and how to use them at dev.java.
    • Faire la mise à jour grâce à ce lien m'a aider personnellement, merci à @Paint_Ninja. https://www.amd.com/en/support 
  • Topics

×
×
  • Create New...

Important Information

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