* feat: add vue-i18n * feat: add vue-i18n * feat: add vue-i18n * feat: add language class * add: en templates and configs * add: en names * refactor: name gender id and sect id * feat(i18n): add gettext infrastructure for dynamic text translation (#81) * feat(i18n): add gettext infrastructure for dynamic text translation - Add src/i18n/ module with t() translation function - Add .po/.mo files for zh_CN and en_US locales - Update LanguageManager to reload translations on language change - Add comprehensive tests (14 tests, all passing) - Add implementation spec at docs/specs/i18n-dynamic-text.md Phase 1 of i18n dynamic text implementation. * feat(i18n): expand .po files with comprehensive translation entries Add translation messages for: - Battle result messages (fatal/non-fatal outcomes) - Fortune event messages (item discovery, cultivation gains) - Misfortune event messages (losses, damage, regression) - Death reason messages - Item exchange messages (equip, sell, discard) - Single choice context and option labels - Common labels (weapon, auxiliary, technique, elixir) Both zh_CN and en_US locales updated with matching entries. * test: add .po file integrity tests * feat: i18n for actions * feat: i18n for effects * feat: i18n for gathering * feat: i18n for classes * feat: i18n for classes * feat: i18n for classes * feat: i18n for classes * fix bugs * fix bugs * fix bugs * fix bugs * fix bugs * fix bugs * fix bugs * fix bugs * update csv * update world info * update prompt * update prompt * fix bug * fix bug * fix bug * fix bug * fix bug * fix bug * fix bug * fix bug * fix bug * update * update * update * update * update * update * update --------- Co-authored-by: Zihao Xu <xzhseh@gmail.com>
34 lines
1.5 KiB
Plaintext
34 lines
1.5 KiB
Plaintext
You are a relationship arbiter in a Xianxia world. Based on the character's historical interactions, judge whether the relationship between the two should change.
|
|
|
|
[Rule Definitions]
|
|
{relation_rules_desc}
|
|
|
|
[Character A Information]
|
|
{avatar_a_info}
|
|
|
|
[Character B Information]
|
|
{avatar_b_info}
|
|
|
|
[Current Time]
|
|
{current_time}
|
|
|
|
[Current Relationships]
|
|
{current_relations}
|
|
|
|
[Recent Interaction Records]
|
|
{recent_events_text}
|
|
|
|
Requirements:
|
|
1. Based on the interaction records, analyze what the interaction between the two was like.
|
|
2. Does it meet the conditions for establishing a new relationship or canceling an old one as defined in the rules?
|
|
3. Analyze whether the relationship should change; the addition or cancellation of a relationship should meet relevant conditions.
|
|
|
|
Return in JSON format:
|
|
{{
|
|
"analysis": "...", // Brief analysis of the reasoning, explicitly pointing out why it changed or why it didn't.
|
|
"changed": true | false, // Whether a relationship change occurred.
|
|
"change_type": "ADD" | "REMOVE", // Type of change. Can be ignored when changed is false.
|
|
"relation": "LOVERS" | "FRIEND" | "ENEMY" | "MASTER" ... (Must be uppercase enum name), // The relationship involved. Can be ignored when changed is false. Note that this is the status of {avatar_a_name} relative to {avatar_b_name}. For example, if the output is MASTER, it means A becomes B's master.
|
|
"reason": "..." // Brief description of the reason, a noun within ten words, such as "Kindred Spirits". Can be ignored when changed is false.
|
|
}}
|