Floating Trees
caley posted in Bugs 9 years ago (edited 9 years ago)
first one I've found , using Chrome with Windows7 . Here
There's also a piggie wandering the trench on the far left, but I suspect former Glitchen has been playing with them ;
caley replied 9 years ago
okay it's not just the trees anymore
Some one or maybe a few folks have been out and about in Ur moving stuff around.
Floating shrines, beans, vendors.... ( Chego Chase)
I wish the imps would let the builders build.
R
caley replied 9 years ago
okay it's not just the trees anymore
Some one or maybe a few folks have been out and about in Ur moving stuff around.
Floating shrines, beans, vendors.... ( Chego Chase)
I wish the imps would let the builders build.
R
Klikini replied 9 years ago (edited 9 years ago)
Floating shrines confirmed...
Elysian Slope (LLI33CQJ3UD1G5J)
Cebarkul LIF12PMQ5121D68
Torpan Cleft LCR241CP4Q129I1 (I had to toggle physics to reach this one)
It seems strange to me that both shrines appear in the top left corner (you can see the energy/mood meter in both screenshots).
Klikini replied 9 years ago (edited 9 years ago)
Floating shrines confirmed...
Elysian Slope (LLI33CQJ3UD1G5J)
Cebarkul LIF12PMQ5121D68
Torpan Cleft LCR241CP4Q129I1 (I had to toggle physics to reach this one)
It seems strange to me that both shrines appear in the top left corner (you can see the energy/mood meter in both screenshots).
Carasek replied 9 years ago
I've noticed the floating shrines bug and done a bit of experimenting. I found if you leave the street with the floating shrine, then go straight back there again, the floating shrine doesn't re-appear. So it seems to be refresh-specific - not sure if that makes it easier or harder to fix, but that has been the case everytime I've tried it. (Using Firefox v32.0 on Windows 8.1)
Carasek replied 9 years ago
I've noticed the floating shrines bug and done a bit of experimenting. I found if you leave the street with the floating shrine, then go straight back there again, the floating shrine doesn't re-appear. So it seems to be refresh-specific - not sure if that makes it easier or harder to fix, but that has been the case everytime I've tried it. (Using Firefox v32.0 on Windows 8.1)