mojira.dev

Rikard Herlitz

Assigned

No issues.

Reported

No issues.

Comments

I felt that it was overkill for the small sign edit feature (in comparison to books), so wasn'tΒ planned. Would be great if it could be a separate feature request.

You are not supposed to be able to add the Β§ symbol and styling yet at all, so that's the bug. It will be prevented in the upcoming snapshot until we implement proper component-based styling.

You are not supposed to be able to add the Β§ symbol and styling yet at all, so that's the bug. It will be prevented in the upcoming snapshot until we implement proper component-based styling.

Yes, please create a separate ticket for signs.

Have not managed to repro yet. No matter how much/far I sprint-fly the system always manages to GC down to <400Mb

Ok guys, wish me luck for the next release that this fix works πŸ˜›

No problem at all! I'll dig through various redstone things (including your suggestions). Not sure which parts or how much we dare fit into this release though (just a heads up on that).

Really wish I could repro :/

Found a repro!

Thank you! I've fixed those as well now πŸ™‚

Thanks. We will look into it!

The lag from redstone or water related blocks is a bit separate from chunks with complex geometry (eg. fences). We might want to split those out into a separate bug.

@unknown Thanks. I've fixed these too and they should work in the next update!

The issue I fixed was related to music in game (eg. if you exited the game and went back in, the paused music+sounds would be resumed and overlap other music and be unstoppable). The overlapping music in title screen could be a separate bug. Any good repros? Can it happen directly on starting the game? (before even opening a map)

This is fixed for all text fields, but not scroll bars (pre2)

(let me know if i missed any)

This should be a ton more performant now (pre2)

eg. the lag when updating complex chunks with lots of fences or similar

Do you have a failing world you could share?

can be achieved through @e and type, limit and sort attributes. sort=[nearest|furthest|random|arbitrary]

/say @r[type=!player] can be done with /say @e[type=!player,limit=1,sort=random]

nice, always wanted to be mysterious. yes, i'm working on it πŸ˜›