JeCel reports: When Milky Medieval Glass is p ... #1768
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1768
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?
JeCel reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
this is a longstanding issue w/ unified dye, having to do w/ how
paramtype2 = "color"
is handled w.r.t. the unified dye palette. basically, uncolored (white) nodes don't haveparam2 = 0
, because white is not at position 0 on unified dye's palettes. when the "default" node, which isn't storing the param2 value in metadata, is placed and broken, the dug-up node will have the "param2=240" value, and won't stack.unfortunately vanessae's repo has been totally deleted, so there's no way to reference the issue that as it was presented there.
i think the proposed solution was to not store the metadata value for the default (white, 240) value?
before we do any work on this, are we currently using the most recent commit from https://github.com/mt-mods/unifieddyes?
Answer: yes, it looks like we are. I'll bug the mt-mods people about this at some point.
It's not a bug in unifieddye.
Need to replace
with
etc. gotta AFK in a minute so just making a note of this for now.
upstream PR https://github.com/adrido/darkage/pull/14
upstream got pulled, 3 weeks ago actually.
and it's actually live. nice!