How to spawn a player at a certain location? not teleporting

[Tinkot]

Is it possible to spawn a player at a certain location with the `on join` event?

i am currently teleporting them but it would be better if i can spawn them instead of teleporting.

         on join:
            teleport player to {hubspawn.%{spawnselector}%}
            if {spawnselector} is 9:
                set {spawnselector} to 1
            else:
                add 1 to {spawnselector}

 

[ShaneBee]

Wouldn't it be the same thing?
Or is the problem that they are spawning somewhere and then moving right away?

 

[Tinkot]

they spawn and then get teleported. its glitchy and feels unnecessarily. teleporting them with the on quit event won't be an option since they need to spawn in a specific location depending on other events.
[doublepost=1525978906,1525978588][/doublepost]well i actually can use on quit but i'm just wondering if its possible. when a player logs in i see this

logged in with entity id 970749 at ([spawn]673.5, 109.0, 894.5)

We can't just change this location somehow?

 

[ShaneBee]

What if you did something like

on join:
    set the spawn point of "world" to the (location here)

 

[Tinkot]

cool idea. But it can't be set to a location for some reason. I dont know what latter means, empty is the world-name

 

[ShaneBee]

so i tried this:

command /setspawn:
    trigger:
        set {spawn} to location of player

on join:
    set the spawn point of "world" to {spawn}

The problem is, the player spawns where they logged out

I then added in "teleport player to spawn" .... which Im starting to think is the only viable option.
I noticed when i logged in, i was at the spawn point. I didn't visually SEE any other place or the actual teleportation event, i was JUST THERE.

 

[Tinkot]

i will figure it out soon. working on another project right now

 

[Lego_freak1999]

i will figure it out soon. working on another project right now

Wenn you start working on it again try using on connect: instead of on join: this event is called Before the player is fully joined

 

[Tinkot]

oh yes i can try that. if this is before the world is send over to the player than it would work perfectly
[doublepost=1526081142,1526080845][/doublepost]Tested it and its not teleporting them at all using on connect. The strange thing is that i can still give them items using this event. I tried it with 1 tick delay and that worked but its still the same. other players can still see the teleportation going on
[doublepost=1526246573][/doublepost]okay i just found out how it works. you need teleport the players using the on quit event. its the only method i can think of. So i made this little manager that teleports the player to a random spot out of 9 spots when they quit. and when my minigames teleport them it will act like normal. Maybe there is another method that deletes all playerdata (entity id and logout location) so the server thinks the players logs in for the first time. that could work but it wil probably mess with some other plugins. however, this works now

on script load:
    set {spawnselector} to 1

on quit:
    teleport player to {hubspawn.%random integer between 1 and 9%}

on join:
    clear player's inventory
    set slot 0 of the player to a clock named "&a&lGameMode Selector"
    set slot 1 of the player to a slimeball named "&c&lSpectate Players"
    execute console command "/ScoreBoard on %player%"
#spawn command. Executed by games (not players)
command /tpspawn [<offlineplayer>]:
    trigger:
        if arg is online:
            clear arg's inventory
            set slot 0 of the arg-1 to a clock named "&a&lGameMode Selector"
            set slot 1 of the arg-1 to a slimeball named "&c&lSpectate Players"
            teleport arg-1 to {hubspawn.%{spawnselector}%}
            execute console command "/ScoreBoard on %arg-1%"
            if {spawnselector} is 9:
                set {spawnselector} to 1
            else:
                add 1 to {spawnselector}