MC-88858Length of writing text on sign limited by Resource Pack
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
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 mayt 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.
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
tover 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.
duplicates
duplicates
duplicates
This isn't intended. Needs to be fixed!
Someone deleted my comment without reason, even though I pointed out that it was not intended.
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.
Thank you for your report.
However, your ticket has been resolved as a duplicate.
This issue has been linked to the original bugreport:
MC-87605. You can find or add further information on that report.Please search before reporting any bugs, as it's likely that one exists already.
Mustek that is related but not duplicate.
That issue is about sign rendering, and is for the current intent "working as intended". This ticket is asking about sign creation, not sign rendering.
Kumasasa can you reopen this per my last comment? This isn't the same thing as the ticket it's marked duplicate as.
You are right, it wasn't linked to the correct ticket, done so now. See
MC-89242, which funnily enough, was made by you.I forgot I opened that since this one was wrongly closed as duplicate.