new setLore funciton in style of setCustomName

[flerbuster]

it feels wrong calling setLore like this

setLore(listOf(literalText(...) { ... }...

[jakobkmar]

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.

[r0yzer]

ich hab rr kein plan was du damit meinst

[flerbuster]

ich rr auch nicht

[flerbuster]

hatte genug

[jakobkmar]

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.

[flerbuster]

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

[jakobkmar]

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.

[flerbuster]

sibling

tmm

[flerbuster]

i will see what i can do but i think i am not smart genug