MC-89242Length of writing text on sign limited by Resource Pack
Clone of MC-88858 that was incorrectly closed.
This issue is NOT a duplicate of MC-87605 as that issue relates to sign rendering (and is working as intended), and this issue is about sign creation.
---------------
Sign rendering has been limited in 1.8 based on the resource pack itself how it renders the text.That is fine and all, but it also impacts simply setting up the sign.
For example, a user with a custom resource pack using larger fonts can't write as many characters on a sign line than another resource pack can.
Truncating the message on sign viewing is accepted, but the client should not be as strict on sign creation, as a sign created on one resource pack may over flow but be perfectly visible on another.
Even more so, users using the vanilla resource pack are reporting being unable to write their character name on a sign due to this.
name: Merek_Shadowmere
Suggestion: Client should allow writing up to 32 characters, and then let viewing the sign enforce the rendering based calculations.
Then activities that read the sign data can at least see full name, even if client can not.
Linked Issues
Created Issue:
Length of writing text on sign limited by Resource Pack
Clone of
MC-88858that was incorrectly closed.
This issue is NOT a duplicate ofMC-87605as that issue relates to sign rendering (and is working as intended), and this issue is about sign creation.
---------------
Sign rendering has been limited in 1.8 based on the resource pack itself how it renders the text.That is fine and all, but it also impacts simply setting up the sign.For example, a user with a custom resource pack using larger fonts can't write as many characters on a sign line than another resource pack can.
Truncating the message on sign viewing is accepted, but the client should not be as strict on sign creation, as a sign created on one resource pack may over flow but be perfectly visible on another.
Even more so, users using the vanilla resource pack are reporting being unable to write their character name on a sign due to this.
name: Merek_ShadowmereSuggestion: Client should allow writing up to 32 characters, and then let viewing the sign enforce the rendering based calculations.
Then activities that read the sign data can at least see full name, even if client can not.
relates to
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
[Mojang] Grum (Erik Broes)A comment with security level 'global-moderators' was removed.
A comment with security level 'global-moderators' was removed.
is duplicated by
Maybe intended? https://twitter.com/seargedp/status/477926066661908480
[Mod] Neko as mentioned in the ticket, that comment from [Mojang] Searge (Michael Stoyke) is about sign RENDERING, which is what my original ticket was closed as duplicate of.
Fully understand that rendering limited by resource pack is "Working as designed". But its also affecting sign creation in a way that even a vanilla client with vanilla resource pack can't write a player's name on the sign when it should be able to.
Client should let you write the name, and then clients that have a resource pack that can fit all 16 characters can see it, and those that can't, can't.
The limit being enforced both directions makes it difficult to create signs.
Forcing a user to use a custom resource pack just to create a sign is silly.
[Mojang] Grum (Erik Broes) Can this please not be closed? I get that its probably not something you want to spend time on, but it's still a problem regardless.
Can we leave it open incase Searge or someone else feels like fixing it?
This is working as intended. Allowing the client to write high amount of characters is not going to make the sign screen feel any better.
[Mojang] Grum (Erik Broes) Not asking for a high amount, but a mere 32 for example would be a sane limit
As said, there are cases where players with 15-16 character names can not write their name on the sign due to character width.
I really believe its beneficial to let them write the name and let the client truncate as it does for any sign created pre 1.8 with names that no longer can be typed.
For servers that read data off the signs, its game breaking when some players can not have their name written on the sign without resorting to third party resource packs.
All I'm asking is to remove the need to use 3rd party resource packs to achieve a sane result of a mere 16 characters on a sign.
Then theres also the benefit of servers that translate & into color codes, a 32 limit would let you write colored text on the sign that RENDERS within the signs limits, but has more characters than could be typed.
for ex &aW&bW&cWW&eW&dW&4W
would not be possible to type on sign as it is today, but when translated into color codes, it will fit on the signs rendering.
This is an issue even within the normal game: switching to the Unicode font allows adding more text.
In multiplayer this is a really annoying issue, since people who have the unicode font enabled can make signs that contains more text than is shown for players using the default font.