indigo saffron
to simplify things, im doing something like and i want to add a pipe for visual purposes and not actually go the next line/score. i feel like im being dumb and missing something, but ive tried messing with escaping and stuff to avail
- sidebar set title:title values:<[health]>[I WANT MY PIPE HERE]<[max_health]>
prisma ravenBOT
(nimsy) how to put pipe in sidebar?
prisma ravenBOT
to simplify things, im doing something like and i want to add a pipe for visual ...
Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>
peak totem
<&chr[007C]>
indigo saffron
ty
gloomy hazelBOT
indigo saffron
wait
gloomy hazelBOT
bleak juniperBOT
!c sidebar
gloomy hazelBOT
rugged brook
to clarify the issue, you should not have to change that pipe out for an escaped value
but it's being read as listtag input
rugged brook
i guess as a workaround you could use the &chr / <&pipe> and suffer with the warning
until that's fixed that is
indigo saffron
that doesn't work either
indigo saffron
im running on latest dev version btw
rugged brook
@indigo saffron ｜
just use that until we can fix the bug
verified it works in latest dev
gloomy hazelBOT
opal meteor
just use that until we can fix the bug
behr how drunk were you at the time of this thread
opal meteor
to simplify things, im doing something like and i want to add a pipe for visual ...
!tag list_single
bleak juniperBOT
!tag list_single
opal meteor
| is list separator, it's being read as list, you gotta make it not a list
peak totem
`<&chr[007C]>`
^ arent those things made for cases like this?
for example <>> and <<> as well?
opal meteor
no
not applicable
you'd know this if you tested before saying that, which:
!badanswers
bleak juniperBOT
!badanswers
Info: badanswers
peak totem
ive been using it in multiple places, thought it would work there as well so yeh my bad
opal meteor
That does not work anywhere (in regards to the pipe symbol)
if you're using it, you should probably go back to the scripts that do that and correct it
if that tag works somewhere, raw pipe symbol does too
rugged brook
wh
rugged brook
!tag list_single
im confused why this worked when sticking the pipe in an elementtag didn't
opal meteor
im confused why this worked when sticking the pipe in an elementtag didn't
cause that's not a thing
at all
rugged brook
@indigo saffron the values argument takes a listtag;
list_single resolves this issue as mcmonkey mentioned
indigo saffron
im confused
so how would i use it?
because if i used pipes... it'd still count as another entry in the list?
woeful coral
values is a list
list_single returns a single value list
i.e everything within is the one value of the list
and one line of the scoreboard
woeful coral
values:<list_single[hi|ho]>
woeful coral
debug
rugged brook
or if you tried it after being shown this time:
indigo saffron
indigo saffron
values:<list_single[hi|ho]>
gui is fucked when i do this
lemme do an mcve rq
(plus, it makes sense that it wouldn't work like that)
so
just to be clear
test:
type: task
debug: false
script:
- define my_value a|b
- sidebar set title:my_title values:<[my_value]>
returns
(as expected)
test:
type: task
debug: false
script:
- define my_value a|b
- sidebar set title:my_title values:<list_single[<[my_value]>|c|d]>
keep in mind the addition |c|d at the end
it returns
(also as expected)
indigo saffron
values:<list_single[hi|ho]>
which means doing this would be wrong
now for the third case
test:
type: task
debug: false
script:
- define my_value <list_single[a|b]>
- sidebar set title:my_title values:<[my_value]>|c|d
the pipe is unescaped
indigo saffron
doesn't make a difference
hence, it doesn't work
woeful coral
which means doing this would be wrong
Wut
rugged brook
wh
rugged brook
```
test:
type: task
debug: false
script:
- define my_value <list_single...
all of what you wrote makes sense except for this one
that one was just object hacking and... weird output, i agree but
definitely shouldnt be used that way
rugged brook
what do you want
indigo saffron
…
rugged brook
i'll write it for you right now
indigo saffron
Don’t worry my friend, I’ve already written in.
rugged brook
yay
upper gustBOT
+> YAY!!!
indigo saffron
to simplify things, im doing something like and i want to add a pipe for visual ...
It’s my first message in the thread.
rugged brook
- sidebar set title:title values:<list_single[<[health]>|<[max_health]>]>
indigo saffron
…..
rugged brook
did it work
rugged brook
i just cant replicate that it doesn't work
that's via /ex sidebar set title:title values:<list_single[taco party time|jajaja]>
which has the left text, a pipe, and the right text
opal meteor
```
test:
type: task
debug: false
script:
- define my_value <list_single...
.include and/or include_single to add more entries to a list
rugged brook
if you have pipes in the entries, you do want the include_single
just because it's list syntax
indigo saffron
`.include` and/or `include_single` to add more entries to a list
What if I want to include it only in a specific part of a much bigger list?
Would I do .insert and the list_single inside it?
This all seems so inconvenient to me
I think I’ll just make a custom character
rugged brook
!tag insert_single
bleak juniperBOT
!tag insert_single
rugged brook
but lists in these scenarios require very careful handling
