Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

emoji on sign cause chunk status to be corrupted #177

Closed
MrEDok opened this issue Jan 2, 2022 · 2 comments
Closed

emoji on sign cause chunk status to be corrupted #177

MrEDok opened this issue Jan 2, 2022 · 2 comments
Labels

Comments

@MrEDok
Copy link

MrEDok commented Jan 2, 2022

Describe the bug
When usign a sign with in this case "FIRE" emoji 🔥 it cause chunk status to be corrupted

Full copied text from the MS-DOS view

############################################################
################# Scan results for: world ##################
############################################################


Unreadable player files:
No problems found.

Unreadable data files:
No problems found.

Chunk problems:
------------------------------
| Problem | Corrupted  Total |
------------------------------
|  Count  |     1      3280  |
------------------------------

Expected behavior
not mark as corrupted

Screenshots
image

Files that would help solving the issue
If possible, the world/files that triggers the error.

Desktop (please complete the following information):

  • OS: Windows/linux
  • Region Fixer Version tested on o.3.4 and o.3.5

Additional context
Add any other context about the problem here.

@MrEDok MrEDok added the Bug label Jan 2, 2022
@Fenixin
Copy link
Owner

Fenixin commented Jan 3, 2022

Hello!

Thank you very much for you report, this could be really useful because it sounds like a UTF-8 issue, and can provide some more help to solve #148. I have to sit sometime and fix this.

Could you provide a regionfile with this issue?

@Fenixin Fenixin mentioned this issue Aug 1, 2022
@Fenixin
Copy link
Owner

Fenixin commented Aug 1, 2022

Hello!

Thanks for your issue. This has been fixed in the last release.

Closing the issue, don't hesitate to open a new issue if you find anything else.

@Fenixin Fenixin closed this as completed Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants