AliasAlreadyTaken reports: We need to conceal the rogue g ... #99
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#99
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?
AliasAlreadyTaken reports a bug:
Player position:
Player look:
Log identifier
Profiler save:
Status:
The problem is that far (map)blocks are loaded when near ones are not; there's no way to solve this without somehow making
ignore
nodes opaque, which would require a client update i thinkMaking ignore nodes opaque would look odd in a lot of other circumstances :D
Maybe we should start forceloading the terrain? But unless we also force fed the mapblocks to every client that visits Haven: No chance.
Forceloading wouldn't help because you've still got no control over the order in which mapblocks get sent to the client, and packets can be dropped.
this could theoretically be fixed via an engine update that allowed masking mapblocks from the client, but we aren't going to do that, and we have more open issues than we can deal w/. closing.