whosit reports: normal digistuff:touchscreen s ... #6510
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6510
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
whosit reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
#4876Edit: Oh, sorry. missed up the touchscreen names...
Yeah, but it's a normal one, not "adv"... Maybe they are aliased or something...
intentional because #5923, probably close as a dupe. once the client fixes get shipped (5.9?) we can re-enable that touchscreen.
Seems like overkill... If someone made a crashy touch screen, it would only affect people who actually click on it. To reset it, you only need to break it and fix the code in luac that generated it. If it's done with malicious intent, we would know who exactly programmed it... Only people with mesemaker could do it... And as far as we know, this has never came up while screens were in use...
On the other hand, I guess we're not a machine server and screens are niche use, so, meh...
that's trolly enough to trap neophytes. and as you point out, we're not a machine server - if some machines are disabled until an the fixed version of the client gets released, i won't lose any sleep. it'll get re-enabled eventually.
Well, even when new client is out, significant number of people will still use older versions. So, if the goal is to never let anyone crash because of this, then release of 5.9.0 is not when this should be re-enabled...
when the new client is released, we can at least point people at how to fix the issue. sure, it's possible to build your own client while cherry-picking the relevant commit. but most people will not be able to do that, either because they can't understand how to do that, or because the fix just isn't otherwise available on their platform. until then, it's unfortunately on us to prevent the problem. when there's an official release to the majority of our audience, then we can re-enable this without fear of alienating too many people.
Regarding backwards compat, the YL approach is "Clients back to 5.0.0 should not crash immediately. If they can't access each and every game content as well as an up to date client, that's ok."
We are not responsible for people who build their own client and remove exactly the bugfixes, but that's a such small group.
In this case I'd say we can reenable this with the release of 5.9.0 - if THEN anyone chooses to crash their client repeatedly on the touchscreen, so be it. The user must access the touchscreen for the bug to happen, it's not that there is a mapblock he cannot access anymore, if there is such a faulty touchscreen in there.