| name | uma-show-event-version |
| description | Add or update UmaShow event rules in src/constant/events.ts and bump UmaShow app versions in package.json, package-lock.json, release/app/package.json, and release/app/package-lock.json. Use when the user asks to add an event, modify event options or success/failure mappings, or update the project version number. |
UmaShow Event And Version
Follow this workflow:
- Read
src/constant/events.ts and locate the nearest matching event block by story ID range or character/event group.
- Add or update the target entry inside
EXACT_EVENT_RULES.
- Keep the event shape as:
name: string
options: EventOptionGroup[]
- each selectable branch keyed by choice number
- For simple binary outcomes, use:
1: { desp: '成功', detail: '成功', type: 'correct' }
2: { desp: '失败', detail: '失败', type: 'wrong' }
- Preserve the file's existing structure and avoid broad rewrites, because this file may contain mojibake-like text in terminal output.
When updating the version number:
- Keep these files in sync:
package.json
package-lock.json
release/app/package.json
release/app/package-lock.json
- Prefer a patch bump unless the user specifies another target version.
- In each lockfile, update both the top-level
version and the root package entry under packages[""] when present.
Validation checklist:
- Confirm the new story ID exists only once in
src/constant/events.ts.
- Confirm all four version files carry the same app version.
- Avoid editing unrelated event rules.