JeCel reports: We have white street signs tha ... #2406
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
source/testserver
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#2406
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
JeCel reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
I want to see if I can attempt this.
Do we have the sign_api from the display modpack on the server?
Yes, we're using this https://gitea.your-land.de/mt-mirror/basic_signs and that https://github.com/mt-mods/signs_lib
And we're using this fork of Display modpack: https://github.com/pyrollo/display_modpack
mt-mirror isn't visible to the public (i can't even see it).
these links might be more useful:
Uh I can't view those links either..
Well I've gotten a two wide banner working, but it centers itself like this which does look rather strange. I'm still experimenting so there might be a way to prevent this (that's unlikely because afaik this is also a problem with the large banner; but I'll still try!).
I'm wondering though, is this good enough to be merged in?
It's a bit of a hack but it seems to be working pretty well!
Should I open a pull request on yl_common or should this be merged into another repo?
yl_commons should be fine for now, unless alias has other ideas.
Nope, yl_commons is fine :)
fixed in your-land/yl_commons#18
live, thank you @Kodin :)