Issues caused by incorrect ritual coordinate configuration leading to overlapping ritual icons on the table or failure to generate

• Understand the available ritual coordinates in the game
  • Court: 1~11
  • Home: 1~14
  • Upper City: 1~12
  • Dark Alley: 1~10
  • Commercial District: 1~19
  • Temple District: 1~11
  • Wild: 1~15
  • Treasure: 1~15
  • Great Adversary: 1~6
  • Ending: 1~7
• How to set coordinates

  • Set fixed coordinates

    • If two rituals with the same fixed coordinate number generate simultaneously, they will overlap.

    "id": 5000001,
            "name": "Managing the Estate",
            "text": "People are still willing to come under your roof and share words, promises, and opportunities.",       
            "tips": "",
            "mapping_id":8001002,
            "once_new":1,
            "round_number": 1,
            "waiting_round":0,
            "waiting_round_end_action":[
            ],
            "method_settlement": "",
            "auto_begin": 1,
            "auto_result":1,
            "location": “Home:1", //only generated on Home:1 coordinate
    

  • Set random coordinates

    • If two rituals with random coordinates generate with the same number, they will automatically adjust to maintain a suitable distance.

    "id": 5000016,
            "name": "Battles at Night",
            "text": "Reading can improve yourself, so develop a habit of reading.",       
            "tips": "",
            "mapping_id":8001005,
            "once_new":0,
            "round_number": 1,
            "waiting_round":1,
            "waiting_round_end_action":[
            ],
            "method_settlement": "",
            "auto_begin": 0,
            "auto_result":0,
            "location": “Home:[2,12]", //randomly generated on Home:2~12 coordinate
    

Issues caused by the number of ritual slots leading to failed ritual generation

• The number of ritual slots cannot exceed 15. It is recommended to keep it under 10, as exceeding this may cause display issues like overflow in the default ritual background.
• If users modify and increase the number of slots for an existing ritual, it is recommended to delete the mapping_id parameter (if configured). Otherwise, mismatches between the slot count and the background's preset slot count may cause the ritual to fail to generate.

"id": 5006531,
        "name": "The Taste of Revenge",
        "text": "What kind of story is recorded in this book, which was placed outside your bedroom door by an unknown person?",       
        "tips": "",
        "mapping_id":8001005, //delete this parameter if increase slot count
        "once_new":1,
        "round_number": 1,

• The mapping_id indexes the current ritual's background template, which includes the background, slot count, and slot position information. If a ritual does not have mapping_id configured, it will default to the basic template background. The basic template is recommended for no more than 10 slots, with a maximum of 15 slots.
  • Does not support previewing or editing ritual backgrounds for now

Issues with have condition misuse, leading to failure in generating rituals or backstage actions due to missing corresponding cards

• Cards in the game exist in several status:
  • [Non-existent]: Cards that have not been generated or have been removed.
    • These cards cannot be targeted by any conditions or actions.
    • Special case: Cards equipped to other cards cannot be found by have. Flexible use of inheritable tags can help locate them.
  • [Exists, in hand]: Cards that have been generated and are currently in the player's hand (inventory).
    • These cards can be found by conditions like have, table_have, and hand_have.
    • These cards can be targeted by actions like table and total.
  • [Exists, not in hand, idle]: Cards that have been generated but are in the player's invisible "card pool."
    • These cards can be found by conditions like have and table_have.
    • These cards can be targeted by actions like table and total.
  • [Exists, not in hand, in ritual]: Cards that have been generated and are currently in ritual slots.
    • These cards can be found by conditions like have.
    • These cards can be targeted by actions like total.

Issues with ritual generation failure via event

• Common cause: The generated ritual is set to automatically absorb specified cards, but the corresponding cards do not exist or are not in an idle state.
• Solution: Add a condition to check whether the corresponding cards are idle.

-------------------Example---------------------------------
{
        "id": 5300002,
        "text": "Seeking Temple Aid",  
        "is_replay": 0, 
        "auto_start": false, 
        "start_trigger": true,
        "on":{
            "round_begin_ba": 1 //start of each round
        },
        "condition":{
            "table_have.2000021":1  //have idle priest on the table
        },
        "settlement": [    //effect
            {
                "tips_resource":"", 
                "tips_text":"",
                "action":{
                    "rite":5000508
                }
            }

        ]
    }

• Cards generated via event do not appear in hand.

  • Check if the generated cards have the [Owned] or [Follower] tag.
  • If not, add these tags during generation.

  -------------------Example---------------------------------
  {
          "id": 5300002,
          "text": "Seeking Temple Aid",  
          "is_replay": 0, 
          "auto_start": false, 
          "start_trigger": true,
          "on":{
              "round_begin_ba": 1 //start of each round
          },
          "condition":{
          },
          "settlement": [    //effect
              {
                  "tips_resource":"", 
                  "tips_text":"",
                  "action":{
                      "card":[2000771,”Owned+1"]
                  }
              }
  
          ]
      }
  
  

A card in hand meets the slot condition but cannot be placed into a ritual slot.

• Common cause: The card has an "adsorption specified" effect tag.
• Solution: If this tag is unintended, remove it or modify the adsorption configuration as needed.

The ritual requires adsorbing a specific card, but the corresponding card doesn't exist, causing the ritual to fail.

• Common cause: The automatic adsorption required card for the ritual is not in an idle state.