Open flerbuster opened 4 months ago
This seems counter intuitive, since this would add multiple lines even without calling newLine()
.
For example, simpling changing the color would result in a new line (if you do not wrap every line in a dummy text component).
This function should search for \n
instead.
ich hab rr kein plan was du damit meinst
ich rr auch nicht
hatte genug
One sibling != one line.
A component is broken down into more parts than just lines, styling, color and interactivity changes also result in more siblings.
One sibling != one line.
A component is broken down into more parts than just lines, styling, color and interactivity changes also result in more siblings.
can you not just do a sibling in the sibling of the sibling and achieve the same thing
can you not just do a sibling in the sibling of the sibling and achieve the same thing
That would be very very unintuitive. It should be newLine()
-> a line break will be inserted.
sibling
tmm
i will see what i can do but i think i am not smart genug
it feels wrong calling setLore like this
setLore(listOf(literalText(...) { ... }...