-
-
Notifications
You must be signed in to change notification settings - Fork 871
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
Remove invalid sign check #3328
Conversation
Many of these checks are designed to prevent the bot from getting flagged/kicked by the server. Have you checked how this is handled my vanilla? |
Of course, it does handle normally. Actually, I didn't see any restrictions on the line length of the sign and its not stated in the protocol docs either. In the vanilla, the sign editor calculates the width of each character to get the maximum length of the line. For example one |
did you check this for minecraft 1.8 ? |
@rom1504 Of course! It does work without any issues. The maximum length you can get is 45 characters on the line |
GitHub Action says: 1 failing
1) mineflayer_external 1.20.4v
sign:
Uncaught TypeError: Cannot read properties of undefined (reading 'trimEnd')
at Timeout._onTimeout (test/externalTests/sign.js:23:42)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7) The 400k lines log is crazy, but i don't think its current PR breaks the pipeline |
If the max is 45 characters then why not adapt the check instead of removing it ? |
Okay, not a problem. As said in #3328 (comment) In the original client, if you type only |
Is this good to go? |
@extremeheat could you look into this as well? Don't see anything that blocks the pr |
... or add a way to skip this check, because for some characters like
|
this is simply not correct (e.g. you can have 45 bars on the line):|||||||||||||||||||||||||||||||||||||||||||||