Why do blueprints behave differently in editor preview than in standalone preview?
I've been working on a simple sidescroller game. In this game I made a blueprint with a block mesh. This block then generates another one which generates another one and so on and so on, thus making an infinite level. The blocks only generate another block if the player is close enough to that block, to not have infinite blocks getting created.
Anyways, these blocks work perfectly in editor preview, but as soon as I do standalone preview the blueprint stops working properly. It currently doesn't spawn any blocks at all, including the one I manually placed on there to start the chain reaction. I've played around with the blueprint and eventually made it actually spawn in editor preview, but again it didn't behave properly.
So why do blueprints behave differently in editor preview and standalone preview? Are they supposed to or is this just a bug and I'll have to wait for a fix?
asked Mar 31 '14 at 11:55 PM in Blueprint Scripting
Well i don't fully understand your problem but what comes to my head is following... could it be that you don't copy the trigger so that if you run along, the trigger for the i+1 block is not next to the i+1 block but next to the first one?
answered Apr 01 '14 at 08:28 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here