game-editor.com

Hi!

I've been adding "floors" to my game's dungeons, but haven't been able to find a simplistic way of moving my player from staircase to staircase. What I do now is make two separate filled regions that, on collision, take my player off to the other one. And I have a new pair for every single staircase called things like D1S1 (Dungeon 1, Stairs 1) is paired with D1S2 (Dungeon 1, Stairs 2), etc. Not only does this make my list of actors huge, but it also gets real confusing real fast.

So my question is: Is there an easier way to move an actor between two locations with perhaps clones so as to not use a lot of actors? I suppose in a manner similar to lcl's Doors Tutorial (which I have tried to edit to work on collision, but was unsuccessful)?

Thanks in advance!

check global code -> doors
should be self explanatory
if you dont understand feel free to ask

Hey, thanks for the response!

I tried it out, but for some reason the first time I collide with the door actor (I have it set up as a filled region, instead of a regular actor, not sure if that makes a difference) it sends my actor off into nowhere, which I can correct by moving my player some thousands of pixels around the next one of the pairs. After that first warp however, the function works fine. I'm curious as to why this is.

Thanks!

Hello DrakeStoel!

DrakeStoel wrote:I tried it out, but for some reason the first time I collide with the door actor (I have it set up as a filled region, instead of a regular actor, not sure if that makes a difference) it sends my actor off into nowhere, which I can correct by moving my player some thousands of pixels around the next one of the pairs. After that first warp however, the function works fine. I'm curious as to why this is.

It's pretty difficult to say what's causing the problem without seeing how you've actually implemented schnellboot's code.

Sure, sure!

I've actually figured it out now. I did just copy and paste the code from the demo into my game, but the problem was that the codes were battling with some of my other codes and it just messed up the destination... For some reason. Not sure why, but I worked it out and now it works great! Thanks so much guys!

Good to hear it's working and good point that the other interconnected/dependent codes can affect the results when any big change is made.