You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
command /test:
trigger:
set {_i} to diamond
set line 1 of {_i}'s lore to "Test"
broadcast "-%line 1 of {_i}'s lore%"
Running the above script will produce a result of -Test when running Skript 2.4-beta10 only.
However, when running the above script with skript-holo 1.0.2, it instead produces a result of -<none>, leading me to believe that this is caused by some conflict of expression with Skript's line expression.
Versions (All are latest, except for the Spigot jar)
Skript: 2.4-beta10
skript-holo: 1.0.2
Holographic Displays: 2.4.0
ProtocolLib 4.4.0
Server: git-Spigot-9de398a-9c887d4 (MC: 1.14.4)
The text was updated successfully, but these errors were encountered:
Wealthyturtle
changed the title
skript-holo conflicting with Skript's lore expression
skript-holo conflicting with Skript's line expression
Nov 17, 2019
[the] line %number% of [holo[gram][s]] %holograms%
The parser should be reading it like (line 1 of hologram {_i})'s lore
can not be reading like line 1 of hologram ({_i}'s lore).
In this case the line expression returns a HologramLine, and it has a converter to ItemType, this should be why. Skript's ExprLore is being an issue in this case because it is weird as known, if it was something like line 1 of %strings% this wouldn't happen; parser can read it like line 1 of ({_i}'s lore).
set line 1 of lore of {_i} to "Test" should work.
I woudn't want to break existing scripts but i'm not sure :{
Script
Running the above script will produce a result of
-Test
when running Skript 2.4-beta10 only.However, when running the above script with skript-holo 1.0.2, it instead produces a result of
-<none>
, leading me to believe that this is caused by some conflict of expression with Skript's line expression.Versions (All are latest, except for the Spigot jar)
The text was updated successfully, but these errors were encountered: