Jump to content

Recommended Posts

Posted

Delete the MoveTo part from the dialogue and instead put it on Stage 40 fragment.

 

Before scripting, click properties, new property, objectreference type, name myMarker.

 

Now put a XMarker in the place you want to teleport.

 

Now return on the property, on the right click "edit value" and select your marker.

 

Finally write this in the fragment:

 

Game.GetPlayer().MoveTo(myMarker)

Posted
Also keep in mind to do anything else you want to do in that fragment before the MoveTo. I don't know about Skyrim, but when you used MoveTo on the player in Oblivion, it acted as a return. (If I remember correctly.)
Posted

Delete the MoveTo part from the dialogue and instead put it on Stage 40 fragment.

 

Before scripting, click properties, new property, objectreference type, name myMarker.

 

Now put a XMarker in the place you want to teleport.

 

Now return on the property, on the right click "edit value" and select your marker.

 

Finally write this in the fragment:

 

Game.GetPlayer().MoveTo(myMarker)

 

Thank you. Scripting is not an easy thing to learn...

Posted

Also keep in mind to do anything else you want to do in that fragment before the MoveTo. I don't know about Skyrim, but when you used MoveTo on the player in Oblivion, it acted as a return. (If I remember correctly.)

 

thanks for the tip.

Posted

Also keep in mind to do anything else you want to do in that fragment before the MoveTo. I don't know about Skyrim, but when you used MoveTo on the player in Oblivion, it acted as a return. (If I remember correctly.)

 

thanks for the tip.

 

Good news. That bug where MoveTo acted as a return in Oblivion does not happen in Skyrim. I guess it's a peculiarity of TES script and luckily doesn't affect Papyrus. I just wrote a couple different scripts for a mod that did multiple things after using MoveTo() on the player, and it worked fine.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...