<playerloc> and @TP issue #100


  • New
  • Defect
Open
Assigned to _ForgeUser8773666
  • Forge_User_47264883 created this issue Oct 17, 2013

    These are actually two issues, that might have the same origin.
    When using @TP in a script, I want to check before tping that the player is in the correct world, by using /world 0 for instance and tp him into world.
    However, @TP will then tp you back into the world you were before.

    When triggering a script, <playerloc> will keep the same value throughout the same script run instance.

    These issues might be connected, as VT doesn't seem to update the players position while the script runs, tping him back into the nether, as the Plugin thinks he is still in there.

    Script that wont work for instance:
        - '@PLAYER Please stand still for three seconds'
        - '@SETSTR $temp.tploc_<playername> <playerloc>'
        - '@LOOP 30'
        - '@PAUSE 0.1'
        - '@IF s $temp.tploc_<playername> != <playerloc>'
        - '@PLAYER &cYou moved, teleportation aborted'
        - '@SETBOOL $temp.tplocb_<playername> true'
        - '@BREAKLOOP'
        - '@ENDIF'
        - '@ENDLOOP'
        - '@IF b $temp.tplocb_<playername> = false'
        - '@TP 0,100,0'
        - '@ENDIF'

  • Forge_User_47264883 added the tags New Defect Oct 17, 2013
  • Forge_User_47264883 edited description Oct 17, 2013
  • _ForgeUser9029595 posted a comment Dec 2, 2013

    Create another script ONLY with @TP command and use

    -'@CMDOP vt run yourscript:scriptwithonlytp <playername>'

    Replace 'yourscript' and 'scriptwithonlytp' ! Now VT use correct world ! It works ! I use this technique in many scripts in my own /home /tp /warp commands !

  • _ForgeUser603316 posted a comment Dec 16, 2013

    I can confirm this issue. This issue is actually about the world not being updated after a teleport. Strangely enough the @TP function also teleports to a world.


    Edited Dec 17, 2013

To post a comment, please login or register a new account.