Reply to Re: Problem with block not being removed
If you don't have an account, just leave the password field blank.
December 3rd 2012, 10:34 AM
shevek
The only local variable problem I encountered was &ghost, which was recently discussed. The problem is slightly more complicated: The first ghost encounter doesn't set the global variable to 1, because it defines it as a local. This is easily fixed by removing "int", thus going back to the old behavior.
The second problem is that the child's name doesn't appear on the church door if you have seen the slimes. I was unable to run through the slime field in two seconds (to avoid the slimes to spawn). My workaround was to set the timeout to 3 seconds.
For this problem (it happens twice), my workaround was to make the blocks nohard to start with. That means I could just run away without killing anyone, but I just didn't do that.
My question was if this hardness blocking problem happens with Dink 1.08 as well. I take your answer as "yes".
The second problem is that the child's name doesn't appear on the church door if you have seen the slimes. I was unable to run through the slime field in two seconds (to avoid the slimes to spawn). My workaround was to set the timeout to 3 seconds.
For this problem (it happens twice), my workaround was to make the blocks nohard to start with. That means I could just run away without killing anyone, but I just didn't do that.
My question was if this hardness blocking problem happens with Dink 1.08 as well. I take your answer as "yes".
