Albrun

I have four [Enki's Cadence Rollercoaster Derby of 1120] horseshoe trophies (99ql, rare, straw, un-impable) that get decay damage despite of that they supposedly shouldn't. At the event it was stated that they had decoration protection set and would not decay ondeed, only take damage if used equipped on an animal. ("<Enki> Keep in mind the partidipation awards will nto decay, but they WILL take damage if used,., they are for decoration!") I got my four trophies on Enki's Cadence Rollercoaster Derby on 2023-08-31. I keep them in a small chest (runed with RSiV against contents decay; rare, skinned, locked), in a house, on an upkeeped deed; I have never used them equipped. They have 2-4 damage as of posting today. At first I thought it was just that one didn't get the deco protection toggled on by oversight, but by now 4 out of 4 are taking decay, plus several other people have reported theirs also decaying. I was asked to report it as a possible bug of the deco protection failing.

I am not learned in runes, but to me the spirit gate writing looks like: First pic (read mirrored right to left): ᛞᛖᚨᛏᚺ ᚨWᚨᛁᛋ -- "death awaits" Second pic writing on the arch (read mirrored right to left; if the arch is supposed to form a n-shape in the end, the text would then be upside down): ᚺᛖᛚᛖ ᛞᛖᚨᛏᚺ ᚨWᚨᛁᛋ -- "here death awaits" Uses mostly older futhark, with a younger S. Where I wrote W in the rune text it uses what looks like an upside down ᛗ=M rune apparently. The "here" reads as "hele" with a ᛚ=L, but I assume that was a typo.

The bugged saddles always have phantom (undyed regular) saddlebags visible, whether there is nothing in them, or saddlesacks, or (undyed) saddlebags. The bug can be partly overridden by having dyed saddlebags in, in which case it shows the correct dye-color saddlebags. Saddlesacks cannot be dyed, so I could not test what a colored saddlesacks might result in (visible saddlesacks? phantom saddlebags but in correct color?). As stated before, the bugged saddles can be fixed by GMs, but that is only temporary. I had all my bugged saddles fixed by GM, but afterwards all my saddles have re-buggged themselves. I do not know what causes the bug, so I have no idea how to avoid it happening again, so I haven't tried to get them fixed again since. As I used dyed bags with my main saddles, the bug wasn't visible usually. Now I got some saddlesacks for Chrismas, but using them is meh because it then shows the brown undyed phantom saddlebags again. Does anyone know what causes the bug to trigger in the first place?

Just using this map (https://assets.wurmonline.com/test-servers/oracle/terrain-starter.png), I'd say it's the spot near the WNW coast, east of the big desert rectangle, north of the horizontal highway. ETA: Okay weird situation, all the previous "found!" answers didn't show when I posted. So please excuse the unnecessary post, no disrespect was meant.

Guard tower in https://cadence.yaga.host/#1721,2251. Plaque "Albrun 362", name "M15 Annabel Lee". And passing on request by Yve: guard tower in https://cadence.yaga.host/#1892,2684. Plaque "Yve 298", name "Kladruby Guards O16". Dunno if there is a map policy which names get added, plaque or label or both? So I provided both. There is a tower symbol in the yaga map legend, but I couldn't find any towers on the maps to compare. (Also lol, I planned to make this post before the exploration testing brought up the tower clues.)

4.2. Getting disembarked on a server crossing from A to B, but on the front end of the switch. The ship travels to the plotted-course server B on its own, while the players get dropped overboard into the sea on server A. Happens solo or with passengers, and in the latter case with everyone or just part of the crew. I have had (myself and witnessed on others) a handful of cases in the last months. In the cases where I was solo or the whole crew dropped, I was lucky to get help from other players who fished me out and brought me cross-server to find my ship. (Yes, the first time I called support, but then found a helping hand before support had time for me and cancelled the ticket. The other times I managed to source help before having to bother support.) I've also witnessed it happen to others, and fished them out to return them to their ship on the other side of the server border (all the while hoping the bug didn't hit us again and leave two crews adrift ). Getting catapulted off your cart or mount by(nearby?) a fence, seemingly over the fence. Then you have to figure out a) which side of the fence the game thinks you are on, so you can reach your cart again, and b) how to get out of the fence if needed. Also similar problem by sliding down a slope on foot and getting thrown over a fence at the bottom. X) Oh yeah, so much of that, especially early as a newbie before I figured out the cause to avoid it, or how to fix it. Not fixing the root issue, but an easy in-the-moment fix is to walk into an open cave tile.

I apologize for being unclear, but the old kinked section of the highway (https://cadence.yaga.host/#2372,2872 to https://cadence.yaga.host/#2417,2872) has been disconnected and removed. Connected at this crossing https://cadence.yaga.host/#2416,2867 there are now *only* the highway coming perfectly straight all the way west from Port Crescendo, and the diagonal highway coming up southeast from Encore. Due to someone deeding over it while the highway was in the process of being built in the early days of Cadence this eastern section of the straight west-east road had to be shifted south by a couple of tiles (https://cadence.yaga.host/#2385,2873); the shifted section has now been removed, as the originally planned straight road has been built and connected now (https://cadence.yaga.host/#2393,2866). I am sorry for causing confusion and extra work. ETA: Thank you so much for fixing it, and for your patience with me! Lol, edited here same time as you posted below, MiniKilljoy.

The Port Crescendo east highway has been fixed, it is now a whole straight line from west to east (P16-P19) until it meets the diagonal highway coming up southeast from Encore. I.e. the kink was removed and highway is now back between https://cadence.yaga.host/#2372,2867 and https://cadence.yaga.host/#2417,2867 (where the map dump still partly shows the original road pavement). Thank you! Also, in case the omission on the map wasn't on purpose: in Port Crescendo P16 itself the highway is connected/intact between https://cadence.yaga.host/#1894,2866 and https://cadence.yaga.host/#1894,2838, not disconnected as currently shown.

When dyed, the examine text on both plain and kingdom flags and banners (probably tall kingdom banner too but I don't have an example to check) says "wood colors" even though the dyed part is the cloth and not the wood. So it probably should either neutrally say "Colors:" or specific "Cloth colors:".

Food items "plain crisps" and "corn crisps" (possibly other crisps too?), and "unfinished small tortoise shield" are missing a model and appear as question mark bags. Also if relevant, not exactly incorrect but improvable model: "Poppies golden spaghetti" uses the standard 'meal' picture but could use the noodle bowl model instead, "dessert pizza" made with chocolate and berries uses the cheesy pizza model but maybe could use the berry tart model.

Well if you are arguing it's dom-rec inheritance my points stand. How does that relate to the three color values labeled. How is white recessive here (unless it's referring to a second white-making gene w in a three-allele system G/w/b). And if it used a two-allele system with recessive black two blacks shouldn't be able to make a white kid. The latter would be a bug then so it's still a bug discussion. Which makes me inclined to believe Archaed, that there is no mendelian genetic inheritance involved here, just like there isn't for other animals. Anyway, sorry for the topic. All this time I got told to report various things here and now that I went and did it turns out like this. X)

So it's not actually an issue and it was wrong for me to be sent here with it? That's embarrassing, sorry for the trouble. For the explanations, that seems confusing, I'm not sure I get it. So sheep have three color values ('labels') available, and the 'grey' one does not have a texture of its own, so you phenotypically get two white one black instead; and that's on purpose. That so far seems agreed on. (Guess then the wiki should say that there's no actual grey phenotype.) But the color value being an actual dominant-recessive inheritance as Seriphina's reply implies or chancepicked like Archaed's does seem mutually exclusive. Also in Seriphina's dom-rec case, I was then first assuming a white-dominant two-allele inheritance (WW / Ww / ww), with the three color values representing the genotypes. But then you said 'white' and 'black' sheep were both recessive, which would need three alleles resulting in more genotypes than the three color values could document, making the color labels rather pointless as indicators. And going by the reported inheritance in your last line, you mean to say the black allele is stronger than the white one, so G>b>w? Tbh the whole dom-rec inheritance here to me seems untypical of wurm, even less with a three-allele inheritance of stepped dominance where the top and bottom one make the same phenotype; seems unnecessarily complicated, but maybe it's wogic. I've been brooding on this way too long already so I'm posting now, forgive my lack of understanding. ETA: On re-re-reading again after posting I got another idea (typical). I may have been monumentally stupid. Do you not actually mean "recessive" when you said it but are misusing that as synonym for "less common trait"? In that case my entire paragraph trying to decode the dom-rec inheritance system from your post can go into the bin.

tl;dr: some white-looking sheep are labeled as color:grey in the inspect-animal window. So far ingame I have encountered 'white' and 'black' sheep, labeled as such and having a matching texture. By chance I noticed a white-looking sheep labeled as color:grey in the inspect-animal window. After a cursory search I found at least a dozen sheep in my village that are labeled as 'grey' in the inspect window, but appear with the regular white-sheep texture. I confirmed with other players, and they too saw the sheep as looking white and labeled 'grey'. The greys were among bred sheep, wild sheep, and even a mission-spawned sheep. Current help chat had not heard of the issue and GM Vayu referred me here. Presumably, either the label in the inspect window is broken and should read 'white', or the greys are legit but missing a texture. Or is the color:grey supposed to be a hint for recessive genes, but that seems weird and seemingly used nowhere else in that manner.

I first met Chaosmeow in January 2021 when she and her group from Defiance Hill joined my home village Port Crescendo. It was only a year since then, but Chaos was a great person to hang out and play with and very easy to like. I miss her, but am glad I got to meet her. Ereyesterday we built her memorial pylon on Resting Chaos (thank you Deyjan) and it turned out very beautiful; I think she would have liked it too.