Official Everybody Edits Forums

Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?

You are not logged in.

Advertisement

Hello, visitor! These forums are run off of the revenue generated from these ads. If you'd like to support us, please whitelist us or consider donating:

#1 2018-08-08 19:49:34

TaskManager
Formerly maxi123
From: i really should update this
Joined: 2015-03-01
Posts: 7,348

lava immunity bug

hello its that time of the year again

some people are aware of this bug but it's been around for a long while and im assuing devs dont know about it
theres this bug or glitch of sorts that you can pull off if you have edit and lava blocks
TL;DR: if you float in a block of lava (without burning and without heal effect, do it by godmodding into it) that has another block of lava beneath and if you erase both of them quickly, your lava burning effect breaks and you no longer die from lava

how to reproduce bug:
1) build a structure, similar to these two, two blocks of lava, either floating in air or on a solid ground (i didnt test other environments but these two cases work)
4jHp4Y0.png

2) use godmode, float on top of the upper lava block, and then disable godmode. you have to use W key to float inside the block, in order to avoid setting yourself on fire (this is another bug by the way)
wN2M0In.png Usl32Es.png

3) while youre floating inside the lava block, erase both of the blocks very quickly, starting with the upper one. you have to erase them quick enough that once the upper block is gone, the lower one has to be removed BEFORE you fall into it i further investigated this, and turns out, if you erase it too quickly it wont work, from what i observed the smiley has to touch lower block with its edge or something?? idk, just trying doing this at various erasing speeds
79kM33N.png

4) if you did that properly, you will fall down with your smiley burning indefinitely, as if it had the lava effect but without the lava timer itself. after this you can swim in lava freely without dying. however touching water removes the "immunity". (the "disable heal" effect doesn't remove this immunity)
OcHBc0Z.png
nPQfHmF.png


i8SwC8p.png
signature by HG, profile picture by bluecloud, thank!!
previous signature by drstereos

Online

#2 2018-08-08 20:24:54

LukeM
Dev Team
From: England
Joined: 2016-06-03
Posts: 2,757
Website

Re: lava immunity bug

I think the thing causing this is the same thing that we fixed for the other effects a couple of updates ago, the implementation of the effect is sort of split half and half between the server and the client, meaning that sometimes desyncs happen causing problems like this.

If I understand it correctly, this is because of the order in which things happen:
1. Client tells server that it wants to remove the block
2. Client hits the block, enables the effect, and tells the server that it is on fire
3. Server receives block removal message, and removes the block
4. Server receives effect message, but theres an air block there so the player couldn't have caught fire
This means that the client thinks its on fire, but the server doesn't, so the client never tells the server to set it on fire again, and the server never tells the client to die.

The reason we haven't fixed these problems with the timed effects is that we think that it will probably break a lot of existing worlds, as it will change the durations slightly due to the delay between hitting the block and the server receiving the message, meaning that precise timings may be broken.

Last edited by LukeM (2018-08-08 20:25:24)

Offline

Wooted by: (2)

#3 2018-08-08 20:27:27

TaskManager
Formerly maxi123
From: i really should update this
Joined: 2015-03-01
Posts: 7,348

Re: lava immunity bug

LukeM wrote:

I think the thing causing this is the same thing that we fixed for the other effects a couple of updates ago, the implementation of the effect is sort of split half and half between the server and the client, meaning that sometimes desyncs happen causing problems like this.

If I understand it correctly, this is because of the order in which things happen:
1. Client tells server that it wants to remove the block
2. Client hits the block, enables the effect, and tells the server that it is on fire
3. Server receives block removal message, and removes the block
4. Server receives effect message, but theres an air block there so the player couldn't have caught fire
This means that the client thinks its on fire, but the server doesn't, so the client never tells the server to set it on fire again, and the server never tells the client to die.

The reason we haven't fixed these problems with the timed effects is that we think that it will probably break a lot of existing worlds, as it will change the durations slightly due to the delay between hitting the block and the server receiving the message, meaning that precise timings may be broken.

good implementation as always //forums.everybodyedits.com/img/smilies/big_smile //forums.everybodyedits.com/img/smilies/big_smile


i8SwC8p.png
signature by HG, profile picture by bluecloud, thank!!
previous signature by drstereos

Online

#4 2018-08-08 20:34:47

LukeM
Dev Team
From: England
Joined: 2016-06-03
Posts: 2,757
Website

Re: lava immunity bug

TaskManager wrote:
LukeM wrote:

good implementation as always //forums.everybodyedits.com/img/smilies/big_smile //forums.everybodyedits.com/img/smilies/big_smile

Thats one of the main reasons I'm looking forward to the rEEboot, it allows us to redesign all these things with the knowledge of what worked well / what should have been done differently //forums.everybodyedits.com/img/smilies/big_smile

Last edited by LukeM (2018-08-08 20:35:06)

Offline

Wooted by: (2)

#5 2018-08-09 00:22:28

azurepudding
Member
Joined: 2016-11-18
Posts: 706

Re: lava immunity bug

This is a cool bug yo

DON'T fix please

Offline

Wooted by: (2)

#6 2018-08-09 05:18:07

N1KF
Wiki Mod
Joined: 2015-02-15
Posts: 9,995

Re: lava immunity bug

azurepudding wrote:

This is a cool bug yo

DON'T fix please

More like a WARM bug. //forums.everybodyedits.com/img/smilies/cool


Thank you so much for all the great, fun, and artistic worlds.

Guidelines for a database archive

LukeM's EELVL deserialiser

Offline

Wooted by: (5)

#7 2018-08-09 10:45:55

peace
Member
From: admin land
Joined: 2015-08-10
Posts: 4,867

Re: lava immunity bug

LukeM wrote:

I think the thing causing this is the same thing that we fixed for the other effects a couple of updates ago, the implementation of the effect is sort of split half and half between the server and the client, meaning that sometimes desyncs happen causing problems like this.

If I understand it correctly, this is because of the order in which things happen:
1. Client tells server that it wants to remove the block
2. Client hits the block, enables the effect, and tells the server that it is on fire
3. Server receives block removal message, and removes the block
4. Server receives effect message, but theres an air block there so the player couldn't have caught fire
This means that the client thinks its on fire, but the server doesn't, so the client never tells the server to set it on fire again, and the server never tells the client to die.

The reason we haven't fixed these problems with the timed effects is that we think that it will probably break a lot of existing worlds, as it will change the durations slightly due to the delay between hitting the block and the server receiving the message, meaning that precise timings may be broken.

then hitting lava again doesnt give a timer since client still thinks ur on fire so doesnt set you on fire again this is sort of bug youre tellign here to fix in reeboot like sever needs to know what he ha sdone a couple of seconds before like her in case the seve rehas to know oh wait i removed a lava nlock before maby the player hitted it before i got the removal message lets set him on fire


cZXKA3f.pngMYaIIs9.png
a.pngty anatoly and nikko99 for a golden sig and blueclued for avatar and daneeko for pixelating my sign //forums.everybodyedits.com/img/smilies/cool3bluekeys.png

Offline

#8 2018-08-09 11:04:51

rgl32
Member
Joined: 2015-02-15
Posts: 542

Re: lava immunity bug

peace wrote:
LukeM wrote:

I think the thing causing this is the same thing that we fixed for the other effects a couple of updates ago, the implementation of the effect is sort of split half and half between the server and the client, meaning that sometimes desyncs happen causing problems like this.

If I understand it correctly, this is because of the order in which things happen:
1. Client tells server that it wants to remove the block
2. Client hits the block, enables the effect, and tells the server that it is on fire
3. Server receives block removal message, and removes the block
4. Server receives effect message, but theres an air block there so the player couldn't have caught fire
This means that the client thinks its on fire, but the server doesn't, so the client never tells the server to set it on fire again, and the server never tells the client to die.

The reason we haven't fixed these problems with the timed effects is that we think that it will probably break a lot of existing worlds, as it will change the durations slightly due to the delay between hitting the block and the server receiving the message, meaning that precise timings may be broken.

then hitting lava again doesnt give a timer since client still thinks ur on fire so doesnt set you on fire again this is sort of bug youre tellign here to fix in reeboot like sever needs to know what he ha sdone a couple of seconds before like her in case the seve rehas to know oh wait i removed a lava nlock before maby the player hitted it before i got the removal message lets set him on fire

I have absolutely no idea what you just said but Im pretty sure he knows whats wrong since he literally wrote out the steps when each event is fired.

Offline

Wooted by:
rgl321533809091718741

Board footer

Powered by FluxBB

[ Started around 1558684553.3903 - Generated in 0.045 seconds, 10 queries executed - Memory usage: 1.4 MiB (Peak: 1.56 MiB) ]