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

Manipulating Display Entities via Effect Command Bug #7187

Open
1 task done
aaaeeeMC opened this issue Nov 3, 2024 · 3 comments
Open
1 task done

Manipulating Display Entities via Effect Command Bug #7187

aaaeeeMC opened this issue Nov 3, 2024 · 3 comments
Labels
2.10 Targeting a 2.10.X version release bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. PR available Issues which have a yet-to-be merged PR resolving it priority: medium Issues that are detrimental to user experience (prohibitive bugs or lack of useful implementation).

Comments

@aaaeeeMC
Copy link

aaaeeeMC commented Nov 3, 2024

Skript/Server Version

[10:11:33 INFO]: [Skript] Skript's aliases can be found here: https://github.com/SkriptLang/skript-aliases
[10:11:33 INFO]: [Skript] Skript's documentation can be found here: https://docs.skriptlang.org/
[10:11:33 INFO]: [Skript] Skript's tutorials can be found here: https://docs.skriptlang.org/tutorials
[10:11:33 INFO]: [Skript] Server Version: 1.21-109-5a5035b (MC: 1.21)
[10:11:33 INFO]: [Skript] Skript Version: 2.10.0-beta1 (skriptlang-github)
[10:11:33 INFO]: [Skript] Installed Skript Addons:
[10:11:33 INFO]: [Skript]  - SkBee v3.5.8 (https://github.com/ShaneBeee/SkBee)
[10:11:33 INFO]: [Skript] Installed dependencies: None

Bug Description

I was trying to see how quaternions work, by spawning in a block display, but it didn't work when I tried to change something. Look in the Errors or Screenshots section.

Expected Behavior

It was obviously supposed to change the specific property to what I put, but it didn't work and instead threw an unspecified error.

Steps to Reproduce

  1. Run !spawn a block display at me ("of (block data)" doesn't work by the way)
  2. Make sure the block display is the nearest block display to you for the next steps.
  3. Run !set transformation translation of nearest block display to vector(-0.5,-0.5,-0.5)
  4. You get an unspecified error.
  5. Furthermore, try !set left transformation rotation of nearest block display to vector(1,0,0,0)
  6. Now say "He was right. Time to fix it, I guess." 😭

Errors or Screenshots

Screenshot 2024-11-03 101000

Other

No response

Agreement

  • I have read the guidelines above and affirm I am following them with this report.
@Romitou
Copy link
Member

Romitou commented Nov 3, 2024

Can replicate, the example provided in the PR #5601 doesn't seem to work when parsing display syntaxes.
However, a workaround is to define a local display variable before using it.

@Efnilite Efnilite added bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. priority: medium Issues that are detrimental to user experience (prohibitive bugs or lack of useful implementation). labels Nov 3, 2024
@TheBentoBox
Copy link
Member

Can confirm (for the dev team - this is the bug I discussed with you in dev chat).

This happens with any expression which resolves to an entity. For example, when using a spawn section to spawn a display, referencing the spawned entity using the entity expression does not work for display syntaxes.

@sovdeeth
Copy link
Member

sovdeeth commented Nov 3, 2024

sounds like maybe we need an entity -> display converter

@erenkarakal erenkarakal added the 2.10 Targeting a 2.10.X version release label Nov 8, 2024
@sovdeeth sovdeeth added the PR available Issues which have a yet-to-be merged PR resolving it label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.10 Targeting a 2.10.X version release bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. PR available Issues which have a yet-to-be merged PR resolving it priority: medium Issues that are detrimental to user experience (prohibitive bugs or lack of useful implementation).
Projects
None yet
Development

No branches or pull requests

6 participants