I ran into this weird bug when I was working on a project. For whatever reason, CRAY powered by Pscn now erases such that everything in the path of the beam gets erased. Normally this is the correct behaviour, but when I used the parameters to change the area of effect, the beam still continued; albeit with a slower speed, as it would advance the beam by the specified limiting value every time it fired.
I'm not sure if this is the correct behaviour or not, but if it is I'm not sure what the workaround would be.
@LBPHacker (View Post)
Actually I have experienced this also, but I don't remember at all what the fix was and I don't know how exactly to reproduce it. It may have been that I just messed up something with tmp and tmp2.This is what I remember:
cray[brck] tmp 5 was creating 5 px of brck when sparked once, and then on the 2nd spark was deleting the whole row of brck (not just 5). I can try to replicate it, but this issue only happened once to me on the previous version of the game on mac.
@temporaryaccount (View Post)
If i am correct, you must have accidentally set the CRAY ctype to sprk while clicking on it.
You first set the .tmp to 5 while the ctype was set to BRCK so it produced 5 pixels of it, as expected.
Then you set it's ctype to sprk (unknowingly), which explains why it started to delete everything in front of it because Cray with sprk as ctype does just that.
@Cracker1000 (View Post)
Yes that's exactly what it was, now I remember.