AliasAlreadyTaken reports: Post office performance idea. ... #6641
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#6641
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:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
And why do not build a copy of that post office and when you go downstairs you will be teleported to there and back? So below the guild palace is just nothing?
Because I don't like teleport for game design reasons.
If teleport was an option, we could also have a city in the sky with player plots and similar.
It is not the postoffice per se that is lagging us, it is the signposts. Those need to be dealt with.
that might help, but we'd have to test things. note that this wouldn't do anything to reduce the complexity of what is displayed and sent to clients, though. signs are heavier than most other entities because they're made up of compositions of images of every individual letter, and that would still be the case.
this would also make it harder to implement this idea (not sure if it has its own issue), which i think is more promising.
Or big transparent images, like this one
(sure can be cropped better, this is just demo)
So 1 image per 7x3 area. Or even bigger images - less nodes.
Size of this demo image is less than 6 KB.
(and you can decorate it :))
oh i see, hard-code the rendered image instead of composing it. hm.
but that means we'd only get post-office sign updates once every 3 or 4 months?
Hmm what about NPC ? No need to have signs, just NPC with compasses :D But then problem is how to tell it to NPC... maybe text input? (player name)
Not if we upload a new png via dynamic media in case something changes. Which is pretty rare
Might be a solution for all signposts that rarely change
Problem is to render the stuff into a fitting png
personally i'd rather try to implement my idea where entities disappear if they're more than 8 nodes away from a player.
and this discussion is making me move that up in my mental list of priorities.