Jump to content

Recommended Posts

Posted

So, I've been adding natural spawning code for a bunch of mobs in my mod, and it has been working for the most part. The exception, however is in my mobs that should spawn in water. So I tried adding this line of code to make a water mob spawn:

EntityRegistry.addSpawn(EntityGiantSquid.class, 100, 1, 1, EnumCreatureType.WATER_CREATURE, BiomeDictionary.getBiomes(Type.OCEAN).toArray(new Biome[0]));

I will note that this entity is not an extension of EntityWaterMob, but I have given it all the functionality of one, and I don't think that should matter because Guardians aren't extensions of it either. So I did a bit of research and I found a past thread on here with this exact same issue, but that thread never got a definite resolution.  If someone could figure out what is going on here then that would be appreciated.

 

<Alternative solution>

So instead of using the above method to spawn my water mobs, there is another way that I'm trying, but it has a few issues as well. If anyone knows a way to fix this method then that would work just as well.

Instead of spawning the mob using the normal spawning mechanics, I have tried to use the EventHandler with the LivingSpawnEvent to replace an occasional squid with my new mob like so:

@SubscribeEvent
	public static void onLivingSpawn(LivingSpawnEvent event) {
		EntityLivingBase entity = event.getEntityLiving();
		if(entity instanceof EntitySquid) {
			if(entity.world.getBiome(new BlockPos(entity)) == Biomes.OCEAN && entity.world.getDifficulty() != EnumDifficulty.PEACEFUL && !entity.world.isRemote) {
				if(entity.getRNG().nextInt(100) == 1) {
					EntityGiantSquid squid = new EntityGiantSquid(entity.world);
					squid.copyLocationAndAnglesFrom(entity);
					entity.world.spawnEntity(squid);
					System.out.println("Spawning giant squid");
					entity.setDead();
				} 
			}
		}
	}

So this method kinda works, but there is also some unpredictable behavior. Every time a giant squid replaces a regular one, there is a message printed to the console. Well when I move around in the ocean, I see waaay more giant squids than debug messages. There was one instance where I saw more giant squids than regular ones, but there should be only one giant squid per 100 squid spawned on average. Think I might be using this event improperly or just using the wrong one.

Posted

You're using the spawn event improperly. Many events are "parent" events that actually fire multiple times for more specific subevents. In this case, the actual events are AllowDespawn, CheckSpawn, and CheckSpecialSpawn.  So for example, the AllowDespawn is being regularly fired for all squids as they age in the world.

 

I think you should use the CheckSpawn or perhaps the EntityJoinWorld events.

  • Like 1

Check out my tutorials here: http://jabelarminecraft.blogspot.com/

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

    • When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • It is 1.12.2 - I have no idea if there is a 1.12 pack
  • Topics

×
×
  • Create New...

Important Information

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