[MCPE-16013] Signs - Text Length Inconsistency Across Platforms Created: 01/Jul/16  Updated: 02/May/17  Resolved: 02/May/17

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.15.1, 0.15.2, 0.16.1, 0.16.2, 1.0.0, 1.0.2
Fix Version/s: 1.1.0.9

Type: Bug
Reporter: [Mojang] Mega_Spud (Jay Wells)
Resolution: Fixed Votes: 1
Labels: sign

Attachments: PNG File android.png     JPEG File win10.jpg    
Issue Links:
Duplicate
is duplicated by MCPE-19837 Sign text line length is limited diff... Resolved
Relates
relates to MCPE-13631 SIGNS- Can't type a full line of text... Resolved
relates to MCPE-16620 Some characters can cause overflow fr... Resolved
Confirmation Status: Confirmed
Platform: Windows
CHK:
ADO: 24785

 Description   

A somewhat trivial bug, but a bug nonetheless. In the Windows 10 edition, fewer characters can be typed into a sign than the Android edition.

I was expecting to be able to type the same amount of characters on a sign across all platforms of the same game version.

Steps to Reproduce

  1. Place a sign in Win 10 edition and type 1 as many times as possible on the first line (max 14)
  2. Repeat the above on an Android device and notice that a maximum of 15 1's can be typed on one line

Tested on Windows 10 PC, Samsung TabPro Android 4.4.2 and Nexus 5 Android 6.0.1

Update by Mega_Spud:

As pointed out by od1g1man, it also seems that in Windows 10, the number of characters is limted to the width of the sign, whereas on Android, it's dependant on the number of characters, which is 15.



 Comments   
Comment by [Mojang] Mega_Spud (Jay Wells) [ 02/May/17 ]

Fixed in 1.1 due to new sign formatting.

Comment by [MCPE Helper] Dylan K. Taylor [ 24/Jan/17 ]

For me it's the reverse, as detailed in https://bugs.mojang.com/browse/MCPE-19837. I can type as many chars as I like on W10 up to the width of the sign, but on PE I'm stuck with 15 chars per line.

Comment by [Mojang] Adrian Östergård [ 24/Aug/16 ]

Reported for test and fix.

Generated at Sat Jan 11 15:09:54 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.