Skip to content

fixed discord bugs pet frame/name bug#67

Closed
JPEscher wants to merge 1 commit into
DanderBot:mainfrom
JPEscher:fixPetNameSecretStringBug
Closed

fixed discord bugs pet frame/name bug#67
JPEscher wants to merge 1 commit into
DanderBot:mainfrom
JPEscher:fixPetNameSecretStringBug

Conversation

@JPEscher

@JPEscher JPEscher commented May 10, 2026

Copy link
Copy Markdown
Contributor
  • fixed bug on pet frame name

reported:

fix demo

credit

  • please credit me for this fix
  • this was too damn easy and i don't deserve credit
  • i dont want credit, dont know the code enough to be confused with a dev of the code

@JPEscher JPEscher changed the title fixet discord bugs pet frame/name bug fixed discord bugs pet frame/name bug May 10, 2026
@JPEscher

Copy link
Copy Markdown
Contributor Author

closing as there is a better pr (#72 )

@JPEscher JPEscher closed this May 11, 2026
DanderBot pushed a commit that referenced this pull request May 11, 2026
GetUnitName can return a secret string value in delves and encounters.
The previous code called #name and name:sub() on the result, which throws
a Lua error the moment any string operation is attempted on a secret value.

Routes truncation through DF:UTF8Len / DF:UTF8Sub, which both guard on
issecretvalue internally and return safe defaults (0 / "") when the input
is secret. The truncation branch no-ops, SetText still receives the secret
string, and FontStrings render it correctly without taint.

Supersedes PR #67 which skipped SetText entirely on secret values, leaving
the pet name text stale rather than updating it.
@JPEscher JPEscher deleted the fixPetNameSecretStringBug branch May 15, 2026 18:52
Krathe82 added a commit to Krathe82/DandersFrames that referenced this pull request Jun 6, 2026
GetUnitName can return a secret string value in delves and encounters.
The previous code called #name and name:sub() on the result, which throws
a Lua error the moment any string operation is attempted on a secret value.

Routes truncation through DF:UTF8Len / DF:UTF8Sub, which both guard on
issecretvalue internally and return safe defaults (0 / "") when the input
is secret. The truncation branch no-ops, SetText still receives the secret
string, and FontStrings render it correctly without taint.

Supersedes PR DanderBot#67 which skipped SetText entirely on secret values, leaving
the pet name text stale rather than updating it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant