Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Former/Past world in a teleport event (TimeStates) #3641

Closed
Lemrigue opened this issue Dec 16, 2020 · 1 comment
Closed

Former/Past world in a teleport event (TimeStates) #3641

Lemrigue opened this issue Dec 16, 2020 · 1 comment
Labels
completed The issue has been fully resolved and the change will be in the next Skript update. enhancement Feature request, an issue about something that could be improved, or a PR improving something. priority: lowest "Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements).

Comments

@Lemrigue
Copy link

Description

I tried using "former world" in a teleport event, but return "world" value instead

Steps to Reproduce

Create a file.sk with
on teleport: send "%former world% / %world%"

Expected Behavior

former world should return the world the player was in before the teleportation, but return the world he is in after the teleportation (https://skriptlang.github.io/Skript/expressions.html#ExprTimeState)

Errors / Screenshots

No errors (but if the event is "on world change" instead : "the world does not have a past state")

Server Information

  • Server version/platform: paper-319
  • Skript version: 2.5.3

Additional Context

I think it worked when I used skQuery, but since it's a Skript feature I reported it

@ShaneBeee
Copy link
Contributor

Marking this as an enhancement since its technically not a bug, its just not written anywhere in Skript to hold states for locations/worlds in TP events.

@ShaneBeee ShaneBeee added enhancement Feature request, an issue about something that could be improved, or a PR improving something. priority: lowest "Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements). labels Dec 25, 2020
@ShaneBeee ShaneBeee added the completed The issue has been fully resolved and the change will be in the next Skript update. label Jan 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
completed The issue has been fully resolved and the change will be in the next Skript update. enhancement Feature request, an issue about something that could be improved, or a PR improving something. priority: lowest "Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements).
Projects
None yet
Development

No branches or pull requests

2 participants