Jump to content

[1.7.10] Event handler to prevent falling out of the world.


Code Wrecker

Recommended Posts

So I wrote a snip of code to catch players falling out of the neither and overworld, and place them back someplace safe. Now I haven't had a lot of falling out of world problems since 1.6.4. But it was on my list of things to solve when I got around to modding.

 

For starters, I realize there MUST be better ways of doing this. This is functional, and after trying to get the world in some global variable, and thinking of calling several player "safe spawn" functions, I went with this hack.

 

My concern is... This is called for every LivingUpdateEvent (yuck).

It has to hook the correct variables (I'd prefer to use some constants.)

I call some random dimension checks. (Getting the correct player dim based on bed, seems to be some NBT Forge hack.)

 

 

So other than the things I hate about it, it's functional, and gets rid of a long standing pet peeve of mine... Falling out of a world for no good reason.

 

What changes/functions would streamline this?

 

 

	@SubscribeEvent
public void checkUpdate(LivingUpdateEvent event) {
	if (event.entityLiving instanceof EntityPlayer && event.entity.posY < -60.0D) {
		if(!(event.entityLiving.dimension == 0 || event.entityLiving.dimension == -1)){
			return;
		}
		OverWorld = DimensionManager.getWorld(0);
		spawn = OverWorld.getSpawnPoint();
		EntityPlayerMP playerMP = (EntityPlayerMP) event.entity;
		if (((EntityPlayer) event.entityLiving).getBedLocation(0) != null) {
			spawn = ((EntityPlayer) event.entityLiving).getBedLocation(0);
		}
		System.out.println("Saving the day!");
		event.entityLiving.fallDistance = 0;
		if (event.entity.worldObj != OverWorld) {
			playerMP.mcServer.getConfigurationManager().transferPlayerToDimension(playerMP, 0);
		}
		event.entityLiving.setPositionAndUpdate(spawn.posX, spawn.posY + .1, spawn.posZ);

 

Link to comment
Share on other sites

1st of all - if you are dealing with players, you don't use LivingUpdateEvent (unless you need mid-tick). PlayerTickEvent FTW!

 

Two ways:

 

1. Use PlayerTickEvent.

* Pick tick phase (event.phase == Phase.START)

* Do everything else like you did.

 

// Note: This alredy cuts your tick-checks by about few thousand since you are only checking Players.

 

2. Use LivingHurtEvent

* Check if event.source is type of DamageSource.outOfWorld which can only happen precisely when you fall out.

* Cancel damage (event) and do everything else like you did.

 

// Note: This cuts whole ticking part, yet LivingHurtEvent will check hurting of any EntityLivingBase.

 

Numbers:

Say you got 100 players and 2000 entities.

In:

1. You do 2000 position checks per second.

2. I can't imagine having more than 2000 LivingHurtEvents fired per second, unless someone deals damage per tick.

 

Verdict:

"Premature optimization is the root of all evil!"

 

Any of those if better than LivingUpdateEvent.

Anyway - you obviously have NO idea how much MC does in one tick. Your code is NOTHING compared to rest.

It doesn't matter how much code you'd execute in that event, this:

player.posY < -60.0D

...alredy cuts out literally everything.

1.7.10 is no longer supported by forge, you are on your own.

Link to comment
Share on other sites

I agree with Ernio. Checking things every tick is sometimes necessary if a condition can occur in any tick and you need to handle it immediately. The game already does a bazillion things per tick so a few position checks isn't going to be noticeable. As Ernio mentioned though it is unnecessary to check every living tick but instead use player tick.

 

If you're really worried about it, profile the time it takes to execute. I'm sure you'll find it is trivial.

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

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

    • Hello, Hi and I am making a forge 1.12.2 mod and also trying to get a custom model helmet item (I made a joker mask) and exported it to .json format and put it in the ~/namespace/models/item folder. Though, I'm struggling to get the item to render what I want it to be rendered like as I've positioned it in the 'head' window view in blockbench. How did you render out your model? I checked your code and it looks like no references to the actual model are being made. I'm new to this forge modding stuff (was a fabric modder) and I desperately need some help. Is there a way to standardly render out armor models made using blockbench? any methods that one can use? My model in JSON: ```json { "credit": "Made with Blockbench", "texture_size": [160, 160], "textures": { "0": "ydyrn:items/joker_mask_texture", "particle": "ydyrn:items/joker_mask_texture" }, "elements": [ { "from": [0, 0, 0], "to": [16, 16, 1], "faces": { "north": {"uv": [0, 1.7, 16, 14.2], "texture": "#0"}, "east": {"uv": [0, 4, 0.9, 5.6], "texture": "#0"}, "south": {"uv": [0, 5.8, 1.6, 7.4], "texture": "#0"}, "west": {"uv": [0, 1.9, 1.3, 3.5], "texture": "#0"}, "up": {"uv": [0, 3.4, 1.6, 4.2], "texture": "#0"}, "down": {"uv": [0, 9, 1.6, 9.7], "texture": "#0"} } }, { "from": [15.8, 11, 0.5], "to": [16.2, 13, 15], "faces": { "north": {"uv": [7.9, 7.9, 7.94, 8.1], "texture": "#0"}, "east": {"uv": [7.9, 7.9, 9.35, 8.1], "texture": "#0"}, "south": {"uv": [7.9, 7.9, 7.94, 8.1], "texture": "#0"}, "west": {"uv": [7.9, 7.9, 9.35, 8.1], "texture": "#0"}, "up": {"uv": [7.9, 7.9, 7.94, 9.35], "texture": "#0"}, "down": {"uv": [7.9, 7.9, 7.94, 9.35], "texture": "#0"} } }, { "from": [0.2, 11, 14.6], "to": [15.8, 13, 15], "faces": { "north": {"uv": [7.9, 7.9, 9.46, 8.1], "texture": "#0"}, "east": {"uv": [7.9, 7.9, 7.94, 8.1], "texture": "#0"}, "south": {"uv": [7.9, 7.9, 9.46, 8.1], "texture": "#0"}, "west": {"uv": [7.9, 7.9, 7.94, 8.1], "texture": "#0"}, "up": {"uv": [7.9, 7.9, 9.46, 7.94], "texture": "#0"}, "down": {"uv": [7.9, 7.9, 9.46, 7.94], "texture": "#0"} } }, { "from": [-0.2, 11, 0.5], "to": [0.2, 13, 15], "faces": { "north": {"uv": [7.9, 7.9, 7.94, 8.1], "texture": "#0"}, "east": {"uv": [7.9, 7.9, 9.35, 8.1], "texture": "#0"}, "south": {"uv": [7.9, 7.9, 7.94, 8.1], "texture": "#0"}, "west": {"uv": [7.9, 7.9, 9.35, 8.1], "texture": "#0"}, "up": {"uv": [7.9, 7.9, 7.94, 9.35], "texture": "#0"}, "down": {"uv": [7.9, 7.9, 7.94, 9.35], "texture": "#0"} } } ], "display": { "thirdperson_righthand": { "translation": [-0.25, -2.75, 0], "scale": [0.3, 0.3, 0.3] }, "thirdperson_lefthand": { "translation": [-0.25, -2.75, 0], "scale": [0.3, 0.3, 0.3] }, "firstperson_righthand": { "rotation": [-9, 115, 15], "translation": [0, 1.25, -1.75], "scale": [0.5, 0.5, 0.5] }, "firstperson_lefthand": { "rotation": [-9, 115, 15], "translation": [0, 1.25, -1.75], "scale": [0.5, 0.5, 0.5] }, "ground": { "rotation": [40, 0, 0], "translation": [0, -2.5, 0], "scale": [0.5, 0.5, 0.5] }, "gui": { "rotation": [0, 180, 0] }, "head": { "translation": [0, 0, 0.25], "scale": [0.82773, 0.73594, 0.9] }, "fixed": { "translation": [0, 0, 8.75] } }, "groups": [ 0, { "name": "straps", "origin": [0, 0, 0], "color": 0, "children": [1, 2, 3] } ] } ```
    • Add the crash-report or latest.log (logs-folder) with sites like https://paste.ee/ and paste the link to it here  
    • In your config folder, delete the sophisticatedcore-common.toml file and test it again
    • Add the crash-report or latest.log (logs-folder) with sites like https://paste.ee/ and paste the link to it here  
  • Topics

×
×
  • Create New...

Important Information

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