alexandre2005 reports: When u look thro salt crystals ... #1921
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1921
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?
alexandre2005 reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Idk if that helps, but some screenies
I have no idea what causes this, but
It affects coloured glass too
AH well rip
Well, it did create an interesting art
depending on the way u look, "it moves" :DDD
I just created a label
result/beyond our control
, but I'd prefer to at least link to an upstream issue before closing this, and there's too many related upstream issues to figure out if any of them are relevant.Beyond our control sounds a bit like
result/not our bug
and has overlap with upstream and lag.If everyone is ok with such an obvious flaw, it shows IMO the amount of suffering MT folks are willing to take. Maybe this is something we should research with core devs and see their opinion - they will never fix it or at least consider, if we let them get away with "irrlicht problem, we can't do anything".
oh i missed that, i'll get rid of the one i created.
Actually, it looks like this has been fixed in recent dev clients. One of these is from a vanilla 5.5.0 client, the other is a recent dev build:
You didn't miss that one, I didn't create it yet. It's only that I have seen the holy trinity of not-our-bug/not-a-bug/cannot-reproduce in more than one label sets ;)
Let's discuss in your-land/administration#146
Regarding the bug: Cool :) So someone DID say "we're not gonna take it" and fixed it? Let's tell alexandre and close this one, since the bugfix will autoamtically hit the world of MT?
Let's keep this open until the fix is in a stable client release, at least.
maybe not totally fixed in that update:
this is still not fixed, and seems to have something to do with mapblock boundaries. stand at
/teleport xyz 3046 129 320
(frosthall), look east, and walk side to side.