fix(ci): keep bilingual forge-announce embeds from merging
Both the DE and EN embed carried the same release url, which makes Discord merge url-identical embeds and render only the first embed's description. The EN block was posted and stored but never shown, so every auto-announce from v1.4.6 onward displayed German only. Drop the url from the EN embed so Discord stacks both as separate cards with both descriptions visible.
This commit is contained in:
@@ -147,10 +147,14 @@ jobs:
|
||||
}
|
||||
Write-Host "Embed-Caps OK: de=$($deDesc.Length)/4096, en=$($enDesc.Length)/4096, total=$totalChars/6000"
|
||||
|
||||
# ---------- Embed-Payload bauen (zwei Embeds, gleiche url) ----------
|
||||
# Sharing the same `url` tells Discord to render both embeds as a
|
||||
# single contiguous card block. The title sits on the first embed,
|
||||
# the footer + timestamp on the last so it reads as one post.
|
||||
# ---------- Embed-Payload bauen (zwei gestapelte Embeds) ----------
|
||||
# Discord MERGES embeds in one message that share the same `url`
|
||||
# (the image-gallery merge) and then renders only the FIRST embed's
|
||||
# description — every following embed contributes images only. So
|
||||
# only the DE embed carries the release URL; the EN embed stays
|
||||
# url-less, which makes Discord stack both as separate cards with
|
||||
# both descriptions visible. Title sits on the first embed, footer
|
||||
# + timestamp on the last so it still reads as one post.
|
||||
$payload = [ordered]@{
|
||||
username = "Forge Herald"
|
||||
avatar_url = "https://gitea.hellion-forge.cloud/JonKazama-Hellion/HellionChat/raw/branch/main/HellionChat/images/icon.png"
|
||||
@@ -167,7 +171,8 @@ jobs:
|
||||
description = $deDesc
|
||||
},
|
||||
[ordered]@{
|
||||
url = $releaseUrl
|
||||
# Deliberately no `url` — a shared url would make Discord
|
||||
# merge this embed into the first and drop the EN body.
|
||||
color = 12730636
|
||||
description = $enDesc
|
||||
footer = [ordered]@{ text = $footerText }
|
||||
|
||||
Reference in New Issue
Block a user