openclaw - 💡(How to fix) Fix feat: 세이브별 동적 캐릭터 레퍼런스 이미지 시스템 [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#60729Fetched 2026-04-08 02:47:53
View on GitHub
Comments
1
Participants
1
Timeline
4
Reactions
1
Author
Participants
Timeline (top)
closed ×1commented ×1cross-referenced ×1locked ×1
RAW_BUFFERClick to expand / collapse

문제

  • 현재 이미지 트리거 가이드라인에 images/reference/kim_malsuk/... 하드코딩됨
  • 첫 캐릭터가 말숙이라 말숙 전용으로 되어 있으나, 새 캐릭터/세이브에는 적용 불가
  • 첫 외모 이미지를 생성한 뒤 해당 세이브 내내 레퍼런스로 재사용하는 흐름이 없음

제안 흐름

  1. 새 게임 시작 시 첫 외모 이미지 생성 (SFW)
  2. 생성된 이미지를 images/reference/<slot>/<character_name>/ 하위에 저장
  3. game.character.referenceImagePath 필드에 경로 저장 → game_db 영속화
  4. 이후 해당 세이브의 모든 이미지 생성 시 이 레퍼런스 사용 (나노바나나 image 파라미터)
  5. NSFW 장면(NAI)에서도 characterId 없이 temporaryReference로 해당 로컬 파일 사용

필요 변경

  • engine.js / stat_loop.js: game.character.referenceImagePath 필드 추가, initGame에서 null 초기화
  • game_db.js: referenceImagePath 영속화
  • 가이드라인: 하드코딩 경로 → 동적 경로(game.character.referenceImagePath)로 변경
  • GM 프로세스: 새 게임 시작 시 첫 외모 이미지 생성 단계 추가

참고

  • 말숙 하드코딩은 첫 캐릭터가 말숙이라 임시로 그런 것이며, 장기적으로는 세이브별 동적 관리 필요

extent analysis

TL;DR

Update the image trigger guidelines to use a dynamic path based on the game.character.referenceImagePath field instead of hardcoding the path to images/reference/kim_malsuk/....

Guidance

  • Identify and update all occurrences of the hardcoded path images/reference/kim_malsuk/... in the image trigger guidelines to use the dynamic path game.character.referenceImagePath.
  • Verify that the game.character.referenceImagePath field is properly initialized and persisted in the game_db for each save.
  • Update the engine.js and stat_loop.js files to include the referenceImagePath field and initialize it to null in the initGame function.
  • Modify the GM process to generate the first appearance image at the start of a new game and store its path in the game.character.referenceImagePath field.

Example

// engine.js
game.character.referenceImagePath = null;

// game_db.js
// Add referenceImagePath to the game_db schema

Notes

The current implementation has a hardcoded path for the first character, which limits its applicability to other characters and saves. The proposed changes aim to make the image trigger guidelines more dynamic and character-save agnostic.

Recommendation

Apply the proposed workaround by updating the image trigger guidelines and the relevant code files to use the dynamic path based on the game.character.referenceImagePath field. This will allow for more flexibility and scalability in managing character images across different saves and characters.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix feat: 세이브별 동적 캐릭터 레퍼런스 이미지 시스템 [1 comments, 1 participants]