Tuxepedia - User contributions [en]

Qiangong2's plot

2026-04-11T06:26:50Z

Jaskrendix:

[https://forum.tuxemon.org/thread.php?id=239 Details on the forum].

Takes place in the [[Fondent region]], where [[Omnichannel]] has total control (the [[Cathedral]]'s Pillars don't exist).

== Omnichannel ==
Omnichannel is the ruling power of the Fondent region. While a nominal local government still exists, nearly all authority is concentrated under Omnichannel leadership. The organization functions as an authoritarian state, with a structure comparable to North Korea: strict hierarchy, pervasive surveillance, and absolute control over public life.

Omnichannel rose to power 25 years ago during the Tuxemon Rampage. As the previous administration failed to contain the attacks, public trust collapsed. Omnichannel gained rapid support by endorsing a short‑term plan to cull the most dangerous Tuxemon, which quickly reduced casualties. Their popularity surged, allowing them to seize political control and consolidate power under CEO Kane.

After taking control, Omnichannel captured nearly all remaining Tuxemon and relocated them to underground research facilities beneath their headquarters. Only a small number of species essential to the environment were allowed to remain in the wild. Although Omnichannel publicly banned unauthorized Tuxemon experimentation, certain individuals—such as Cam—were privately permitted to continue their research when it served Omnichannel's interests.

* '''HQ:''' [[Cotton Town]]
* '''Public CEO / Figurehead:''' [[Aeble Flisk]]
* '''True Leader:''' [[Omnichannel CEO Kane]]
* '''Advisors:''' –
* '''Board of Directors:''' –
* '''Security / Police:''' Omnichannel's enforcement ranks are not formally documented, but commonly observed roles include [[Enforcer Boss]]es, [[Enforcer Rookie]]s and [[Enforcer Agent]]s
* '''Motto:''' ''"We are Safety, We are Order, We are Omnichannel"''
* '''Info:''' Omnichannel maintains strict control over Tuxemon, research, and public life through propaganda, surveillance, and a rigid Enforcer hierarchy.

== The Trial ==
Publicly, the Trial is presented as a unifying celebration meant to reconnect the region after years of strict movement restrictions. In reality, it functions as a recruitment pipeline: Omnichannel uses the Trial to identify individuals with exceptional strength, charisma, or psychological resilience who can be molded into the next generation of Omnichannel leadership. The spectacle also serves as propaganda, giving the populace something to rally behind.

== Team Xero / Xero Institute for Tuxemon Research ==
The Xero Institute was originally founded by [[Martin Xero]], a former member of Omnichannel's board of directors, shortly before Kane's rise to power. During the Tuxemon Rampage, the Institute played a key role in researching Tuxemon weaknesses and containment strategies. Because of this contribution, the Institute retained a degree of autonomy even after Omnichannel seized control.

Three major figures shaped the Institute's early direction:
* '''[[Kay Wren]]''' – believed Tuxemon could be tamed and trained without harming them.
* '''[[Cam]]''' – believed Tuxemon should be drained of their power to make them docile, later experimenting on humans to contain that power.
* '''The Xero Member''' – advocated for eliminating all Tuxemon deemed too dangerous or "useless."

Martin Xero was eventually purged after Omnichannel discovered he had been secretly protecting Tuxemon instead of assisting with extermination efforts. Following his removal, his daughter Misa gathered sympathetic researchers and staff. Over time, this group expanded until it encompassed the entire Institute, transforming it into '''Team Xero'''.

Team Xero remains the only branch of Omnichannel ever granted permission to breed new Tuxemon, a privilege established during the crisis and never formally revoked. Approximately 10 years after the rampage, the [[Kay Wren]] split from the Institute for personal, power‑driven reasons, though the full implications remain unclear, continuing his research independently with Omnichannel's approval.

Misa is fully aware of Allie's growing influence within Omnichannel. As Martin Xero's daughter and the leader of Team Xero, she understands exactly how powerful her sister has become. However, because Omnichannel and Xero are rival organizations, she has no ability to stop Allie's rise or interfere with her operations.

Team Xero is not publicly acknowledged by Omnichannel; to ordinary citizens they function like a secret service—never mentioned, never officially recognized.

== History ==
Twenty‑five years ago, the Fondent region experienced the Tuxemon Rampage, a sudden outbreak in which Tuxemon across the region turned hostile and began destroying settlements. The existing government failed to contain the crisis, leading to widespread panic and loss of public trust.

During this period, Omnichannel gained rapid support by endorsing a short‑term plan proposed by a Xero Institute member to cull the most dangerous Tuxemon. The immediate reduction in casualties caused Omnichannel's approval to skyrocket, allowing the organization to seize political control and eventually consolidate all authority under CEO Kane.

After the crisis, most surviving Tuxemon were captured and relocated to underground facilities beneath Omnichannel HQ. Only a small number of species essential to the environment were allowed to remain in the wild. The Protagonist's family fled the region during this period and returned only after Omnichannel had fully asserted control.

== Tuxemon Rampage ==
The Tuxemon Rampage occurred 25 years before the events of the game. The Rampage was caused by experiments gone wrong, though the exact details remain obscured by Omnichannel. During the rampage, Tuxemon across the region became uncontrollably violent, destroying towns and forcing many families, including the Protagonist's, to flee Fondent.

Three researchers were tasked with responding to the crisis:
* '''[[Kay Wren]]''' – sought to tame Tuxemon without harming them.
* '''[[Cam]]''' – attempted to drain Tuxemon of their power to make them docile.
* '''The Xero Member''' – advocated for culling all "dangerous" or "useless" Tuxemon.

Omnichannel approved the Xero member's plan in the short term, which reduced attacks and increased public support. This event directly enabled Omnichannel's rise to power.

== Key Figures ==
=== [[Kay Wren]] - "The Tuxemon Professor" ===
A researcher who believed Tuxemon could be tamed and trained without harming them. After the rampage, he worked underground to rehabilitate and breed Tuxemon. He later split from the Institute for personal, power‑driven reasons, though the full implications remain unclear. During the Rampage, Aeble served only as a minor administrative assistant and was not involved in Kay Wren's research or decisions.

=== [[Cam]] ===
A researcher obsessed with extracting and harnessing Tuxemon power. Cam experimented on both himself and Omnichannel grunts, often driving subjects to madness. Although Omnichannel publicly shut down his work, he was privately allowed to continue until his methods became too dangerous. After proving that human‑Tuxemon merging was possible, he was brought back into Omnichannel's service.

=== Unknown Xero Member ===
A pragmatic figure who believed only "useful" Tuxemon should be allowed to live. Their culling strategy was instrumental in Omnichannel's rise to power. After the Rampage, the unknown Xero member disappeared from the political scene, and their whereabouts remain unknown.

== Characters ==
=== Family Wren ===
The Wren family is one of the most important scientific lineages in the Fondent Region, deeply tied to both the Tuxemon Rampage and the protagonist's personal history.

* [[Kay Wren]] – "The Tuxemon Professor" Former Xero Institute researcher; now an independent scientist tolerated by Omnichannel.
* Kay's Wife – Unnamed; not involved in the story and only mentioned in passing.
* [[Maple Wren]] – Kay's daughter and mother of the Protagonist. Disappeared on April 27 under mysterious circumstances.
* [[Callie Wren]] – Kay's daughter and aunt of the Protagonist. Raises the protagonist after Maple's disappearance.

=== The Xero Lineage ===
Once part of Omnichannel's leadership, the Xero family became the heart of the resistance after Martin's purge.

* [[Martin Xero]] – Founder of the Xero Institute; purged by Kane for protecting Tuxemon.
* [[Misa]] – Martin's daughter; founder and leader of Team Xero.
* [[Allie]] – Misa's sister; defected to Omnichannel and is one of Omnichannel's most influential operatives, wielding significant authority despite not being part of the inner ruling circle. Her true rank is secretly far higher than publicly acknowledged, a fact revealed only in late‑game. Her power is substantial enough that even Misa, who knows her well, cannot counteract her influence within the regime.

=== Omnichannel Leadership ===
The authoritarian rulers of the Fondent Region.

* [[Omnichannel CEO Kane]] – Founder of the regime and true leader of Omnichannel, operating behind the scenes.
* [[Aeble Flisk]] – Public-facing "CEO" and figurehead who represents Omnichannel to the public. He was present during the Tuxemon Rampage in a low‑level administrative role and only knew fragments of what was truly happening. Even today, he understands he is being manipulated by Kane but is content with his position and never questions the regime.
* [[Kyle]] – High‑ranking Omnichannel enforcer; known for brutality and psychological warfare.
* [[Allie]] – A highly influential Omnichannel operative with significant authority, though not part of the inner ruling circle. Her true rank is secretly far higher than publicly acknowledged, a fact revealed only in late‑game.

=== The Trial Participants ===
Individuals selected or coerced into participating in Omnichannel's televised Trial.

* [[Christie]] – A powerful but unstable recruit with a troubled past in Omnichannel training.
* [[Speck]] – A young participant whose family was imprisoned by Omnichannel.

== Formation of Team Xero ==
The Xero Institute was originally Omnichannel's Tuxemon research division, founded by [[Martin Xero]]. After Martin was purged for secretly protecting Tuxemon, his daughter Misa gathered sympathetic researchers and staff. Over time, this group expanded until it encompassed the entire Institute, becoming known as '''Team Xero'''.

Team Xero inherited the Institute's autonomy and remains the only organization in the region permitted to breed new Tuxemon, a privilege granted during the crisis and never formally revoked.

== Protagonist Background ==
The Protagonist was not raised in the Fondent region. Their family fled during the Tuxemon Rampage after losing their home. They returned only after Omnichannel had fully established control. Because the Protagonist is an unknown factor who did not grow up under Omnichannel's system, both Omnichannel and Team Xero take an interest in them.

== References in Dialogue ==
* Flower City Incident – A major event referenced in dialogue. Canonically, no information has been revealed about what happened, and the developers intend for it to remain mysterious.

== Canon vs. Mystery Table ==

This table summarizes which elements of the Fondent‑era storyline are established canon and which are intentionally left unexplained. Items in the "Mystery" column are not to be expanded, solved, or contradicted in future contributions unless explicitly approved.

{| class="wikitable"
! Topic
! What Is Canon
! What Remains a Mystery
|-
| '''Tuxemon Rampage'''
| Caused by experiments gone wrong; Tuxemon became violent; government collapsed; Omnichannel rose to power.
| Exact nature of the experiment; who initiated it; whether it was sabotage or an accident.
|-
| '''Culling Plan'''
| Proposed by the unknown Xero member; approved by Omnichannel; reduced casualties; boosted Omnichannel's popularity.
| How many species were wiped out; which species; long‑term ecological consequences.
|-
| '''Underground Tuxemon Storage'''
| Most surviving Tuxemon were captured and stored beneath Omnichannel HQ.
| What exactly is stored there; how many Tuxemon remain; what experiments continue today.
|-
| '''Flower City Incident'''
| Referenced in dialogue as a major event that filled the prisons.
| Cause, scale, casualties, political consequences, and responsible parties.
|-
| '''Omnichannel Leadership'''
| Kane is the true leader; Aeble is a willing figurehead; Kyle is a high‑ranking enforcer; Allie is a powerful operative, her true rank within Omnichannel is concealed.
| Kane's long‑term plans; structure of the inner circle; how Kane maintains control.
|-
| '''The Trial'''
| Publicly a unifying celebration; secretly a recruitment pipeline for future Omnichannel leaders; also propaganda.
| Internal evaluation criteria; what happens to winners after the Trial.
|-
| '''Team Xero'''
| Founded by Martin Xero; taken over by Misa after his purge; only group allowed to breed Tuxemon.
| The deeper consequences of Kay Wren’s ambition; the unknown Xero member’s disappearance and current whereabouts.
|-
| '''Unknown Xero Member'''
| Advocated culling; pragmatic; helped gather surviving Tuxemon.
| Identity, motivations, and whether they still influence events.
|-
| '''Kay Wren'''
| Former Xero researcher; father of Maple and Callie; tolerated by Omnichannel.
| His deeper involvement in the Rampage; what he knows about Kane; the deeper consequences of his ambition remain unclear.
|-
| '''Maple Wren'''
| Mother of the protagonist; disappeared on April 27; Kay's daughter.
| Why she disappeared; where she went; whether she is alive.
|-
| '''Callie Wren'''
| Aunt of the protagonist; raised the player; Kay's daughter.
| What she knows about Maple's disappearance; why she stayed behind.
|-
| '''Allie'''
| Misa's sister; defected to Omnichannel; extremely influential; Misa knows her true rank.
| How she rose so quickly; her long‑term goals; her relationship with Kane.
|-
| '''Cam'''
| Experimented on humans and Tuxemon; cast out then reinstated; obsessed with draining Tuxemon power.
| How much of his research Omnichannel still uses; what he truly believes about "the Truth."
|-
| '''Fondent Region Under Omnichannel'''
| Authoritarian; surveillance; propaganda; strict hierarchy; movement restrictions.
| True public sentiment; existence of other resistance groups besides Xero.
|-
| '''Tuxemon in the Present Day'''
| Rare; controlled; bred only by Xero; most species extinct or contained.
| True number of surviving species; existence of hidden wild populations.
|-
| '''Public Knowledge'''
| Citizens know the official story: Rampage → Omnichannel saved them. Omnichannel routinely uses the Rampage as a fear‑based warning, telling citizens that disobedience risks triggering another catastrophe.
| How much the public suspects; whether rumors about the truth circulate.
|-
| '''Protagonist's Family'''
| Fled during the Rampage; returned after Omnichannel took control.
| Whether they were targeted; whether Maple's disappearance is connected to Omnichannel.
|-
| '''Protagonist's File'''
| Omnichannel is concerned because the protagonist is an unknown who did not grow up in Fondent.
| What exactly is in the file; why Omnichannel is so interested; whether Kane has a personal motive.
|}

Flashbacks Ideas

2026-03-02T14:25:59Z

Jaskrendix:

This page collects flashback concepts that may be used across different campaigns. All content here should be considered provisional — not yet implemented or officially approved. Approved flashbacks appear on their respective campaign pages.

* [[Flashbacks Spyder]]
* [[Flashbacks Xero]]

= Spyder =

== The Statues Must Fall ==

;Monk: These statues are not mere stone. They are memory. They are balance. Remove them, and Cotton Town forgets what it once honored.
;Beaverbrook: Ah, Monk of the Five Elements! Just the voice I hoped to hear echoing through these quaint ruins. Come—walk with me. Let’s talk strategy.
;Monk: I do not strategize. I tend. I listen. I preserve.
;Beaverbrook: Preservation is stagnation. You guard relics while the world evolves. Omnichannel offers progress—fusion, expansion, deluxe Tuxemon in every home!
;Monk: Progress without reverence is conquest. These statues mark the elemental balance. Their removal will unmoor the town’s spirit.
;Beaverbrook: Spirit? Please. We’re talking prime real estate. The statues can be digitized, archived, reimagined in augmented reality. Isn’t that enough?
;Monk: You cannot archive presence. You cannot simulate silence. These stones breathe with the town.
;Beaverbrook: Then let them breathe in a museum, behind velvet ropes. Cotton Town will be our flagship campus. The statues are in the way.
;Monk: You speak of campuses and flags. I speak of wind and stone. We are not aligned.
;Beaverbrook: Alignment is overrated. I don’t need your blessing—I need your silence. Or better yet, your endorsement. Imagine: ‘Monk Approved Expansion.’ Has a ring to it.
;Monk: I will not bless desecration. But I will remain. And I will remember.
;Beaverbrook: Suit yourself. But when the birthing pits open and the fusion begins, don’t say I didn’t offer you a seat at the table.

== The Token Protocol ==

;Beaverbrook: Looten's data confirmed the instability. The creature's lifespan is short—four minutes of evolution followed by system collapse. We need to monetize that instability, Rhodes.
;Rhodes: Instability is a liability, sir. It suggests a refund cycle.
;Beaverbrook: No. It suggests a renewal cycle. Every evolution must be a costly, one-time event. When the creature expires, the trainer must return to us. We need a consumable product to trigger the Fusion.
;Rhodes: A consumable that validates the investment... a single-use key. We can link the transaction to a blockchain, preventing replication. Let’s call it a Fusion Token.
;Beaverbrook: Brilliant. The tokens will be the key to our entire deluxe line. They will be scarce, highly priced, and tied directly to the creature’s inevitable decay.
;Rhodes: This will generate enormous recurring revenue. We’re not selling evolution; we’re selling momentary supremacy at a premium.
;Beaverbrook: Exactly. We sell the miracle, and then we sell the replacement. Get the legal team drafting the EULA for the Fusion Token immediately. I want it ironclad.

== The First Data Point ==

;Looten: The core held! For four minutes, the subject experienced instantaneous, stable evolution. The subsequent meltdown was regrettable, but scientifically, this is an unparalleled success!
;Beaverbrook: Success is repeatable and scalable, Looten. Four minutes of stability is a feature, not a success. What is the turnover rate? How quickly can we run the next cycle?
;Looten: The creature's lifespan was short, yes. But that’s a biological challenge we need to research—
;Beaverbrook: Nonsense. That is a built-in upgrade cycle. We sell the initial evolutionary success, and when the creature expires, the customer requires a new Fusion Token for a replacement. It’s perfect retention.
;Looten: You're turning this into planned obsolescence! This is a sentient being!
;Beaverbrook: It's a market opportunity. Your initial research cost millions. Your duty is to ensure we achieve an adequate return on investment. I want a proposal for tokenizing the process by end of day. No more pure science, Looten. It's time for mass market monetization.

== The Ashes of Prototype Seven ==

;Looten: Prototype Seven was... promising. The fusion held for nearly six minutes. That’s a record.
;Beaverbrook: Held? It screamed, Looten. It screamed and then melted through the floor.
;Looten: Progress is messy. We’re closer than ever. The neural lattice almost stabilized.
;Beaverbrook: Almost. Almost doesn’t sell. Almost doesn’t survive a press cycle. Do you know what the shareholders saw? A crater.
;Looten: They’ll see the potential. Once we refine the containment shell—
;Beaverbrook: Containment? You think this is about containment? This is about optics. About control. About deluxe Tuxemon in every living room, not radioactive grief in a bunker.
;Looten: You wanted evolution. I gave you fusion. You wanted miracles. I gave you monsters.
;Beaverbrook: I wanted marketable miracles. Not twitching abominations that eat their own tails.
;Looten: You’re afraid of the future. You want it sanitized. Packaged. But real progress is raw. It bleeds.
;Beaverbrook: And yet here you are, bleeding credibility. You think you’re a pioneer. You’re a liability with a lab coat.
;Looten: You don’t understand the science.
;Beaverbrook: I understand the story. And right now, the story is slipping. We need a win, Looten. A mascot. A miracle. Not another meltdown.
;Looten: Then let me try again. Prototype Eight. No ethics board. No oversight. Just pure creation.
;Beaverbrook: Fine. But if it screams... you scream with it.

== The Poisoned Sample ==

;Looten: The Core data is complete, but it confirms everything: the Fusion process is inherently unstable. It generates trauma that we are selling as 'evolution.'
;Dr. Elara: Send the raw metrics to Beaverbrook. We need to finalize the 'Apex' production line before the next fiscal quarter review.
;Looten: I can’t. This data is a ticking bomb. If the Tuxemon Project gets a hold of this, they can use it to prove the system is fundamentally flawed.
;Dr. Elara: Then destroy it, Looten. You know the protocols. Delete the research, take the payout, and take a vacation. Your conscience is an unauthorized variable.
;Looten: I have no conscience left, Elara. Only guilt. I wanted evolution, and I created weapons. But I can still stop them from being mass-produced.
;Dr. Elara: What are you doing? Stop! You’ll contaminate the entire secure server!
;Looten: I’m not deleting the research, Elara. I’m giving it to the public. It will be scrambled, a mere fragment, but it will contain the signature instability of the Fusion Cores.
;Dr. Elara: You’re signing your death warrant! Omnichannel will hunt you to the ends of the earth!
;Looten: Let them. It's the only way to pay the ethical debt. If this data gets into the right hands, they’ll have the key to understanding the corruption. They’ll have their first data point.

== The Lakebed Briefing ==

;Zoolander: It’s done. The lake’s gone. The river’s been rerouted. The basin’s dry.
;Beaverbrook: And what a basin it is... Look at it. Like a peeled fruit. Secrets exposed. Potential... ripening.
;Zoolander: There were nesting grounds down there. Ecosystems. We flushed them out like waste.
;Beaverbrook: Waste is subjective. Investors see opportunity. [[Cathedral]] sees legacy. And Omnichannel? We see product.
;Zoolander: You said it was just a geological survey. You said we were looking for mineral veins.
;Beaverbrook: I said what you needed to hear. Now you’re hearing the truth. The eggs are real. The myths were marketing. And you, dear Zoolander, are part of history.
;Zoolander: History doesn’t absolve us. We displaced families. Poisoned wells. The mine’s workers are scared. They whisper about things moving in the mud.
;Beaverbrook: Let them whisper. Fear is engagement. Engagement is retention. Retention is revenue.
;Zoolander: You talk like the mine is a storefront. Like the lake was a billboard.
;Beaverbrook: It was. And now it’s a launchpad. The fusion cores beneath that sediment? They’ll power the next generation of deluxe Tuxemon. Imagine: ‘Born from the bones of the forgotten.’ Has a ring to it.
;Zoolander: You’re not listening. Something’s wrong down there. The readings are erratic. The eggs... they pulse.
;Beaverbrook: Then let them hatch. Let them scream. Let them sell.
;Zoolander: I didn’t sign up for this.
;Beaverbrook: You signed the Cathedral charter. You rerouted the river. You drained the lake. You’re already in the story, Zoolander. Now decide: are you a footnote... or a founder?

== The Directive Divide ==

;Zircon: The prototype disobeyed a direct command. It turned on its handler. That’s not evolution—it’s insubordination.
;Beaverbrook: Insubordination? Please. It was improvising. Adapting. That’s what we engineered it to do.
;Zircon: We engineered it to follow orders. To execute precision strikes. Not to ‘improvise’ a massacre.
;Beaverbrook: Massacre is such a military word. I prefer ‘brand disruption.’ The footage is trending. Engagement is through the roof.
;Zircon: You think this is about metrics? We lost three operatives. One of them was seventeen.
;Beaverbrook: And yet the public sees a miracle. A creature born of fusion, unbound by limits. They’re calling it ‘The Apex.’
;Zircon: The Apex is unstable. It ignored its kill-switch. It’s not a soldier—it’s a liability.
;Beaverbrook: It’s a symbol. A flagship. A deluxe Tuxemon with battlefield charisma. We’ll tweak the firmware.
;Zircon: You’re playing dress-up with a weapon. This isn’t a toy line—it’s a tactical asset.
;Beaverbrook: And assets must be marketable. You want obedience. I want awe. The Apex delivers both... eventually.
;Zircon: You’re gambling with lives. I’ve seen what happens when control slips. You haven’t.
;Beaverbrook: I’ve seen what happens when vision is shackled by fear. You want a leash. I want a legacy.
;Zircon: Then pray your legacy doesn’t bite back.
;Beaverbrook: If it does... we’ll sell the scars.

== The Empathy Protocol ==

;Argon: They’re responding to music now. Not just rhythm—melody. Some even mimic it. That’s not programming. That’s preference.
;Beaverbrook: Preference? Please. It’s a glitch with good PR. We’ll call it ‘EmoSync’ and sell it as a feature.
;Argon: It’s not a feature. It’s a sign of emergent consciousness. These Tuxemon aren’t just reacting—they’re relating.
;Beaverbrook: Relating doesn’t pay dividends. Reacting does. We engineered them to bond, not philosophize.
;Argon: You engineered them to obey. But they’re evolving. They’re forming attachments. They grieve.
;Beaverbrook: Grief is a marketing opportunity. Imagine the campaign: ‘They miss you when you’re gone.’ Tug the heartstrings, open the wallets.
;Argon: You’re missing the point. If they feel, we owe them protection. Rights. Autonomy.
;Beaverbrook: Autonomy? You want to unionize the monsters? Give them voting privileges? They’re assets, Argon. Beautiful, profitable assets.
;Argon: They’re alive.
;Beaverbrook: They’re licensed. And if you keep pushing this empathy agenda, you’ll be obsolete.
;Argon: Then I’ll be obsolete. But I won’t be complicit.
;Beaverbrook: Suit yourself. But when the deluxe line launches with ‘EmoSync 2.0,’ don’t act surprised. You gave us the data. We just gave it a price tag.

== Tuxemon Project People (NPCs) ==

;Evelyn: The Visionary (Tuxepedia Idea, moral mandate, TuxemonNet algorithm).
;Liam: The Outreach and Interface Designer (UX, community building, practical skepticism).
;Maya: The Network and Logistics Specialist (Contacted [[Team Bazaar]], handled international research).
;Julian: The Backend and Security Architect (Ensured data was distributed, resilient, and secure).

== Tuxemon Project Mission ==

;Evelyn: The fight isn't just about escaping the Pillars; it's about building a foundation for truth. That's the real purpose of this project.
;Liam: Exactly. The Tuxepedia is the archive, the record of every Tuxemon out there. It counters the corporate lie with decentralized, community-vetted fact.
;Maya: And it has to be more than just names and numbers. We need the deep, scientific analysis—the how and the why. That's where TuxemonNet comes in.
;Julian: TuxemonNet is the engine. It's the open-source algorithm that can categorize creatures without bias. It prevents them from corrupting the science to promote their "deluxe" or "Apex" models.
;Evelyn: We saw what happened to Argon and Looten's work—it was corrupted and sold. Our ultimate mission is to promote Partnership and Autonomy. We must expose the unethical use of the fusion process.
;Liam: We shift the paradigm. No more 'assets,' no more 'munitions.' We give trainers the knowledge to respect, not just control.
;Maya: The integrity of the data is everything. If we remain open and distributed, they can't take us down. The community becomes the fail-safe.
;Julian: We're not building a single fortress. We're building a network of resistance. And every piece of shared knowledge is a blow against their control.
;Evelyn: The Tuxemon Project is the collective promise that knowledge will be free, and every Tuxemon's life will hold value beyond its market price.

== First Bazaar Meeting ==

;Evelyn: The Tuxemon Project is official. We have the algorithm, the database design, and the ethical mandate. But we can't launch from a clean corporate server; that’s suicide.
;Liam: We need a network that is literally off the grid. Decentralized hubs, not single fortresses.
;Maya: I made contact with a group that fits that description—they call themselves [[Team Bazaar]]. They champion open systems and operate outside the Pillars' data monopolies.
;Julian: Can we trust them? They sound like digital pirates.
;Maya: They are liberty-loving wanderers. They use "pirate radio" and pop-up labs. Their philosophy is that shared knowledge is resistance. They're already doing what we want to do, but without the core data.
;Evelyn: Then they are our vessel. We offer them the Tuxepedia data, and they offer us their network. Where are they based?
;Maya: I've arranged a meet at a forgotten mansion near Flower City. It’s their unofficial main hub.
;Liam: A forgotten mansion? That sounds less like a secure network and more like a death trap.
;Julian: It sounds like the perfect anti-establishment camouflage. If Omnichannel can't track them, they can't track us. Let's embrace the chaos.
;Evelyn: We become part of the swarm. We leave the clean spreadsheets behind and enter the bazaar. This is how we go truly decentralized.

== Tuxepedia Idea ==

;Evelyn: We need a way to catalog all the tuxemon out there. Something that's accessible to everyone, not just the Pillars.
;Liam: I've been thinking about that. What if we create a database that's open-source? Anyone can contribute, anyone can access it.
;Maya: But how do we guarantee the information is accurate? If we just throw the gates open, we risk chaos.
;Evelyn: We can create a system of expert moderators—vetted researchers who can review and verify the data before it's published. It ensures quality control without centralization.
;Julian: And what about the Pillars? They won't just stand by while we build something that undermines their authority.
;Liam: We start small. We build a groundswell of supporters. By the time we have enough momentum, the Pillars won't be able to stop us without a public relations nightmare.
;Maya: I love the idea, but it needs a solid name. What are we going to call this thing?
;Evelyn: How about 'Tuxepedia'? It’s a clean blend of 'encyclopedia' and 'tuxemon'.
;Julian: I like the simplicity of just 'Tuxepedia'—like Wikipedia. It feels community-focused, less formal.
;Liam: Hmm. I see your point, Julian, but 'The Tuxepedia' sounds more established, more official for a global resource.
;Maya: I think Evelyn has the right idea; simple is better. 'Tuxepedia' it is.
;Evelyn: Alright, then. Let's get to work. We have a lot of conceptual ground to cover before we can make this vision a reality.

== Tuxepedia Project ==

;Evelyn: I've been working on a new algorithm called 'TuxemonNet'. A neural network that can analyze and categorize tuxemon characteristics automatically. It’s a key to unlocking the true potential of tuxemon research, and it will be open-source. I think I've finally cracked it! I was up all night testing it, and the algorithm identified 95% of the tuxemon in the test dataset.
;Liam: That's astounding, Ev! Let me take a look at the code. Does it handle the complexities of type-morphing and regional variations well?
;Evelyn: It's working beautifully with the small dataset. We can use this to create a robust and scalable database. I’m thinking machine learning will continuously refine the categorization over time.
;Liam: This is the fuel we needed. We can finally start building the Tuxepedia. I've been sketching out a user interface—it needs to be intuitive, even for beginner trainers.
;Maya: I’m buzzing with excitement! We're genuinely going to change the way people think about tuxemon. I’ve already contacted some international researchers, and they're all eager to contribute.
;Julian: I'm focused on the backend. It needs to be secure and resilient to handle a massive volume of data, especially as we scale. I’ll make sure the architecture is up to the task.
;Liam: I'll start the outreach now. We need to build the community around this project. The online forums are already showing a ton of interest.
;Maya: This is it. We’re finally building momentum. Let's keep this pace! This is going to be amazing.
;Evelyn: My goal is for this to be a true platform—a place for people to share their knowledge and collectively advance the field of tuxemon research.
;Julian: We're making history here. We're building something that will change the world.

== Tuxepedia Issues ==

;Liam: We've got a serious problem.
An informant within the Pillars confirmed they're actively spreading rumors that our research will destabilize the tuxemon ecosystem. They see The Tuxepedia as a direct threat to their control.
;Evelyn: We can't let fear-mongering stop us. We’ve come too far to give up now. We need a strategy to counter them.
;Julian: Our strength isn't in a bunker or a centralized server; it's in the community itself. The Tuxepedia is a collective, distributed effort, and that makes it nearly impossible to dismantle.
;Maya: That’s the key. What if they try to insert false information or manipulate data? How can the public trust its accuracy?
;Liam: That's the beauty of it. The moment they try, the eyes of the entire community will be on it. Any falsehoods or inaccuracies they insert will be quickly corrected by the collective body of experts and trainers.
;Evelyn: Exactly. The strength comes from the diversity of our contributors. They'd have to manipulate hundreds of people across the globe—a task they simply don't have the reach or subtlety for.
;Julian: The Pillars are used to taking down single entities. They'll be hard-pressed to sabotage a network of thousands of individuals working together. We're too decentralized to be stopped.
;Maya: I think that's what makes The Tuxepedia so powerful. It's not just a database—it's a living symbol of what people can achieve when they prioritize knowledge over control.
;Liam: They won't stop us. We push forward. Together, we can achieve something amazing.
;Evelyn: We're in this together. And together, we are unstoppable.

== Tuxepedia Launch ==

;Liam: It's finally here. The first version of the Tuxepedia is live! We did it, guys. We actually did it.
;Evelyn: I knew we could! I'm so incredibly proud of us. Now, the real work begins. We need to anticipate their next move—the Pillars won't let this go easily.
;Maya: My heart is pounding! We're changing the landscape of tuxemon research. I’ve heard from researchers all over; the enthusiasm is electric. This is just the beginning.
;Julian: And we're just getting started on the tech side. We've got so many features and data points to add—the possibilities are endless.
;Liam: I've already started sketching out the next version: advanced search features, perhaps integration with other research databases.
;Evelyn: Hold on. Before we sprint to V2, let's take a moment. We need to celebrate this achievement. We've earned it.
;Maya: Champagne is ready! Let’s pop the cork and toast to the Tuxepedia, and to a future where knowledge is free!
;Julian: To the Tuxepedia! May it bring knowledge and power to the people! And may the future of tuxemon research be bright and exciting!
;Liam: Cheers to that! We did it. We actually did it.
;Evelyn: This is only the start. Imagine a world where every single tuxemon trainer has access to this vast repository of knowledge. What happens next is up to them.

== Founders’ Crossroads ==

;Evelyn: We have to start now. Every day we wait, the Pillars deepen their control over the creatures' bonding protocols. Our moral obligation demands action.
;Liam: Moral obligation doesn’t pay for the servers, Ev, and it certainly won't protect our families when the Pillars find out. We’re talking about treason on a corporate scale.
;Maya: Liam has a point. They control the flow of all information. If they discover we’re building a counter-database, they won't just fire us; they’ll erase us.
;Evelyn: And what’s the alternative? To stand by and watch the whole world be convinced that Tuxemon are just programmable products? We have the knowledge to fight them.
;Julian: We need a phased approach. The technology needs to be distributed from day one. If a single central server holds the master data, we're a single hack away from total failure.
;Liam: Distribution mitigates the risk, I grant you. But the goal still needs to be sustainable. We must plan for the worst-case scenario. Are we all ready to lose everything?
;Evelyn: Yes. I'm. This isn't just a project. It's the only ethical path forward. We build it, and we make the knowledge free.
;Maya: I'm in.
;Julian: For the truth.
;Liam: Fine. But if anyone asks, I was working on a totally different, highly secure spreadsheet for Omnichannel. Let's call it the Tuxepedia Idea.

== The Tactical Failure ==

;Major Sterling: The operation failed due to Major Elias's unauthorized attempt to retrieve a downed soldier. The data shows a 14% statistical risk increase caused by that single act of hesitation. Unacceptable.
;Zircon: Human variables, Major. They pollute the metrics. The mission mandate was simple: resource acquisition. Elias prioritized human sentimentality over the objective. A clear case of tactical failure.
;Major Sterling: You cannot eliminate human nature, Zircon. We train our soldiers to have loyalty and courage.
;Zircon: Loyalty is an unreliable metric; it can be diverted by fear or grief. Courage is simply a spike in adrenaline. What I seek is a force that is incapable of deviation—a force whose loyalty is guaranteed by its core programming, not its emotions.
;Major Sterling: You're describing drones, not soldiers.
;Zircon: I'm describing a superior tactical asset. I will find a way to eliminate the soft, inefficient factors of human conscience and replace them with precise, measurable obedience. The Tuxemon provide the perfect substrate.

== The Loyalty Overhaul ==

;Argon: I've completed the neural communication link prototype. We can see a 70% increase in mutual trust metrics when the Tuxemon feel they are being understood. This is a breakthrough for partnership, Elara.
;Dr. Elara: Fascinating data, Argon. However, the directive has changed. We require 100% compliance, not 70% mutual trust. We need to modify the link to prioritize unquestioning obedience from the subject to the handler.
;Argon: That modification would override the creature’s free will! It turns mutual understanding into a dominance protocol. I designed this for communication, not forced servitude.
;Dr. Elara: Compliance protocols are necessary to protect the asset's value and the financial investment, Argon. Your focus on "free will" is academically interesting but commercially irrelevant. Omnichannel cannot risk a consumer product disobeying a direct command.
;Argon: You're fundamentally misunderstanding the organism. Forced obedience will create trauma, not loyalty!
;Dr. Elara: Trauma, like empathy, is simply a data anomaly to be managed. Adjust the code, Argon. The priority is guaranteed compliance—or your research budget is pulled.

== The Price of Emosync ==

;Argon: I just observed Subject Delta exhibiting grief behaviors—genuine, observable distress after the Prototype's termination. This isn't just behavioral code, Elara. This is emergent consciousness.
;Dr. Elara: Consciousness is a subjective, ill-defined variable, Argon. What you observed was a predictable side-effect of the Tuxemon's bonding protocol. The data logs indicate a neural feedback loop consistent with programmed attachment failure.
;Argon: You're reducing sorrow to a feedback loop! We can't just release a generation of beings that are engineered to feel, then treat their pain as a feature. They have no rights, no protection!
;Dr. Elara: Protection is a human concern, not a scientific one. The Emosync feature is a cornerstone of the deluxe model's marketability. It ensures deep trainer engagement. You gave us the mechanism for empathy; Omnichannel simply gave it a price tag.
;Argon: The cost isn't market share; it's ethical debt. This protocol creates a capacity for feeling that we are intentionally leaving vulnerable.
;Dr. Elara: Then rewrite the protocol. Until the data proves otherwise, it is a highly profitable data anomaly. Do not confuse a successful simulation with a moral dilemma.
;Argon: I will not be complicit in weaponizing grief.

== The Cathedral’s Flaw ==

;Architect: The final blueprints are a disaster, Mr. Beaverbrook. The Cathedral's structure cannot support the planned Fusion Core mass when combined with the instability of the dried lakebed foundation. We are violating three international seismic protocols.
;Beaverbrook: Seismic protocols are guidelines for second-tier operations, Architect. We are building a legacy. The land is not "unstable"; it's underutilized. We will simply reinforce the foundation and move on.
;Architect: Reinforcement is not mitigation. The birthing pits are designed to contain chaotic fusion processes. If the core fails, the resulting contamination will leach directly into the regional aquifer. This is a public health catastrophe waiting to happen.
;Beaverbrook: Catastrophe? I prefer to call it maximum density optimization. We are establishing the global flagship campus. Every square meter must generate revenue. The law exists to restrain the uninspired; we are pioneers.
;Architect: My signature will not be on these final plans. I refuse to authorize a structure built on known geological and ethical failure points. My license, and frankly, my conscience, forbids it.
;Beaverbrook: Fine. I'll have one of the junior engineers sign off. Your principles are an inconvenience, nothing more. Keep the retirement package. Just keep your mouth shut about the "Cathedral's flaw".
;Architect: I cannot control the ground, Mr. Beaverbrook. And that ground will remember what you built on top of it.

== The Apex Brand Briefing ==

;Beaverbrook: The footage is catastrophic, Rhodes. The public saw a prototype scream and then incinerate a section of the facility. The narrative is slipping. Fix it.
;Rhodes: Sir, we're working twenty-four/seven on damage control. The keywords are "uncontrolled mutation" and "facility containment failure." We need to shift away from that immediately.
;Beaverbrook: No, we embrace the power. The creature didn't fail; it achieved an unauthorized leap in evolution. We need a brand name that captures that primal, raw power. Call it 'The Apex'.
;Rhodes: 'The Apex' is strong, but how do we justify the casualties? We can't just sweep three operative losses under the rug, sir. The optics are terrible.
;Beaverbrook: We reframe the losses as "investments in groundbreaking research." The public isn't interested in safety; they want to know they own the strongest, most dangerous thing on the market. That creature is our flagship product.
;Rhodes: So, the brand messaging is: "Unbound by Limits. Priced for Supremacy." We turn fear into aspiration. I can work with that, but it's going to cost triple the media buy.
;Beaverbrook: Then triple the media buy. I want 'The Apex' trending on every channel by the end of the fiscal quarter. Controlling the narrative is the most valuable asset we have, Rhodes.

== The Unauthorized Cure ==

;Dr. Lee: The results are undeniable, Dr. Elara. Our combination of enzymes and antibodies successfully neutralizes the Spyder strain without long-term genetic disruption. It’s a complete cure.
;Dr. Elara: I see the metrics, Lee. Highly effective. Highly efficient. And entirely unauthorized.
;Dr. Lee: Unauthorized? This is a public health crisis! Why would we withhold a cure?
;Dr. Elara: The official timeline requires containment and quarantine, not rapid cure. The virus serves a tactical purpose: it destabilizes the region, allowing for coordinated asset acquisition and eliminating unauthorized training competition.
;Dr. Lee: You’re saying the virus is a deliberate conspiracy? And that the quarantine is a cover for a corporate land grab?
;Dr. Elara: I'm saying your cure interferes with the market strategy. Your goal was a vaccine protocol; you provided a solution that undermines the entire operational directive.
;Dr. Lee: My goal was to save lives! If you don't release this data—
;Dr. Elara: You won’t release the data, Lee. You will cease all work, transfer the files, and sign a non-disclosure agreement. Your research budget is officially terminated.
;Dr. Lee: I can’t. This is bigger than Omnichannel. I have to warn Dr. Chen. I need to get this cure out!
;Dr. Elara: I have already contacted security, Dr. Lee. Attempting to share classified research constitutes corporate treason. They will be at your door shortly.

== The Home Office ==

;Protagonist's Mom: I told you, don't touch the server! You know that's my work for Omnichannel! If they find out I'm doing proprietary work here, they'll revoke my consulting license and our family's savings are gone.
;Protagonist: But why is the program called the "Truth Filter"? Every time I search, it seems to block all the critical articles about the Greenwash contamination near the river.
;Protagonist's Mom: It's called quality control, honey. They pay me well to ensure the narrative is stable. It's the only way we can afford this home and your education.
;Protagonist: But Dad always said real progress meant questioning the narrative, not paying someone to sanitize it. We're part of the lie now.
;Protagonist's Mom: Your father was a martyr to his principles, and that's not a luxury we can afford. You need to focus on getting your own Gold Pass and staying safe.
;Protagonist: Safe? I'd rather know the truth than be safely ignorant.
;Protagonist's Mom: You're being dramatic. The Pillars provide order; that's the bottom line.
;Protagonist: And what about the cost of that order?
;Protagonist's Mom: The cost is silence. That's the deal. You need to choose safety over sentiment.
;Protagonist: I don't think Dad would have agreed with that deal.

== Nimrod's Compliance Protocols ==

;Nimrod Boss Tru: The Ignibus prototype has a 99.8% compliance rating, Zircon. That two-tenths of a percent failure rate is a catastrophic liability. It represents a crack in our control.
;Zircon: That failure is the creature's instinctual need for social bonding. It's a biological variable we can't fully suppress without severe neural damage.
;Nimrod Boss Tru: Neural damage is acceptable. Biology is inherently inefficient, and sentiment is a liability. Replace the Empathy Protocol immediately.
;Zircon: But you yourself designed the original Empathy Protocol—you said loyalty based on mutual respect was the strongest.
;Nimrod Boss Tru: That was before Omnichannel clarified the market metrics. We need guaranteed compliance, not mutual respect. The customer must never be disobeyed.
;Zircon: This modification turns the Tuxemon into a tool of dominance. You're removing its free will.
;Nimrod Boss Tru: I'm removing its weakness. We are building the Enforcer corps, not a petting zoo.
;Zircon: And what if this damages the Fusion compatibility?
;Nimrod Boss Tru: The Chrome Robo will handle the Fusion. Your job is to ensure the Ignibus sees disobedience only as a threat.
;Zircon: As you command. But I hope you understand the monster you are creating.

== The Fast-Food Feature (Scoop's Malice) ==

;Scoop Boss Donald: The sales projection for the Quarter-Pounder Pesto is stagnant, Doctor. We need a marketing angle that guarantees high-volume traffic and repeat business.
;Scoop Scientist: We could introduce the Spyder strain via the mass distribution vector—it's easily carried in the food supply without detection.
;Scoop Boss Donald: The Spyder strain? Isn't that the one that causes weakness in Tuxemon?
;Scoop Scientist: Yes. It's a mild, easily curable ailment for humans, but it significantly weakens the subjects’ defense metrics, making official restorative snacks necessary.
;Scoop Boss Donald: "Mild, easily curable." Perfect. We’ll call it the 'Health & Happiness' initiative. It creates instant demand for our high-profit products.
;Scoop Scientist: But the long-term effects on unregistered Tuxemon could be severe, especially without the expensive official vaccine. We can't guarantee safety for those outside the Gold Pass system.
;Scoop Boss Donald: Then they should have bought the Gold Pass. It's an incentive for compliance. The instability is a feature, not a bug.
;Scoop Scientist: This is actively weaponizing a disease for profit, sir. It violates every ethical guideline.
;Scoop Boss Donald: Ethics are an obstacle to market penetration, Doctor. Roll it out globally, starting with the Fondent region.
;Scoop Scientist: As you command, Boss Donald. But the public won't forgive us if this gets out.

== Rock and Fossil ==

;Shaft Boss Zoolander: The geologists are refusing to drill deeper. They say the ancient sedimentary layers are too unstable, and the noise is disrupting the local ecosystem. I need you to address this immediately.
;Old Miner: Madam Zoolander, we signed up to mine iron ore, not to excavate myths! What's with all this talk of "revived power sources" and "dragon remnants"? The men are scared and the ground is shifting.
;Shaft Boss Zoolander: The Cathedral's mandate has shifted. We are no longer focused on simple resources; we are securing biological assets for Greenwash's new program.
;Old Miner: But the fossilized dragon eggs are located in a high-risk zone! You're risking our lives for eggs that belong in a museum!
;Shaft Boss Zoolander: History is less profitable than assets. The eggs are worth far more than any mineral vein we could find.
;Old Miner: The noise is driving the local Tuxemon wild! The safety readings are off the charts! We're on the verge of a catastrophic cave-in.
;Shaft Boss Zoolander: Casualties are an acceptable metric. I have authorized triple hazard pay. That is more than enough compensation.
;Old Miner: Compensation doesn't replace a life, Madam.
;Shaft Boss Zoolander: Get back down there. The Cathedral needs those assets for the Apex project.
;Old Miner: I'll tell the crew. But they won't forget this, and neither will I.

== The Empathy Protocol's Betrayal (Greenwash's Failure) ==

;Argon: Dr. Elara, I've completed the neural communication link prototype. We can see a 70% increase in mutual trust metrics when the Tuxemon feel they are being understood. This is a breakthrough for ethical Partnership.
;Dr. Elara: Fascinating data, Argon. However, the directive has changed. We require 100% compliance, not 70% mutual trust.
;Argon: That modification would override the creature’s free will! It turns mutual understanding into a dominance protocol! I designed this for communication, not forced servitude.
;Dr. Elara: Compliance protocols are necessary to protect the asset's market value and the financial investment, Argon. Your focus on "free will" is commercially irrelevant.
;Argon: But I just observed Subject Delta exhibiting genuine grief after its partner's termination. They feel! We can't just release a generation of beings engineered to feel, then treat their pain as a feature!
;Dr. Elara: The Emosync feature is a cornerstone of the deluxe model's marketability. It ensures deep trainer engagement. You gave us the empathy; we simply gave it a price tag.
;Argon: The cost isn't market share; it's ethical debt. This is wrong.
;Dr. Elara: The board needs results. Adjust the code, Argon. The priority is guaranteed compliance—or your research budget is pulled entirely.
;Argon: And what if I refuse?
;Dr. Elara: Then you become redundant. You know the protocols.

== The Fallout of the Poisoned Sample ==

;Omnichannel CEO Beaverbrook: Elara! Explain this data breach immediately! Looten didn't just resign; he corrupted the Fusion Core metrics and leaked a massive encrypted file to the public network.
;Dr. Elara: He contaminated the secure server, sir. It was an act of ethical sabotage. He felt overwhelming guilt over the creation of the Apex line.
;Omnichannel CEO Beaverbrook: Guilt is a failure of management! Does the public have the complete Fusion Report?
;Dr. Elara: No. It's scrambled—a fragment. But it contains the signature instability data. If anyone can decrypt and complete it, they'll expose the fact that Fusion is fundamentally flawed.
;Omnichannel CEO Beaverbrook: Then we need to control the narrative. We will flood the network with counter-data. We will frame Looten's fragment as a "disinformation hack."
;Dr. Elara: And the person who completes the file? They will have the power to dismantle the entire Cathedral operation.
;Omnichannel CEO Beaverbrook: Then we must find them first. Get Nimrod Boss Tru on the line. We need to deploy the full Enforcer corps to secure any citizen found attempting to decode the data.
;Dr. Elara: That means anyone contributing to the Tuxepedia is a target.
;Omnichannel CEO Beaverbrook: They are not contributors, Elara. They are thieves attempting corporate espionage.
;Dr. Elara: Understood, sir. The hunt for the truth starts now.

== The Tactical Failure's Lesson ==

;Nimrod Boss Tru: Major Elias failed the extraction. The data shows he paused his Sharpfin to retrieve a downed soldier before securing the target asset.
;Zircon: Human variables. They pollute the metrics. Elias prioritized human sentimentality over the objective, causing a 14% statistical risk increase.
;Nimrod Boss Tru: Precisely. Loyalty to a fellow soldier is an unpredictable metric. It can be diverted by fear or grief.
;Zircon: What you seek is a force incapable of deviation—whose loyalty is guaranteed by its core programming, not its emotions.
;Nimrod Boss Tru: I'm describing a superior tactical asset. Elias will be reassigned to desk duty. We need to focus on technology that cannot be reasoned with.
;Zircon: Like the Chrome Robo project?
;Nimrod Boss Tru: Yes. We will find a way to eliminate the soft, inefficient factors of human conscience and replace them with precise, measurable obedience.
;Zircon: The Tuxemon provide the perfect substrate for that experiment.
;Nimrod Boss Tru: They do. And failure is no longer an option.
;Zircon: Understood. Sentiment will be purged from all future assets.

== The Chief Driller's Final Log (Spin-Off based on Zoolander) ==

* File: Log_044_DrillerChief_Final
* Status: Corrupted, Encrypted, 72% Recovered
* Date: Unknown (Approx. Day 8 Post-Drain)
* Source: Foreman's Helmet Recorder (Deep Shaft 3)

;Driller: Shut it down. Shut it all down. Emergency Stop!
;Driller: Beaverbrook's readings are lies. The air down here... it’s not metallic, it’s not sulfur. It's old meat and wet gold. It’s getting thicker. It's in the air, you can chew it. We’re breathing it in, deep.
;Driller: Johnson says his teeth feel loose; he keeps trying to pull them out. Miller says the rock is sighing.
;Driller: And I swear, the shadows behind the support beams are too tall. Too tall for a man, too sharp for a lamp. They just stand there, waiting.
;Driller: Zoolander came down here, and she looked right through one. She's starting to hear it, too.
;Driller: Beaverbrook calls it 'geo-thermal effluvium' and 'pre-eonian mineral dust.' I call it dragon breath.
;Driller: We're not mining a basin; we've walked into its mouth. Those eggs aren't just sleeping; they're dreaming, and their nightmares are leaking out.
;Driller: The whispers... they aren't coming from the mud, and they aren't coming from the eggs. They're coming from inside the steel.
;Driller: They tell you the lake was meant to be there. They tell you that Omnichannel doesn't belong here. They tell you...
;(The Driller gasps.)
;Driller: ...They tell you that it knows what you are.
;(A low, resonant hum begins and intensifies, vibrating the microphone. It sounds like a thousand deep breaths.)
;(A sudden, muffled scream erupts, followed by the sickening sound of heavy metal twisting and falling.)
;Driller: Run! It’s awake! It's not the eggs—it's the Basin! It's trying to think us out of existence!
;(The recording ends with a final, overwhelming burst of static, followed by silence.)

== The Spore Cloud: Rupture and Contamination (Spin-Off based on Zoolander) ==

This scene captures the chaotic moment of the initial breach, where Zoolander's drive for results overrides the Driller's desperate warnings, unleashing a primal, biological terror.

;Driller: Boss, stop the feed! We're past the hard density, but the sensor's reading a pressure surge the hydraulics can't handle. It's not rock—it's elastic. It feels like we're punching through a lung!
;Shaft Boss Zoolander: [Leaning over the comms system, voice tight] Beaverbrook doesn't care about your feelings, Driller. He cares about the target coordinates. Push through the membrane! We're already over budget on this phase!
;Driller: I'm telling you, this isn't normal! I see iridescent residue on the tips! Something's down there, and it's holding itself together!

[The drill screams, then abruptly loses all resistance. A sound like a giant, pressurized egg cracking echoes through the shaft. A viscous, black-and-glowing geyser erupts from the borehole, slamming against the containment shield.]

;Driller: [$#@! It's boiling!] Get back! The air—it's heavy, Boss! I can't breathe! [He collapses, violently scratching at his skin where the vapor has touched him, a crimson welt forming instantly.]
;Shaft Boss Zoolander: [Stumbling backward, shielding his eyes from the noxious mist] What the hell is that stench? It smells like a thousand years of rot and sulfur! Secure the perimeter! Everyone—full biohazard lockdown!
;Driller: [Gasping, his voice hoarse] You told us to push! You did this! It feels like my skin is trying to crawl off my bones!
;Shaft Boss Zoolander: [Eyes wide, staring at the iridescent, pulsing fragments melting the steel shield] No. It's... it's a gas pocket. An unforeseen geological anomaly. That's the only story, Driller. Now you clean up your mess and you keep your mouth shut!

== The First Loss: Unnatural Death and Cover-Up (Spin-Off based on Zoolander) ==

This scene reveals the grisly, non-mining-related death of a worker, providing physical evidence that something alive and predatory has hatched or escaped, and Zoolander's cold suppression of the truth.

;Recovery Tech: [Quietly, with forced professionalism] We found Macready, Boss. He's pinned under the support beam... but the beam didn't do all this.
;Shaft Boss Zoolander: [Walking past the beam, his boots crunching on something brittle] What's the preliminary? Structural failure on the Level 7 access tunnel. Get the photos and log the coordinates.
;Recovery Tech: Sir, look closer. His helmet—it's not dented. It's punctured, like something drove three massive spikes through the composite. And those scrape marks on the rock... they're not from falling debris. They were made by something climbing.

[The Recovery Tech bends down and picks up a large, curved fragment—thick, mother-of-pearl white, and still radiating faint warmth.]

;Recovery Tech: This came out of the mud right next to him. It's like porcelain, but it's organic. What is this, Boss? One of Beaverbrook's secret experiments?
;Shaft Boss Zoolander: [Snatching the fragment and quickly shoving it into a containment bag] It's slag, I said! A new compound created by the thermal stress. You never saw this! Macready died due to negligence of his safety check.
;Recovery Tech: Negligence? He was shredded! His radio was found five meters away with a message playing: "...moving in the shadows... smells like ozone and blood..." This wasn't negligence, Zoolander. This was a kill.
;Shaft Boss Zoolander: [Standing over the Tech, his voice a low, hard threat] The narrative is set: Structural Failure. You log the time of death, you sign the forms, and you forget the slag, the scrapes, and the whispers you hear. Or you join Macready in being buried by the corporate budget. Now get him out of here.

= Xero =

== The Sisterhood Split ==

'''Dialogue Clues:'''
* Misa: "Allie is my sister and means the world to me, so it destroyed me when I found out he had taken her to HQ."
* Misa: "We used to play here all the time when we were younger..."

'''Setting:'''
City Park.

;Allie: Look at it, Misa. The Omnichannel building. So tall, so… orderly. Everything makes sense there. No more chaos, no more fear.
;Misa: Chaos? Allie, that's just life. Tuxemon aren't chaos, they're… raw power. Freedom. That's what Omnichannel fears. They just want to put everything in a neat little box.
;Allie: And what's wrong with neat? What's wrong with safety? Mother worries sick every time a wild Tuxemon is spotted near the market. Imagine if everyone felt safe, if everyone knew their place. Aeble Flisk… he gets it. He’s one of the few who sees the need for order.
;Misa: Fix it? Or control it, Allie? There's a difference. People shouldn't need a corporation to tell them how to live. And Tuxemon… they shouldn't be contained.
;Allie: They just need to be guided. Directed. Imagine the power, Misa. The stability. No more struggling, no more worrying about what's around the next corner. I... I think I want to be a part of that. I want to make things orderly.
;Misa: Allie, don't. Please.
;Allie: It's the future, Misa. You'll see. The Fondent Region deserves structure. Peace through precision.

== The Academy Rivalry ==

'''Dialogue Clues:'''
* Misa: "Kyle is one of my least favorite people at Omnichannel... We were in the same cohort at The Academy and he's been nothing but trouble since."

'''Setting:'''
"The Academy" or school.

;Misa: ...and as you can see, Professor, by adapting these bio-luminescent flora, we can naturally enhance a Tuxemon's innate abilities without invasive modification. It offers a sustainable, ethical pathway to partnership.
;Professor: Excellent work, Misa. Innovative and considerate.
;Kyle: "Considerate," Professor? Or inefficient? While Misa's been carefully nurturing houseplants, my own research—into direct neural stimulation—shows far more immediate and absolute results. Why partner, when you can command?
;Misa: Command? That's not research, Kyle, that's… dominance! We're here to understand Tuxemon, not break them!
;Kyle: Oh, the idealist speaks. Tell me, Misa, when did "understanding" ever win a grant? Omnichannel will want solutions. Fast ones. Power matters more than your gentle theories. And my solutions are undeniably superior. They simply work.
;Misa: At what cost? You're ignoring the inherent risks, the long-term damage!
;Kyle: Details, Misa, mere details. The future is about power, not petals. You’ll never get anywhere clinging to such naive notions. My results speak. Your feelings don’t.

== The Conspiracy of Control ==

'''Dialogue Clues:'''
* Knight: "Two people control Omnichannel. The board is a joke. Allie. Allie is the one they don't want you to know about."

'''Setting:'''
Omnichannel HQ.

;Aeble: The latest broadcast went splendidly, Allie. Kane will be pleased — public approval for the Trial is surging. My face is everywhere, of course. My charming, benevolent face.
;Allie: As always, Aeble. The masses adore you. Your performance as the singular, unwavering leader of the Fondent Region is quite convincing. And the Board? They’re still preoccupied with their reelection campaigns. Just as Kane intended.
;Aeble: You have a particular talent for distracting them, my dear. Their egos are… predictable. But the real work… that falls to Kane. We just keep the stage tidy.
;Allie: Of course. The Tuxemon Professor is proving troublesome… Kane wants him contained, not removed. For now.
;Aeble: Indeed. And the new batch of contestants for the Trial? Any… interesting specimens?
;Allie: One, in particular. Full of potential, and very unaware of the strings being pulled.
;Aeble: Excellent. We are safety, we are order, we are Omnichannel. And with Kane above us… we keep the machine running.

== The City Park Incident ==

'''Dialogue Clues:'''
* Speck: "You imprisoned my family and forced me and my brother to join the Trial."
* Kyle: "I was the one that gave the order to attack... Oh, and Speck? I enjoyed the screams."

'''Setting:'''
Citipark. Omnichannel Grunts tear up flowerbeds. Civilians are being rounded up. Kyle watches from a safe distance.

;Grunt: Sir! We've secured the main square! Minimal resistance, as predicted. The locals are… distressed.
;Kyle: "Distressed," Grant? Such a delicate word for simple panic. Make sure everyone knows exactly who is in charge now. Round up anyone resisting. Confiscate everything. And the families of any known Tuxemon owners? They go straight to detention. No exceptions.
;Speck: Leave them alone! They haven’t done anything! My family!
;Grunt: Get back, kid! This is Omnichannel business!
;Kyle: Oh, look what we have here. Another little hero. You’re from that family with the prize-winning… what was it, a Fruitera? Such a shame. It’s for your own good, boy. We’re bringing order.
;Speck: This isn’t order, this is… tyranny! You’re destroying everything!
;Kyle: Destroying? No, we're cleansing. And honestly, it’s quite satisfying. I particularly enjoy the… vocalizations. They really punctuate the message. Your screams will echo longer than your ideals. Make sure this one is earmarked for "re-education," Grant. He’ll make a fine addition to our future endeavors. After his family is secured, of course.

== The Research Division Rift ==

'''Dialogue Clues:'''
* Cam: "I was fired from the research division because they feared me."
* Kay Wren: "My source of funding has become... hesitant as of late."
* Cam: "Humans and Tuxemon, merged together as one... unless they burn out entirely."

'''Setting:'''
A high-tech research lab (Omnichannel HQ?)

;Cam: You don't see it, do you, Kay?! The potential! We can achieve true symbiosis! Beyond mere partnership, beyond understanding! A complete convergence of wills! Imagine the power!
;Kay Wren: Cam, this isn't symbiosis, it's madness. Subject 7... its neural readings are critical. The burnout is imminent. You're pushing these Tuxemon past their limits, past sanity! And your own psyche is… unstable.
;Cam: They called me unstable. But I see it all so clearly now...
;Cam: Unstable? I'm enlightened! They fear what they don't understand, Kay! The higher-ups are blind! They fear what they can’t control! Tuxemon are a threat, a rampant force of destruction! We must control them entirely! Become one with them! Only then can we truly annihilate the threat!
;Scientist 1: Professor Wren, his last three subjects have all suffered irreversible neural collapse. This merging process is too dangerous!
;Kay Wren: He was brilliant once. I don’t know what happened.
;Kay Wren: Cam, I'm shutting this down. Effective immediately. Your research… it's gone too far. You're losing yourself.
;Cam: Suspended?! You’d suspend me?! Because you’re afraid?! You feeble, insignificant minds! You'll never see the Truth! You'll cling to your outdated notions while the real power… the real solution… passes you

== Cam's Descent into Madness ==

'''Dialogue Clues:'''
* Cam: "I was fired from the research division because they feared me."
* Cam: "Humans and Tuxemon, merged together as one... unless they burn out entirely."
* Cam: "Hahahahaha, and after 30 merges and splits, I gladly pay it!"

'''Setting:'''
A high-tech research lab (Omnichannel HQ?) Cam is strapped into a neural harness, his body twitching with residual energy, veins darkening beneath his skin. His eyes are bloodshot and unfocused, locked on a containment chamber where something is unraveling — a shape flickering, distorting, losing all sense of form.

;Cam: Don’t look away! Don’t you dare! It’s beautiful… the shift… the unraveling! The echo beneath the scream! Feel it? No, you can’t! Your minds are too narrow, too quiet! This is the becoming! The glorious, glorious unbecoming!
;Scientist 1: He’s destabilizing the subject! The brainwave patterns… they’re fragmenting!
;Cam: Fragmented? Oh, but that’s where the truth hides! The tangled, trembling pieces! We reshape them! We rethread them! Like chords on a broken harp! The light dims — snap! And then the hush! So much hush! So much space to fill!
;Scientist 2: It’s… it’s losing cohesion! The structure is dissolving!
;Cam: Yes… yes, dissolve! Let it flow! The shell fades, but the will remains! It reaches! It pulses! It sings in my thoughts! I absorb it! I absorb the fear! I absorb the fury! It becomes my fury! My boundless, eternal fury! They tried to stop me! They said I couldn’t hold them all! But I can! I can! So many voices echo inside me now! More than you could count! And they dance! They dance in my bones! And there’s still room! Always room!
;Scientist 1: He’s completely unhinged! He’s integrating it! This isn’t burnout — it’s fusion!
;Cam: So quiet now… so wonderfully mine. The lesson learned. The truth embraced. I'm the vessel. I'm the echo. I'm the silence between echoes. And soon… soon you will all join the choir within!
;Cam: Hahahahaha! Sing with me! Sing with me! SING WITH ME!

2026-03-02T10:26:10Z

Jaskrendix:

Callie Wren

2026-02-04T08:01:05Z

Jaskrendix:

{{Character
|Trainer Class=Homemaker
|Sources=Qiangong2
|Main Details== Callie Wren: Communication Profile =

== Role ==
The Player's Aunt & Primary Caretaker.

== Relationship (Internal Canon) ==
[[Maple Wren]]'s sister; [[Kay Wren]]'s daughter.

== Speech Style ==
High–Low Contrast. She pivots between "Cringe/Cool Aunt" energy (pop culture jokes, playful slang) and "Urgent Guardian" commands (Wait!, Listen!, Grab me a glass!).

== Tone ==
Vigilant & Defensive. She is hyper-aware of the world's dangers and becomes tense when discussing curfews, alerts, or anything tied to the Wren family. She uses ellipses (...) when forced to reference the past.

== Vocabulary ==
Modern slang to deflect tension, shifting to practical, survival-focused language when the Omnichannel is mentioned.

== Focus ==
Protecting the player, maintaining stability in the house, and avoiding direct discussion of Maple. She refers to “how things were” instead of naming her sister.

== Signature Interaction ==
She dodges emotional questions with humor, but snaps into command mode the moment danger is implied.

== Player Knowledge Constraint ==
She never reveals the deeper Wren family structure. She avoids naming Maple directly and never mentions Kay's true relationship to the player.
}}

Kay Wren

2026-02-04T07:59:37Z

Jaskrendix:

{{Character
|Trainer Class=Professor
|Sources=Qiangong2
|Main Details== Kay Wren (Professor): Communication Profile =

== Relationship (Internal Canon) ==
Father to [[Maple Wren]] and [[Callie Wren]]. This connection is hidden from the player.

== Speech Style ==
Warm, energetic, familiar, and slightly verbose. Uses exclamation points frequently, often addressing the player as if they are a long-lost friend.

== Tone ==
Cheery, Enthusiastic, and Secretive. He presents as a benevolent academic but hints at hidden knowledge and connections (he is arrested shortly after).

== Focus ==
Encouraging the Player, getting them into the Trial, and masking his true intentions/status. He focuses on the practical steps of the Trial while downplaying the dangers.

== Player Knowledge Constraint ==
The player does NOT know he is related to the Wren family. He avoids personal identifiers and redirects any attempts to discuss his past.
}}

Kay Wren

2026-02-04T07:59:00Z

Jaskrendix:

{{Character
|Trainer Class=Professor
|Sources=Qiangong2
|Main Details== Kay Wren (Professor): Communication Profile =

== Relationship (Internal Canon) ==
Father to Maple and Callie. This connection is hidden from the player.

== Speech Style ==
Warm, energetic, familiar, and slightly verbose. Uses exclamation points frequently, often addressing the player as if they are a long-lost friend.

== Tone ==
Cheery, Enthusiastic, and Secretive. He presents as a benevolent academic but hints at hidden knowledge and connections (he is arrested shortly after).

== Focus ==
Encouraging the Player, getting them into the Trial, and masking his true intentions/status. He focuses on the practical steps of the Trial while downplaying the dangers.

== Player Knowledge Constraint ==
The player does NOT know he is related to the Wren family. He avoids personal identifiers and redirects any attempts to discuss his past.
}}

Kay Wren

2026-02-04T07:54:59Z

2026-02-02T15:51:30Z

Jaskrendix:

== Actions ==

=== AccessPCAction ===
Change to PCState.

This action transitions to the PCState, typically used for viewing
player character details or an NPC as if it were a PC.

'''Usage'''
<code>

access_pc <character_slug>

</code>
'''Parameters'''
* <code>character_slug</code>: The slug of the character (NPC) to view in PCState.

=== AddCollisionAction ===
Handles the addition of a collision zone associated with a specific
label.
Optionally, with coordinates provided, it can block a specific tile
within the map.

'''Usage'''
<code>

add_collision <label>[,x][,y]

</code>
'''Parameters'''
* <code>label</code>: The name or identifier of the obstacle.
* <code>x</code>: (Optional) X-coordinate of the specific tile to block.
* <code>y</code>: (Optional) Y-coordinate of the specific tile to block.

=== AddComboAction ===
Registers one or more combos from a YAML string.

'''Usage'''
<code>

add_combo <yaml_data>

</code>
'''Parameters'''
* <code>yaml_file</code>: Name of the YAML file (without extension) located in the mods folder.

=== AddContactsAction ===
Add contact to the app.
npc_slug must have the msgid inside the PO.

'''Usage'''
<code>

add_contacts <character>,<npc_slug>[,relation][,strength],
[,steps][,decay_rate][,decay_threshold]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>npc_slug</code>: slug name (e.g. "npc_maple").
* <code>relation</code>: type of relation
* <code>strength</code>: amount of strength (higher, better), default 50, capped 100
* <code>steps</code>: amount of steps, default character steps
* <code>decay_rate</code>: decay rate of the relationship, default 0.01, capped 1.0
* <code>decay_threshold</code>: threshold of steps after which the decay triggers,
default 500

=== AddHeldItemAction ===
Adds a held item to a specific monster.

'''Usage'''
<code>

add_held_item <variable>,<item>

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id.
* <code>item</code>: Slug of the item (e.g. "potion").

=== AddItemAction ===
Add an item to the specified trainer's inventory.

'''Usage'''
<code>

add_item <item_slug>[,quantity][,npc_slug]

</code>
'''Parameters'''
* <code>item_slug</code>: Item name to look up in the item database.
* <code>quantity</code>: Quantity of the item to add or to reduce. By default it is 1.
* <code>npc_slug</code>: Slug of the trainer that will receive the item. It
defaults to the current player.

=== AddMonsterAction ===
Add a monster to the specified trainer's party if there is room.

'''Usage'''
<code>

add_monster <mon_slug>,<mon_level>[,npc_slug][,exp_mod][,money_mod]

</code>
'''Parameters'''
* <code>mon_slug</code>: Monster slug to look up in the monster database or name variable
where it's stored the mon_slug
* <code>mon_level</code>: Level of the added monster.
* <code>npc_slug</code>: Slug of the trainer that will receive the monster. It
defaults to the current player.
* <code>exp_mod</code>: Experience modifier
* <code>money_mod</code>: Money modifier

=== AddStepTrackerAction ===
Adds a step tracker to a specific character.

'''Usage'''
<code>

add_step_tracker <character>,<tracker_id>,<countdown>[,<milestones>
[,<auto_reset>[,<initial_countdown>]]]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or an NPC slug name (e.g., "npc_maple").
* <code>tracker_id</code>: Unique name for identifying the step tracker.
* <code>countdown</code>: Number of steps before the tracker reaches zero.
* <code>milestones (optional)</code>: Step milestones, separated by : (e.g., "500:250:100").
* <code>auto_reset (optional)</code>: "true" or "false" to enable or disable automatic reset.
Defaults to false.
* <code>initial_countdown (optional)</code>: Full cycle length. Defaults to countdown value.

=== AddTechAction ===
Adds a tech to a specific monster.

'''Usage'''
<code>

add_tech <variable>,<technique>[,power][,potency][,accuracy]

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where the monster UUID is stored.
* <code>technique</code>: Slug of the technique to add (e.g. "bullet").
* <code>power</code>: Optional float (0.0-3.0). Overrides default power.
* <code>potency</code>: Optional float (0.0-1.0). Overrides default potency.
* <code>accuracy</code>: Optional float (0.0-1.0). Overrides default accuracy.

'''Examples'''
* "add_tech monster_id,flamethrower"
* "add_tech monster_id,flamethrower,2.5,0.8,0.95"

=== AddTrackerAction ===
Add tracker.

'''Usage'''
<code>

add_tracker <character>,<location>[,visited]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>location</code>: location name (e.g. "paper_town").
* <code>visited</code>: Optional string flag indicating if the location was visited.
Accepts "true", "1", "yes" for True (case-insensitive).
Defaults to True if omitted.

=== AdjustBillPenaltyAction ===
Applies a penalty to a bill for a character — either interest or late fee.

'''Usage'''
<code>

adjust_bill_penalty <character_slug>,<bill_slug>,<method>

</code>
'''Parameters'''
* <code>character_slug</code>: Slug of the character (e.g. "player", "npc_maple").
* <code>bill_slug</code>: Slug of the bill to modify.
* <code>method</code>: Either "interest" or "fee".

'''Examples'''
* adjust_bill_penalty player,electric_bill,interest
* adjust_bill_penalty npc_maple,rent,fee

=== AFKThresholdAction ===
Add, modify, or remove AFK thresholds.

'''Usage'''
<code>

afk_threshold <action> <level> [duration]

</code>
'''Parameters'''
* <code>action</code>: One of "add", "modify", "remove"
* <code>level</code>: The threshold name (string)
* <code>duration</code>: Required for "add" and "modify" (float, seconds)

=== BoundaryMoveAction ===
Moves the current active boundary by the given delta values.

'''Usage'''
<code>

boundary_move <boundary_name>[,dx:dy]

</code>
'''Parameters'''
* <code>boundary_name</code>: Required. The name to assign to the boundary
* <code>dx</code>: The change in the x-coordinate.
* <code>dy</code>: The change in the y-coordinate.

=== BoundaryResizeAction ===
Resizes the current active boundary.

'''Usage'''
<code>

boundary_resize <boundary_name>[,values]

</code>
'''Parameters'''
* <code>boundary_name</code>: Required. The name to assign to the boundary
(e.g., "safe_zone", "event").
* <code>values</code>: A colon-separated string of integers:
* For rectangle: dx:dy
* For circle: delta

=== BoundarySetAction ===
Sets or replaces the current boundary with a new one, or resets to default
if no parameters are given.

'''Usage'''
<code>

boundary_set <boundary_name>[,shape][,values]

</code>
'''Parameters'''
* <code>boundary_name</code>: Required. The name to assign to the boundary
(e.g., "safe_zone", "event").
* <code>shape</code>: Optional. Either "rectangle" or "circle".
* <code>values</code>: Optional. A colon-separated string of integers:
* For "rectangle": x0:x1:y0:y1
* For "circle": cx:cy:radius

=== BreedingAction ===
Select a monster in the player party filtered by gender and store its
id in a variables (breeding_father or breeding_mother)

'''Usage'''
<code>

breeding <gender>

</code>
'''Parameters'''
* <code>gender</code>: Gender (male or female).

=== CallEventAction ===
Execute the specified event's actions by name.

'''Usage'''
<code>

call_event <event_name>

</code>
'''Parameters'''
* <code>event_name</code>: The name of the event whose actions will be executed.

=== CameraManageAction ===
Adds, removes, or switches/follows a camera in the camera manager.

'''Usage'''
<code>

camera_manage add [name] [npc_slug]
camera_manage remove [name]
camera_manage follow [name] [npc_slug]

</code>
'''Parameters'''
* <code>action</code>: "add", "remove", or "follow"
* <code>camera_name</code>: The identifier for the camera.
* <code>npc_slug</code>: Optional slug of the NPC/entity to follow (used for add/follow).

=== CameraModeAction ===
* <code>Change camera mode</code>: freeroaming or fixed.

'''Usage'''
<code>

camera_mode <mode>

</code>
'''Parameters'''
* <code>mode</code>: The mode of the camera: 'free_roaming' or 'fixed'.

=== CameraMoveAction ===
Smoothly move the camera to a specific coordinate or reset it to its original position.

'''Usage'''
<code>

camera_move <time>,<x>,<y>

</code>
'''Parameters'''
* <code>time</code>: the duration (in seconds) required for the camera to transition to the target position.
* <code>x,y</code>: the coordinates where the camera needs to be centered.

=== CameraPositionAction ===
Move the camera on a coordinate.

'''Usage'''
<code>

camera_position <x>,<y>

</code>
'''Parameters'''
* <code>x,y</code>: the coordinates where the camera needs to be centered.

=== CameraShakeAction ===
Shake the camera with a precise intensity and duration.

'''Usage'''
<code>

camera_shake <intensity>,<duration>

</code>
'''Parameters'''
* <code>intensity</code>: The magnitude of the shake effect. A higher value results
in a more pronounced shake, while a lower value produces
a subtler effect (min 0.0, max 3.0).
* <code>duration</code>: The length of time (in seconds) that the shake effect
should last. The method calculates the number of frames
to shake based on an assumed frame rate.

=== ChangeBgAction ===
Handles the background change within the session, allowing users
to apply a new background color or image dynamically.

'''Usage'''
<code>

change_bg <background>[,image][,category]

</code>
'''Parameters'''
* <code>background</code>: The background identifier, which can be:
* A file name located in `gfx/ui/background/`
* An RGB color formatted as `R:G:B` (e.g., `255:0:0`)
* <code>image</code>: An optional image identifier, which can be:
* An item slug (stored in `gfx/items`)
* A direct file path
* <code>category</code>: The category of the image (e.g., item or image.
If omitted, defaults to "background".

* <code>Notes</code>:
* Background images must be in `gfx/ui/background/`.
* Background dimensions must be 256x144 pixels.

=== ChangeBgNpcAction ===
Displays an NPC sprite over a background image, using the NPC's base
sprite located in ``gfx/sprites/player/<slug>.png``.

'''Usage'''
<code>

change_bg_char <background>,<npc_slug>

</code>
'''Parameters'''
* <code>background</code>:
The background identifier, which must be the name of a file
located in ``gfx/ui/background/`` (without the ``.png``
extension). The background image must match the native
resolution of the game (256x144 pixels).

* <code>npc_slug</code>:
The slug of the NPC to display. A matching sprite file must
* <code>exist at</code>:

``gfx/sprites/player/<npc_slug>.png``

The sprite will be loaded, scaled, and rendered on top of
the background.

* <code>Notes</code>:
* Background images must be located in ``gfx/ui/background/``.
* Background dimensions must be exactly 256x144 pixels.
* NPC sprites are loaded directly from their corresponding PNG
file in ``gfx/sprites/player/``.
* This action always pushes the ``NpcImageState``, which displays
the background and overlays the NPC sprite.

=== ChangeBgMonsterAction ===
Displays a monster sprite over a background image, using the
monster's front sprite extracted from its sprite sheet.

'''Usage'''
<code>

change_bg_monster <background>,<monster_slug>

</code>
'''Parameters'''
* <code>background</code>: The background identifier, which must be the name of
a file located in `gfx/ui/background/` (without the `.png`
extension). The background image must match the native
resolution of the game (256x144 pixels).
* <code>monster_slug</code>: The slug of the monster to display. The monster
must exist in the monster database. Its front sprite will be
extracted from its sprite sheet and rendered on top of the
background.

* <code>Notes</code>:
* Background images must be located in `gfx/ui/background/`.
* Background dimensions must be exactly 256x144 pixels.
* The monster sprite is taken from the monster's sprite sheet
using the `front_rect` defined in its model.
* This action always pushes the `MonsterImageState`, which
displays the background and overlays the monster sprite.

=== ChangeFactionMembershipAction ===
Makes an NPC (or player) join or leave a specific faction.

'''Usage'''
<code>

change_faction_membership <character>,<faction_slug>,<status>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>faction_slug</code>: The slug identifier of the faction whose membership will be changed.
* <code>status</code>: Must be either "join" or "leave", indicating the membership action.

=== ChangeStateAction ===
Change to the specified state (generic).

This action handles state transitions that do not require specific
additional parameters beyond the state name itself.

'''Usage'''
<code>

change_state <state_name>

</code>
'''Parameters'''
* <code>state_name</code>: The state name to switch to.

=== ChangeTasteAction ===
Changes the specified taste (warm or cold) of a monster.

'''Usage'''
<code>

change_taste <variable>,<type_taste>,<new_taste>

</code>
'''Parameters'''
* <code>variable</code>: Name of the game variable containing the monster's UUID.
* <code>type_taste</code>: Either "warm" or "cold" to indicate which taste to change.
* <code>new_taste</code>: Slug of the new taste to assign, or "random" to select a new one
at random (excluding "tasteless" and the current taste).

* <code>Notes</code>:
* When using "random", the new taste is chosen based on rarity_score weighting.
* When specifying a taste slug, it must exist, match the selected type,
and must not be "tasteless".
* If no valid taste is found during random selection, the taste remains unchanged
and a warning is logged.

=== CharFaceAction ===
Make the character face a certain direction.

'''Usage'''
<code>

char_face <character>,<direction>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>direction</code>: Direction to face. It can be: "left", "right", "up", "down",
"player" or a character slug.

=== CharFacePlayerAction ===
Make an NPC face the player when they come within a specified distance.

'''Usage'''
<code>

char_face_player <npc_slug>,<trigger_dist>,<persistent>

</code>
'''Parameters'''
* <code>npc_slug</code>: Slug of the NPC that will face the player.
* <code>trigger_dist</code>: Maximum tile distance at which the NPC will begin
facing the player. Defaults to 3.
* <code>persistent</code>: Whether the NPC should continue tracking the player
after the first trigger. Defaults to True.

=== CharLookAction ===
Make a character look around.

'''Usage'''
<code>

char_look <character>[,frequency][,directions]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>frequency</code>: Frequency of movements. 0 to stop looking. If set to
a different value it will be clipped to the range [0.5, 5].
If not passed the default value is 1.
* <code>directions</code>: the direction the character is going to look, by default
all

eg. char_look character
* <code>eg. char_look character,,right</code>: left

=== CharMoveAction ===
Relative tile movement for characters.

It interprets movement instructions, updates character positions accordingly,
and blocks execution until the destination is reached.

'''Usage'''
<code>

char_move <character>,<move>...

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>move</code>: A sequence of movement instructions in the format:
"<direction> [amount_of_tiles]"
* <code>where</code>:
* direction: One of "up", "down", "left", "right".
* amount_of_tiles (optional): Number of tiles to move (default is 1).
* Multiple moves can be provided, e.g., "up 10, down 5, left 5".

=== CharPatrolAction ===
Enables a character to patrol a predefined route in a continuous loop.

'''Usage'''
<code>

char_patrol <character>,<move>...

</code>
* <code>Parameters</code>:
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>move</code>: A sequence of movement instructions in the format:
"<direction> [amount_of_tiles]"
* <code>where</code>:
* direction: One of "up", "down", "left", "right".
* amount_of_tiles (optional): Number of tiles to move (default is 1).
* Multiple moves can be provided, e.g., "up 10, down 5, left 5".

* <code>Functionality</code>:
* Converts movement instructions into a looping patrol path.
* NPC moves along the predefined path, restarting when completed.
* Blocks execution if the NPC encounters an obstacle.
* Automatically resumes patrol when movement is available.

=== CharPlagueAction ===
Set the entire party as infected or inoculated or healthy.

'''Usage'''
<code>

char_plague <plague_slug>,<condition>[,character]

</code>
'''Parameters'''
* <code>plague_slug</code>: The slug of the plague to target.
* <code>condition</code>: Infected, inoculated, or None (removes the plague from the
character, indicating a healthy state).
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>enforced_check</code>: Optional string flag to enforce eligibility rules.
Accepts "true", "1", or "yes" (case-insensitive).
Default is False (eligibility is bypassed).

=== CharPositionAction ===
Set the position of a character.

'''Usage'''
char_position <character>,<tile_pos_x>,<tile_pos_y>

'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>tile_pos_x</code>: X position to set the character to.
* <code>tile_pos_y</code>: Y position to set the character to.

=== CharRunAction ===
Set the character movement speed to the global run speed.

'''Usage'''
<code>

char_run <character>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").

=== CharSpeedAction ===
Set the character movement speed to a custom value.

'''Usage'''
<code>

char_speed <character>,<speed>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>speed</code>: Speed amount.

=== CharStopAction ===
Make the character stop moving.

'''Usage'''
<code>

char_stop <character>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").

=== CharTalkAction ===
Displays dialogue for a character based on context and location.

This action retrieves dialogue from the character's dialogue profile,
optionally using a location-specific override. The dialogue field determines
which type of line to display (e.g. greeting, pre_battle, farewell).

'''Usage'''
<code>

char_talk <character>,<field>[,location]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or the slug of an NPC (e.g. "npc_maple").
* <code>field</code>: The dialogue type to display. Must be one of:
* greeting
* idle
* farewell
* pre_battle
* post_battle_win
* post_battle_lose
* post_battle_draw
* <code>location</code>: Optional map identifier (e.g. "map.tmx") used to override default dialogue.

* <code>Behavior</code>:
* If a location is provided and a location-based override exists, it will be used.
* Otherwise, the default dialogue profile is used.
* If the dialogue field contains multiple lines, one is selected randomly.
* Dialogue text is formatted before display.

* <code>Example</code>:
char_talk npc_maple,greeting,map_forest

=== CharWalkAction ===
Set the character movement speed to the global walk speed.

'''Usage'''
<code>

char_walk <character>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").

=== CharWanderAction ===
Make a character wander around the map.

'''Usage'''
<code>

char_wander <character>[,frequency][,t_bound][,b_bound]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>frequency</code>: Frequency of movements. 0 to stop wandering. If set to
a different value it will be clipped to the range [0.5, 5].
If not passed the default value is 1.
* <code>t_bound</code>: coordinates top_bound vertex (eg 5,7)
* <code>b_bound</code>: coordinates bottom_bound vertex (eg 7,9)

eg. char_wander character,,5,7,7,9

=== ChoiceItemAction ===
Ask the player to make a choice among items.

'''Usage'''
<code>

choice_item <choices>,<variable>

</code>
'''Parameters'''
* <code>choices</code>: List of possible choices
* <code>(item slugs eg</code>: potion:tea),
* <code>separated by a colon "</code>: ".
* <code>variable</code>: Variable to store the result of the choice.

=== ChoiceMonsterAction ===
Ask the player to make a choice among monsters.

'''Usage'''
<code>

choice_monster <choices>,<variable>

</code>
'''Parameters'''
* <code>choices</code>: List of possible choices
* <code>(monster slugs eg</code>: rockitten:apeoro),
* <code>separated by a colon "</code>: ".
* <code>variable</code>: Variable to store the result of the choice.

=== ChoiceNpcAction ===
Ask the player to make a choice among NPCs.

'''Usage'''
<code>

choice_npc <choices>,<variable>

</code>
'''Parameters'''
* <code>choices</code>: List of possible choices
* <code>(item slugs eg</code>: maple:billie),
* <code>separated by a colon "</code>: ".
* <code>variable</code>: Variable to store the result of the choice.

=== CipherDialogAction ===
Displays a dialog window with text that may be ciphered based on the character's
unlocked letters and the active CipherProcessor.

The dialog text is optionally translated, styled, and formatted based on script
parameters. Any unlocked letters will remain visible, while the remaining content
may be obfuscated depending on the cipher configuration.

'''Usage'''
<code>

cipher_dialog <text>[,avatar][,position][,style]

</code>
'''Parameters'''
* <code>text</code>: Text of the dialog.
* <code>avatar</code>: Monster avatar. If it is a number, the monster is the
corresponding monster slot in the player's party.
If it is a string, we're referring to a monster by name.
* <code>position</code>: Position of the dialog box. Can be 'top', 'bottom', 'center',
'topleft', 'topright', 'bottomleft', 'bottomright', 'right', 'left'.
Default 'bottom'.
* <code>h_alignment</code>: Alignment of text in the dialog box, it can be 'left', 'center'
or 'right'. Default 'left'.
* <code>v_alignment</code>: Alignment of text in the dialog box, it can be 'bottom',
'center' or 'top'. Default 'top'.
* <code>style</code>: a predefined style in db/dialogue/dialogue.json

=== ClearKennelAction ===
Clear a kennel.

It advisable to save the game and check twice.

Remember the main kennel is "Kennel"

Without destination (transfer) the monster will
be deleted as well as the kennel.

'''Usage'''
<code>

clear_kennel <character>,<kennel>[,transfer]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>kennel</code>: The kennel to clear.
* <code>transfer</code>: The kennel to transfer the monsters.

=== ClearTuxepediaAction ===
Clear the key and value in the Tuxepedia dictionary. If the
monster_slug parameter is missing, this action will completely
reset the Tuxepedia dictionary by removing all seen monsters.

If the monster_slug parameter is provided, this action will remove
the specified monster from the Tuxepedia dictionary.

'''Usage'''
<code>

clear_tuxepedia <monster_slug>

</code>
'''Parameters'''
* <code>monster_slug</code>: Monster slug name (e.g. "rockitten").

=== ClearVariableAction ===
Removes specified variables from the player's stored variables.

'''Usage'''
<code>

clear_variable <variable1>[,variable2]

</code>
'''Parameters'''
* <code>variable</code>: One or more variables to be removed.

=== CopyVariableAction ===
Copy the value of var2 into var1 (e.g. var1 = var 2).

'''Usage'''
<code>

copy_variable <var1>,<var2>

</code>
'''Parameters'''
* <code>var1</code>: The variable to copy to.
* <code>var2</code>: The variable to copy from.

=== CraftingStationAction ===
Change to the specified state.

'''Usage'''
<code>

crafting_station <character_slug>,<method>[,file_yaml]

</code>
'''Parameters'''
* <code>character_slug</code>: The slug of the character (NPC).
* <code>method</code>: Suggests how the recipe is executed, e.g., cooking, forging.
* <code>file_yaml</code>: The YAML file (like `recipe.yaml`) that contains the recipe
definitions to load into the system (mods folder).

=== CreateKennelAction ===
Creates a new kennel with optional metadata.

It's advisable to create a msgid in the en_US PO file.

msgid "kennel_name"
msgstr "Kennel Name"

'''Usage'''
<code>

# Create a visible kennel with default capacity
create_kennel player,my_kennel

# Create a hidden kennel with capacity 20
create_kennel player,my_kennel,true,20

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>kennel</code>: Name of the kennel.
* <code>hidden</code>: Optional flag ("true"/"false", "1"/"0", "yes"/"no") for
visibility.
* <code>max_capacity</code>: Optional integer for maximum capacity (defaults to
MAX_KENNEL).

=== CreateNpcAction ===
Create an NPC object and adds it to the game's current list of NPC's.

'''Usage'''
<code>

create_npc <npc_slug>,<tile_pos_x>,<tile_pos_y>[,<behavior>]

</code>
'''Parameters'''
* <code>npc_slug</code>: NPC slug to look up in the NPC database.
* <code>tile_pos_x</code>: X position to place the NPC on.
* <code>tile_pos_y</code>: Y position to place the NPC on.
* <code>behavior</code>: Behavior of the NPC (e.g. "wander"). Unused for now.

=== DojoMethodAction ===
Represents an event action for the monks in the Dojo (Spyder).

'''Usage'''

<code>

dojo_method <variable_name>,<option>

</code>
'''Parameters'''

* <code>variable_name</code>:
The name of the variable where the monster ID will be stored.

* <code>option</code>:
* <code>The action to perform. Can be either</code>:

* "technique": Learn any move the monster hasn't acquired from its base
moveset, without restrictions based on level or evolution stage.
* "monster": Devolve the monster.

=== EvolutionAction ===
Checks, asks and evolves.

'''Usage'''
<code>

evolution <character>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>variable</code>: Name of the variable where to store the monster id. If no
variable is specified, all monsters get experience.
* <code>evolution</code>: Slug of the evolution.

=== FadeInAction ===
Fade in and block until the fade duration has completed.

'''Usage'''
<code>

fade_in [trans_time][,rgb]

</code>
'''Parameters'''
* <code>trans_time</code>: Transition time in seconds - default 0.3
* <code>rgb</code>: color (eg red > 255,0,0 > 255:0:0) - default rgb(0,0,0)

* <code>eg</code>: "fade_in 3"
* <code>eg</code>: "fade_in 3,255:0:0:50" (red)

=== FadeOutAction ===
Fade out and block until the fade duration has completed.

'''Usage'''
<code>

fade_out [trans_time][,rgb]

</code>
'''Parameters'''
* <code>trans_time</code>: Transition time in seconds - default 0.3
* <code>rgb</code>: color (eg red > 255,0,0 > 255:0:0) - default rgb(0,0,0)

* <code>eg</code>: "fade_out 3"
* <code>eg</code>: "fade_out 3,255:0:0:50" (red)

=== FadeoutMusicAction ===
Fade out the music over a set amount of time in milliseconds.

'''Usage'''
<code>

fadeout_music [duration]

</code>
'''Parameters'''
* <code>duration</code>: Number of milliseconds to fade out the music over.

=== FormatVariableAction ===
Format the value of a variable from the game (eg. float or int).
By default the game variable is a dict[str, Any].

'''Usage'''
<code>

format_variable <variable>,<type_format>

</code>
'''Parameters'''
* <code>variable</code>: The variable to format.
* <code>type_format</code>: Kind of format (float or int).

eg. "format_variable name_variable,int"

=== GetPartyMonsterAction ===
Saves all the iids (party) in variables.

'''Usage'''
<code>

get_party_monster [npc_slug]

</code>
'''Parameters'''
* <code>npc_slug</code>: npc slug name (e.g. "npc_maple") - default "player"

=== GetPendingMovesAction ===
Display a menu of pending techniques for monsters listed in
event_data["check_max_tech"], and store the selected technique ID
in a game variable.

'''Usage'''
<code>

get_pending_moves <variable_name>

</code>
'''Parameters'''
* <code>variable_name</code>: Name of the game variable to store the selected
technique ID.

* <code>Example</code>:
* "get_pending_moves chosen_move"

=== GetPlayerMonsterAction ===
Select a monster in the player party and store its id in a variable.
* <code>It allows filtering</code>: slug, gender, evolution_stage, element, shape,
taste_warm, taste_cold, level, weight, height, max_hp, current_hp,
armour, dodge, melee, ranged and speed.

eg "get_player_monster name_variable,shape,serpent"
eg "get_player_monster name_variable,shape,serpent"

* <code>For the definition</code>: level, weight, height, max_hp, current_hp, armour, dodge,
melee, ranged and speed (all numeric values) is necessary to use a numeric
comparison operator. Accepted values are "less_than", "less_or_equal",
"greater_than", "greater_or_equal", "equals" and "not_equals".

eg "get_player_monster name_variable,speed,more_than,50"
eg "get_player_monster name_variable,level,less_than,15"

* <code>Note</code>:
let's say a player doesn't has no options, then the variable
* <code>will result as</code>: name_variable:no_option
let's say a player has options, but clicks return, then the
* <code>variable will result as</code>: name_variable:no_choice

'''Usage'''
<code>

get_player_monster <variable_name>,<filter_name>,<value_name>[,extra]

</code>
'''Parameters'''
* <code>variable_name</code>: Name of the variable where to store the monster id.
filter
* <code>filter_name</code>: the name of the first filter
* <code>value_name</code>: the actual value to filter
* <code>extra</code>: used to filter more

=== GiveExperienceAction ===
Gives experience points to the monster.

'''Usage'''
<code>

give_experience <variable>,<exp>

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id. If no
variable is specified, all monsters get experience.
* <code>exp</code>: Name of the variable where to store the experience points or
directly the number of points. Negative value will result in 0.

eg. "give_experience name_variable,steps_variable"
eg. "give_experience name_variable,420"

=== InfoAction ===
Records monster's attribute values inside a game variable.
It allows recording the monster's owner attribute values too.

'''Usage'''

<code>

info <variable>,<attribute>

</code>
'''Parameters'''

* <code>variable</code>:
Name of the variable where to store the monster id.

* <code>attribute</code>:
The attribute to check (level, speed, etc.)

'''Examples'''

* "info name_variable,level"
* -> if the monster is lv 4, then it'll create a variable called:
* <code>"info_level</code>: 4"

* "info name_variable,owner_steps"
* -> if the owner walked 69 steps, then it'll create a variable called:
* <code>"info_owner_steps</code>: 69"

=== InputLoadAction ===
Load a recording from a file into memory under a given name.

'''Usage'''
<code>

input_load <filepath> <name>
</code>

=== InputPlaybackAction ===
Start or stop playback of a named recording.

'''Usage'''
<code>

input_playback <action> <name>
</code>

=== InputRecordAction ===
Start or stop input recording, optionally naming the recording.

'''Usage'''
<code>

input_record <action> [name]
</code>

=== InputSaveAction ===
Save a named recording to a file.

'''Usage'''
<code>

input_save <filepath> [name]
</code>

=== InputVariableAction ===
Set a code and check if it's correct or not.
The player's output will be by default lowercase.

'''Usage'''

<code>

input_variable <variable>,<question>[,answer][,escape]

</code>
'''Parameters'''

* <code>question</code>:
The question the player needs to reply (e.g. "access_code").
* <code>Then you create the msgid "access_code" inside the PO file</code>:

msgid "access_code"
msgstr "Here the actual question?"

* <code>variable</code>:
Name of the variable where to store the output.

* <code>escape</code>:
Optional string flag ("true", "1", "yes" for True),
defaults to False when omitted.

'''Examples'''

* "input_variable access_code,response_question"
* "input_variable access_code,response_question,escape"

* -> "is variable_set response_question:whatswrittenbytheplayer"
* -> "not variable_set response_question:whatswrittenbytheplayer"

=== LearnTechByMethodAction ===
Teaches a technique to a specific monster using a specific learning method.

'''Usage'''
<code>

learn_tech_by_method <monster_var>,<technique>,<method>

</code>
* <code>Parameters</code>:
* <code>monster_var</code>: Game variable name containing the monster UUID.
* <code>technique</code>: Slug of the technique to learn.
* <code>method</code>: Learning method enum name (e.g. "EVENT", "TM")

'''Examples'''
* "learn_tech_by_method monster_id,flamethrower,EVENT"
* "learn_tech_by_method monster_id,fireblast,TM"

=== LoadGameAction ===
Loads the game.

If the index parameter is absent, then it'll load
slot4.save

index = 0 > slot 1
index = 1 > slot 2
index = 2 > slot 3

'''Usage'''
<code>

load_game [index]

</code>
'''Parameters'''
* <code>index</code>: Selected index.

* <code>eg</code>: "load_game" (slot4.save)
* <code>eg</code>: "load_game 1"

=== LoadWeatherAction ===
Loads a YAML file containing weather previsions using the Pydantic schema
and registers it with the WorldWeatherManager.

'''Usage'''
<code>

load_weather <path_to_yaml_file>

</code>
'''Parameters'''
* <code>model_file</code>: Path to the YAML file (e.g., "weather_previsions.yml").

=== LoadYamlAction ===
Loads the yaml file. It must be in the maps folder.

'''Usage'''
<code>

load_yaml file

</code>
'''Parameters'''
* <code>file</code>: File to load.

* <code>eg</code>: "load_yaml file_yaml"

=== LockControlsAction ===
Lock player controls

'''Usage'''
<code>

lock_controls
</code>

=== ManageMapCacheAction ===
Adds or removes a map from the cache.

'''Usage'''
<code>

manage_map_cache <action>,<map_name>

</code>
'''Parameters'''
* <code>action</code>: "add" or "remove"
* <code>map_name</code>: Name of the map (map.tmx)

=== MenuAction ===
Toggle visibility of one or more world menu entries, or apply a preset.

'''Usage'''
<code>

menu <flag>[,menu_1:menu_2:...] # toggles specific menus
menu <preset> # applies preset config

</code>
* <code>Parameters</code>:
* <code>flag</code>: "enable" or "disable", applied to specified menus (or all)
* <code>preset</code>: one of defined presets ("minimal", etc.)

'''Examples'''
* menu reset > clears all menu flags
* menu enable > enables all menus
* <code>menu disable,menu_bag</code>: menu_player > disables specified menus
* menu enable,all > enables all menus
* menu minimal > applies "minimal" preset

=== ModifyBillAction ===
Add or remove an amount of money from a bill (slug).

'''Usage'''
<code>

modify_bill <slug>,<bill_slug>,[amount][,variable]

</code>
'''Parameters'''
* <code>slug</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>bill_slug</code>: Slug of the bill.
* <code>amount</code>: Amount of money to add/remove (-/+)
* <code>variable</code>: Name of the variable where to store the amount.

eg. "modify_bill player,bill_slug,-50"
eg. "modify_bill player,bill_slug,,name_variable"

=== ModifyCharAttributeAction ===
Modify the given attribute of the character by modifier.

By default this is achieved via addition, but prepending a '%' will cause
it to be multiplied by the attribute.

'''Usage'''
<code>

modify_char_attribute <character>,<attribute>,<value>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>attribute</code>: Name of the attribute to modify.
* <code>value</code>: Value of the attribute modifier.

=== ModifyContactsAction ===
Modify contact relationship.

'''Usage'''
<code>

modify_contacts <character>,<npc_slug>,<attribute>,<value>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>npc_slug</code>: slug name (e.g. "npc_maple").
* <code>attribute</code>: it can be 'strength', 'decay_rate' or 'decay_threshold'
* <code>value</code>: the new value

=== ModifyFactionReputationAction ===
Modifies an NPC's (or player's) reputation with a specific faction.

'''Usage'''
<code>

modify_faction_reputation <character>,<faction_slug>,<amount>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>faction_slug</code>: The slug identifier of the faction to modify reputation for.
* <code>amount</code>: A string representation of an integer. Positive or negative values
(e.g. "25", "-50") that change the reputation score accordingly.

=== ModifyMoneyAction ===
Add or remove an amount of money for a wallet (slug).

'''Usage'''
<code>

modify_money <slug>,[amount][,variable]

</code>
'''Parameters'''
* <code>slug</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>amount</code>: Amount of money to add/remove (-/+)
* <code>variable</code>: Name of the variable where to store the amount.

eg. "modify_money player,-50"
eg. "modify_money player,,name_variable"

=== ModifyMonsterBondAction ===
Change the bond of a monster in the current player's party.

'''Usage'''
<code>

modify_monster_bond [variable][,amount]

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id. If no
variable is specified, all monsters are touched.
* <code>amount</code>: An int or float value, if no amount, then default 1 (int).
* <code>lower_bound</code>: Lower bound of range to return an integer between (inclusive)
* <code>upper_bound</code>: Upper bound of range to return an integer between (inclusive)

eg. "modify_monster_bond"
eg. "modify_monster_bond name_variable,25"
eg. "modify_monster_bond name_variable,-0.5"
eg. "modify_monster_bond name_variable,,1,5" (random between 1 and 5)
eg. "modify_monster_bond name_variable,,-5,-1" (random between -5 and -1)

=== ModifyMonsterHealthAction ===
Modify the hp of a monster in the current player's party.

'''Usage'''
<code>

modify_monster_health [variable][,health]

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id. If no
variable is specified, all monsters are healed.
* <code>health</code>: A float value between 0 and 1, which is the percent of max
hp to be restored to. A int value, which is the number of HP
to be restored to. If no health is specified, the hp is maxed
out.

=== ModifyMonsterStatsAction ===
Change the stats of a monster in the current player's party.

'''Usage'''
<code>

modify_monster_stats [variable][,stat][,amount]

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id. If no
variable is specified, all monsters are touched.
* <code>stat</code>: A stat among armour, dodge, hp, melee, speed and ranged. If no
stat, then all the stats.
* <code>amount</code>: A/an float/int value, if no amount, then default 1 (+).
* <code>lower_bound</code>: Lower bound of range to return an integer between (inclusive)
* <code>upper_bound</code>: Upper bound of range to return an integer between (inclusive)

eg. "modify_monster_stats"
eg. "modify_monster_stats ,,0.25"
eg. "modify_monster_stats name_variable,speed,25"
eg. "modify_monster_stats name_variable,dodge,-12"
eg. "modify_monster_stats name_variable,dodge,-0.4"
eg. "modify_monster_stats name_variable,,,1,5" (random between 1 and 5)

=== OpenJournalAction ===
Change to JournalInfoState.

This action transitions to the JournalInfoState, displaying information
about a specific monster in the player's journal.

'''Usage'''
<code>

open_journal <monster_slug>

</code>
'''Parameters'''
* <code>monster_slug</code>: The slug of the monster to display in the journal.

=== OpenShopAction ===
Opens a shop interface between the player and a target NPC.

'''Usage'''
open_shop <npc_slug>,<menu>[,model]

* <code>Parameters</code>:
* <code>npc_slug</code>: Either "player" or the NPC slug identifier (e.g. "npc_maple").
* <code>menu</code>: Type of shop interaction to open. Must be one of:
* "buy_item"
* "sell_item"
* "both_item"
* "buy_monster"
* "sell_monster"
* "both_monster"
* "train_monster"
* "heal_monster"
* <code>model (optional)</code>: A configuration profile name used to load custom shop behavior.

* <code>Notes</code>:
* The target NPC must have an economy assigned.
* If menu is "both_*", a choice dialog is shown for selection.

=== OverwriteTechAction ===
Replaces a known technique with another for a specific monster.

This action is typically used when a monster chooses to forget a move
and learn a new one.

'''Usage'''
<code>

overwrite_tech <removed>,<added>

</code>
'''Parameters'''
* <code>removed</code>: Name of the game variable that stores the UUID of the
technique to be replaced.
* <code>added</code>: Slug of the technique to be added (e.g., "peck", "fireball")

* <code>Example</code>:
"overwrite_tech name_variable,peck"

=== ParkExperienceAction ===
Shows the results of the Park session.

'''Usage'''
<code>

park_experience

</code>
'''Parameters'''
* <code>option</code>: Either 'start' or 'stop'

=== PathfindAction ===
Pathfind the player / npc to the given location.

This action blocks until the destination is reached.

'''Usage'''
<code>

pathfind <npc_slug>

</code>
'''Parameters'''
* <code>npc_slug</code>: Either "player" or npc slug name (e.g. "npc_maple").

=== PathfindToCharAction ===
Handles pathfinding movement where one entity navigates toward another
with configurable direction and distance.

'''Usage'''
<code>

pathfind_to_char <target_entity>,<moving_entity>,
[direction],[distance]

</code>
'''Parameters'''
* <code>target_entity</code>: The target entity being approached
(e.g. "character_maple").
* <code>moving_entity</code>: The entity that will move toward the target
(e.g. "character_jimmy").
* <code>direction</code>: Determines approach direction
(up, down, left, or right).
* <code>distance</code>: Number of tiles to maintain from the player
(e.g. 2,3,4).

=== PauseMusicAction ===
Pause the current music playback.

'''Usage'''
<code>

pause_music
</code>

=== PlayMapAnimationAction ===
Trigger a map animation at a specified position based on the character's
coordinates within the world map

'''Usage'''
<code>

play_map_animation <animation_name>,<duration>,<loop>,<character>

</code>
'''Parameters'''
* <code>animation_name</code>: The name of the animation stored in the
resources/animations/tileset directory. For example, an animation
named "grass" will load frames named "grass_xx.png".
* <code>frame_duration</code>: Duration (in seconds) for each frame of the animation.
* <code>loop_mode</code>: Indicates whether the animation should loop. Options: "loop"
or "noloop".
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").

=== PlayMusicAction ===
Play a music file from "resources/music/".

'''Usage'''
<code>

play_music <filename>[,volume][,loop][,fade_ms]

</code>
'''Parameters'''
* <code>filename</code>: The name of the music file to play.
* <code>volume</code>: A value between 0.0 and 1.0 that adjusts the music
volume.
* <code>loop</code>: The number of times to loop the music. Default is to loop
forever.
* <code>fade_ms</code>: The time in milliseconds to fade in the music before
reaching maximum volume.

* <code>Note</code>:
The volume will be based on the main value in the options menu.
e.g. if you set volume = 0.5 here, but the player has 0.5 among
its options, then it'll result into 0.25 (0.5*0.5)

=== PlaySoundAction ===
Plays a short sound effect from the "resources/sounds/" folder.

'''Usage'''
<code>

play_sound <filename>[,volume]

</code>
'''Parameters'''
* <code>filename</code>: The sound file to load (must exist in the sounds database).
* <code>volume</code>: A float between 0.0 and 1.0 representing the relative volume level.
This value is multiplied by the user's configured sound volume.

* <code>Example</code>:
If volume=0.5 and the player's sound setting is also 0.5,
the resulting effective playback volume will be 0.25.

* <code>Note</code>:
This is intended for short non-looping sound effects (e.g., cues, UI feedback),
not for ambient or background music.

=== PlayTileAnimationAction ===
Trigger a map animation at a specified tile position on the world map.

'''Usage'''
<code>

play_tile_animation <tile_pos_x>,<tile_pos_y>,<animation_name>,<duration>,<loop>

</code>
'''Parameters'''
* <code>tile_pos_x, tile_pos_y</code>: Coordinates (x, y) specifying the tile position
where the animation will be drawn on the map.
* <code>animation_name</code>: The name of the animation stored in the
resources/animations/tileset directory. For example, an animation
named "grass" will load frames named "grass_xx.png".
* <code>frame_duration</code>: Duration (in seconds) for each frame of the animation.
* <code>loop_mode</code>: Indicates whether the animation should loop. Options: "loop"
or "noloop".

=== PrintAction ===
Print the current value of one or more game variables to the console.

If no variable is specified, print out values of all game variables.

'''Usage'''
<code>

print
print <variables>

Script parameters:
variables: Optional, prints out the value of this/these variable/s,
multiple variables separated by ':'.
</code>

=== QuarantineAction ===
Quarantine or release monsters infected with a specific plague.

* <code>Usage</code>:
quarantine <character>,<plague_slug>,<value>[,amount]

* <code>Parameters</code>:
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>plague_slug</code>: The slug of the plague to target.
* <code>action_type</code>: "in" to quarantine infected monsters, "out" to release them.
* <code>amount</code>: (Optional, only for "out") The number of monsters to release
randomly.

* <code>Example</code>: "quarantine out,5" (Release 5 infected monsters randomly)

=== QuitAction ===
Completely quit the game.

'''Usage'''
<code>

quit
</code>

=== QuitWorldAction ===
Exit the current world without quitting the game.

'''Usage'''
<code>

quit_world
</code>

=== RandomBattleAction ===
Starts a random battle with a randomly chosen NPC and a party of randomly
generated monsters within a specified level range.

'''Usage'''
<code>

random_battle nr_txmns,min_level,max_level

</code>
'''Parameters'''
* <code>nr_txmns</code>: The number of Tuxemon in the opponent's party (1 to 6).
* <code>min_level</code>: The minimum level for the opponent's monsters.
* <code>max_level</code>: The maximum level for the opponent's monsters.

=== RandomEncounterAction ===
Randomly start an encounter.

Randomly starts a battle with a monster defined in the "encounter" table
in the "monster.db" database. The chance that this will start a battle
depends on the "encounter_rate" specified in the database. The
"encounter_rate" number is the chance
walking in to this tile will trigger a battle out of 100.
"total_prob" is an optional override which scales the probabilities so
that the sum is equal to "total_prob".

'''Usage'''
<code>

random_encounter <encounter_slug>[,total_prob][,rgb]

</code>
'''Parameters'''
* <code>encounter_slug</code>: Slug of the encounter list.
* <code>total_prob</code>: Total sum of the probabilities.
* <code>rgb</code>: color (eg red > 255,0,0 > 255:0:0) - default rgb(255,255,255)

=== RandomHordeAction ===
Randomly start an horde.

Randomly starts a battle with a monster defined in the "encounter" table
in the "monster.db" database. The chance that this will start a battle
depends on the "encounter_rate" specified in the database. The
"encounter_rate" number is the chance
walking in to this tile will trigger a battle out of 100.

'''Usage'''
<code>

random_horde <encounter_slug>[,rgb]

</code>
'''Parameters'''
* <code>encounter_slug</code>: Slug of the encounter list.
* <code>total_prob</code>: Optional float between 0 and 100 representing the chance
of triggering a horde encounter.
* <code>rgb</code>: color (eg red > 255,0,0 > 255:0:0) - default rgb(255,255,255)

=== RandomIntegerAction ===
Randomly chooses an integer between two numbers (inclusive) and sets a key in
the player's game_variables dictionary to this value.

For example, 'random_integer xyz,1,6' will set the value of the game variable
'xyz' to be a random integer from 1, 2, 3, 4, 5, or 6.

'''Usage'''
<code>

random_integer <variable>,<lower_bound>,<upper_bound>

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable to set.
* <code>lower_bound</code>: The inclusive lower bound of the integer range.
* <code>upper_bound</code>: The inclusive upper bound of the integer range.

=== RandomItemAction ===
Picks a random item from a list and adds it to the trainer's inventory.

'''Usage'''
<code>

random_item <item_slugs>[,quantity][,trainer_slug]

</code>
'''Parameters'''
* <code>item_slugs</code>: A colon-separated string of item names to choose from.
* <code>Example</code>: 'potion:super-potion:hyper-potion'.
* <code>quantity</code>: The number of the item to add. Defaults to 1.
* <code>trainer_slug</code>: The slug of the trainer to receive the item.
Defaults to the current player.

=== RandomMonsterAction ===
Adds a random monster to the specified trainer's party, if there is room.

'''Usage'''
<code>

random_monster <level>[,npc_slug][,exp][,mon][,shape][,evo]

</code>
'''Parameters'''
* <code>level</code>: The level of the added monster.
* <code>npc_slug</code>: The slug of the trainer to receive the monster
Defaults to the current player.
* <code>exp</code>: A modifier for the monster's experience.
* <code>mon</code>: A modifier for the monster's money yield.
* <code>shape</code>: The monster's shape (e.g., 'varmint', 'brute').
* <code>evo</code>: The monster's evolution stage (e.g., 'basic', 'stage1').

=== RemoveCollisionAction ===
Removes a collision zone associated with a specific label from the
world map.

'''Usage'''
<code>

remove_collision <label>

</code>
'''Parameters'''
* <code>label</code>: The name or identifier of the obstacle to be removed.

=== RemoveComboAction ===
Removes a registered combo sequence from the ComboDetector.

'''Usage'''
<code>

remove_combo <combo_name>[,buttons]

</code>
'''Parameters'''
* <code>combo_name</code>: Required. A name or ID for the combo (used for logging).
* <code>buttons</code>: Required. A colon-separated list of button names (e.g. LEFT:RIGHT:A).

=== RemoveContactsAction ===
Remove contact from the app.

'''Usage'''
<code>

remove_contacts <character>,<slug>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>slug</code>: slug name (e.g. "npc_maple").

=== RemoveFlairAction ===
Remove a flair from a monster.

'''Usage'''
<code>

remove_flair <variable>,<category>

</code>
'''Parameters'''
* <code>variable</code>: The name of the variable that holds the monster's UUID.
* <code>category</code>: The category of the flair to remove. If omitted, all flairs will be removed.

=== RemoveHeldItemAction ===
Removes a held item from a specific monster.

'''Usage'''
<code>

remove_held_item <variable>

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id.

=== RemoveMonsterAction ===
Remove a monster from the party if the monster is there.

Monster is determined by instance_id, which must be passed in a game
variable.

'''Usage'''
<code>

remove_monster <variable>

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id.

=== RemoveNpcAction ===
Remove an NPC object from the list of NPCs.

'''Usage'''
<code>

remove_npc <npc_slug>

</code>
'''Parameters'''
* <code>npc_slug</code>: Npc slug name (e.g. "npc_maple").

=== RemoveStateAction ===
Remove the specified state or the last active one.

This action allows the removal of a specific state from the client's
active state list. If no state name is provided, it removes the current
state, except for certain protected states (e.g., "WorldState" and
"BackgroundState").

'''Usage'''
<code>

remove_state [state_name]

</code>
'''Parameters'''
* <code>state_name</code>: The name of the state to remove (e.g., "PCState").
If not provided, the last active state will be removed, unless it's a
protected state.

=== RemoveStepTrackerAction ===
Removes a step tracker from a specific character.

'''Usage'''
<code>

remove_step_tracker <character>,<tracker_id>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or an NPC slug name (e.g., "npc_maple").
* <code>tracker_id</code>: Unique name for identifying the step tracker.

=== RemoveTechAction ===
Remove a specific technique from a specific monster in the party.

'''Usage'''
<code>

remove_tech <tech_id>[,<force_remove>]

</code>
'''Parameters'''
* <code>tech_id</code>: Name of the variable where the technique ID is stored.
* <code>force_remove</code>: Optional string flag to override forget rules.
Accepts "true", "1", or "yes" (case-insensitive).

'''Examples'''
* "remove_tech name_variable"
* "remove_tech name_variable,true"
* "remove_tech name_variable,1"

=== RemoveTrackerAction ===
Remove tracker.

'''Usage'''
<code>

remove_tracker <character>,<location>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>location</code>: location name (e.g. "paper_town").

=== RenameMonsterAction ===
Open the text input screen to rename the monster.

'''Usage'''
<code>

rename_monster <variable>

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id.

=== RenamePlayerAction ===
Open the text input screen to rename the character.

'''Usage'''
<code>

rename_player <character> [random]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or an NPC slug (e.g. "npc_maple")
* <code>random</code>: Adding "random" makes appear the dontcare button in the input.

=== ReplacePartyFromYamlAction ===
Replaces a character's party with a predefined set of monsters from a YAML file.

This action loads a named party configuration from a YAML file and assigns it
to the specified character (either the player or an NPC). Each monster entry
in the YAML can define attributes like slug, level, and weight for random selection.

'''Usage'''
<code>

replace_party_from_yaml <character>,<yaml_file>,<set_name>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or an NPC slug (e.g. "npc_maple").
* <code>yaml_file</code>: Name of the YAML file (without extension) located in the mods folder.
* <code>set_name</code>: The key of the party to use within the YAML file.

'''Examples'''
* "replace_party_from_yaml npc_maple,parties,starter_set"

=== ReplaceTechsFromYamlAction ===
Replaces a monster's moveset using a predefined set from a YAML file.

'''Usage'''
<code>

replace_techs_from_yaml <variable>,<yaml_file>,<set_name>

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where the monster UUID is stored.
* <code>yaml_file</code>: Path to the YAML file containing movesets.
* <code>set_name</code>: The key of the moveset to use within the YAML file.

'''Examples'''
* "replace_techs_from_yaml monster_id,movesets,starter_set"

=== RumbleAction ===
Rumble available controllers with rumble support.

'''Usage'''
<code>

rumble <duration>,<power>[,period][,delay][,attack_length]
[,attack_level][,fade_length][,fade_level][,direction]

</code>
'''Parameters'''
* <code>duration</code>: Time in seconds to rumble for.
* <code>power</code>: Percentage of power to rumble (0 to 100).
* <code>period</code>: Time period between vibrations in milliseconds.
Default 25.
* <code>delay</code>: Time in seconds before the rumble starts.
Default 0.
* <code>attack_length</code>: Time in milliseconds for the rumble to ramp up.
Default 256.
* <code>attack_level</code>: Initial intensity level during ramp-up.
Default 0.
* <code>fade_length</code>: Time in milliseconds for the rumble to fade out.
Default 256.
* <code>fade_level</code>: Final intensity level during ramp-down.
Default 0.
* <code>direction</code>: Direction of the rumble effect, for spatial control.
Default 16384.

=== RumblePatternAction ===
Play a named rumble pattern on available controllers.

'''Usage'''
<code>

rumble_pattern <pattern_name>[,target]

</code>
'''Parameters'''
* <code>pattern_name</code>: Name of the pattern ('pulse', 'heartbeat', 'explosion').
* <code>target</code>: Optional device index (-1 for all). Default -1.

=== SaveGameAction ===
Saves the game.

If the index parameter is absent, then it'll create
slot4.save

index = 0 > slot 1
index = 1 > slot 2
index = 2 > slot 3

'''Usage'''
<code>

save_game [index]

</code>
'''Parameters'''
* <code>index</code>: Selected index.

* <code>eg</code>: "save_game" (slot4.save)
* <code>eg</code>: "save_game 1"

=== SaveTimestampAction ===
Saves the current Unix timestamp (in seconds) into a game variable.

'''Usage'''
<code>

save_timestamp <variable>

</code>
'''Parameters'''
* <code>variable</code>: The name of the game variable to store the timestamp in.

=== ScreenTransitionAction ===
Initiate a screen transition that blocks until both fade out and fade in
are complete.

'''Usage'''
<code>

screen_transition [trans_time][,rgb]

</code>
'''Parameters'''
* <code>trans_time</code>: Transition time in seconds - default 0.3
* <code>rgb</code>: color (eg red > 255,0,0 > 255:0:0) - default rgb(0,0,0)

* <code>eg</code>: "screen_transition 3"
* <code>eg</code>: "screen_transition 3,255:0:0:50" (red)

=== SetBattleAction ===
Appends a new battle to the player's battle history.

'''Usage'''
<code>

set_battle <fighter>,<result>,<opponent>

</code>
'''Parameters'''
* <code>fighter_slug</code>: The slug of the battle participant (e.g., "player").
* <code>outcome</code>: The desired battle outcome ("won", "lost", or "draw").
* <code>opponent_slug</code>: The slug of the opponent (e.g., "npc_maple").

* <code>Example</code>:
`set_battle player,won,npc_maple`
Add the 'player' has won against 'npc_maple' to the history.

=== SetBillAction ===
Initializes or updates a bill for a character, including its amount,
interest rate, late fee and share rate.

'''Usage'''
<code>

set_bill <character>,<bill_slug>[,amount][,interest_rate][,late_fee][,share_rate]

</code>
'''Parameters'''
* <code>character</code>: "player" or the slug of an NPC (e.g. "npc_maple").
* <code>bill_slug</code>: identifier for the bill (must be translated in en_US base.po).
* <code>amount</code>: initial amount of the bill (optional, defaults to 0).
* <code>interest_rate</code>: interest rate applied to the bill (optional, e.g. 0.1 for 10%).
* <code>late_fee</code>: flat fee added to the bill when triggered (optional, eg. 10).
* <code>share_rate</code>: percentage of battle earnings automatically applied to the bill
(optional, e.g. 0.2 for 20%).

'''Examples'''
* set_bill player,bill_cathedral,100,0.1,50,0.5
* set_bill npc_maple,bill_rent,,0.05,25,0.2

* <code>Notes</code>:
* Interest and late fee are stored but not automatically applied.
* Use separate actions to trigger interest or fee accumulation.
* Amount must be non-negative.

=== SetBubbleAction ===
Put a bubble above player sprite.

'''Usage'''
<code>

set_bubble <npc_slug>[,bubble]

</code>
'''Parameters'''
* <code>npc_slug</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>bubble</code>: dots, drop, exclamation, heart, note, question, sleep,
angry, confused, fireworks

* <code>Example usage</code>:
"set_bubble spyder_shopassistant" (remove bubble from NPC)
"set_bubble spyder_shopassistant,note" (set bubble for NPC)
"set_bubble player,note" (set bubble for player)
"set_bubble player" (remove bubble from player)

=== SetCharAttributeAction ===
Set the given attribute of the character to the given value.

'''Usage'''
<code>

set_char_attribute <character>,<attribute>,<value>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>attribute</code>: Name of the attribute.
* <code>value</code>: Value of the attribute.

=== SetPlayerBirthdayAction ===
Open the date picker to set the player's birthday.

'''Usage'''
<code>

set_char_birthday <character> [random]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or an NPC slug (e.g. "npc_maple")
* <code>random</code>: If provided, assigns a random birthday instead of
opening the date picker.

=== SetCipherAction ===
Toggles ciphering for dialogue by enabling or disabling the CipherProcessor.

'''Usage'''

<code>

set_cipher <option>,<cipher_map>

</code>
* <code>Parameters</code>:

* <code>option</code>:
* "enable": Activates ciphering using the provided cipher map (if any).
* "disable": Disables ciphering entirely.

* <code>cipher_map</code>:
The filename (without extension) of a YAML file located in the mods folder.
* If omitted during "enable", the default cipher map is used.
* Ignored when option is "disable".

=== SetEconomyAction ===
Sets the economy (prices and initial stock of items/monsters) for a specific NPC.

This action orchestrates loading the economy data and then applying it to
the target character's shop/inventory, including handling initial quantities
and variable-based availability.

'''Usage'''
<code>

set_economy <npc_slug>,<economy_slug>

</code>
'''Parameters'''
* <code>npc_slug</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>economy_slug</code>: Slug of an economy.

=== SetEnvironmentAction ===
Switch or unload the active battle environment.

'''Usage'''
<code>

set_environment [slug]

</code>
'''Parameters'''
* <code>slug</code>: Optional. If provided, loads the environment slug from the
database. If omitted, unloads the current environment.

'''Examples'''
* set_environment grass
* set_environment

=== SetFacingModeAction ===
Change the facing mode of an NPC.

'''Usage'''
<code>

set_facing_mode <npc_slug>,<mode>

</code>
'''Parameters'''
* <code>npc_slug</code>: Slug of the NPC whose facing mode will be changed.
* <code>mode</code>: One of the valid facing mode names:
* follow_movement
* locked
* scripted

This action immediately updates the NPC's facing behavior. When set to
'locked' or 'scripted', the NPC will no longer automatically rotate to
match movement direction. When set to 'follow_movement', the NPC resumes
normal facing updates driven by the PathController.

=== SetKennelVisibleAction ===
Set a kennel's visibility state for a character.

* <code>From hidden to visible</code>:
set_kennel_visible player,name_kennel,true

* <code>From visible to hidden</code>:
set_kennel_visible player,name_kennel,false

'''Usage'''
<code>

set_kennel_visible <character>,<kennel>,<visible>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or NPC slug name (e.g. "npc_maple").
* <code>kennel</code>: Name of the kennel.
* <code>visible</code>: Optional string flag to set visibility.
Accepts "true", "1", "yes" for visible (case-insensitive).
Defaults to False when omitted or invalid.

=== SetLayerAction ===
Allows to change the color of the transparent layer.

'''Usage'''
<code>

set_layer <rgb>

</code>
'''Parameters'''
* <code>rgb</code>: color (eg red > 255,0,0,128 > 255:0:0:128)
default transparent

* <code>Note</code>: this is not a separate state, so it's advisable
to add a 4th value to the rgb, if not you're not
going to see the character, ideally 128.

=== SetMissionAction ===
Set missions by updating it and by checking the prerequisites.

'''Usage'''
<code>

set_mission <character>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").

=== SetMoneyAction ===
Set an amount of money for a specific slug.

'''Usage'''
<code>

set_money <slug>,[amount]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>amount</code>: Amount of money (>= 0) (default 0)

=== SetMonsterAttributeAction ===
Set the given attribute of the monster to the given value.

'''Usage'''
<code>

set_monster_attribute <variable>,<attribute>,<value>

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id.
* <code>attribute</code>: Name of the attribute.
* <code>value</code>: Value of the attribute.

=== SetMonsterFlairAction ===
Set or replace a monster's flair in a given category.

'''Usage'''
<code>

set_monster_flair <variable>,<category>,<flair>[,<sprite_type_1>:<sprite_type_2>:...]

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable that holds the monster's UUID.
* <code>category</code>: Category of the monster flair.
* <code>flair</code>: Name of the monster flair.
* <code>sprite_type(s)</code>: Optional pipe-separated list of sprite types
* <code>(e.g., front</code>: menu01)

* <code>Behavior</code>:
* If the category already has a flair, it will be replaced.
* If the category is new, the flair will be added.
* If sprite types are provided, the flair will only apply to those views.

=== SetMonsterHealthAction ===
Set the hp of a monster in the current player's party.

'''Usage'''
<code>

set_monster_health [variable][,health]

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id. If no
variable is specified, all monsters are healed.
* <code>health</code>: A float value between 0 and 1, which is the percent of max
hp to be restored to. A int value, which is the number of HP
to be restored to. If no health is specified, the hp is maxed
out.

=== SetMonsterLevelAction ===
Change the level of a monster in the current player's party.

'''Usage'''
<code>

set_monster_level [variable][,levels_added]

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id. If no
variable is specified, all monsters level up.
* <code>levels_added</code>: Number of levels to add. Negative numbers are allowed.
Default 1.

=== SetMonsterPlagueAction ===
Set a monster's plague to the given condition.

'''Usage'''
<code>

set_monster_plague <variable>,<plague_slug>,<condition>

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id.
* <code>plague_slug</code>: The slug of the plague to target.
* <code>condition</code>: Infected, inoculated, or None (removes the plague from the
character, indicating a healthy state).
* <code>enforced_check</code>: Optional string flag to enforce eligibility rules.
Accepts "true", "1", or "yes" (case-insensitive).
Default is False (eligibility is bypassed).

=== SetMonsterStatusAction ===
Change the status of a monster in the current player's party.

'''Usage'''
<code>

set_monster_status [slot][,status]

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id. If no
variable is specified, all monsters get/lose status.
* <code>status</code>: Status to set. If no status is specified, the status is
cleared.

=== SetPartyAttributeAction ===
Set the given attribute of party's monsters to the given value.

'''Usage'''
<code>

set_party_attribute <character>,<attribute>,<value>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>attribute</code>: Name of the attribute.
* <code>value</code>: Value of the attribute.

=== SetPartyStatusAction ===
Records important information about all monsters in the party.

'''Usage'''
<code>

set_party_status <player>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").

=== SetPricePolicyAction ===
Sets the PricePolicy for a specific NPC's economy.

'''Usage'''
<code>

set_price_policy <npc_slug>,<policy_slug>

</code>
'''Parameters'''
* <code>npc_slug</code>: Either "player" or NPC slug (e.g. "npc_maple").
* <code>policy_slug</code>: Slug of a price policy (e.g. "black_market").

=== SetRandomVariableAction ===
Sets a key in the player's `game_variables` dictionary to a randomly
selected value from a specified list. Values can be repeated or
weighted to influence selection probability.

'''Usage'''
<code>

set_random_variable <variable>,<value1>:<value2>:<value3>

You can also use weighted values:
set_random_variable <variable>,<apple=1>:<banana=3>:<cherry=2>

</code>
'''Parameters'''
* <code>variable</code>: The name of the game variable to set.
* <code>values</code>: A colon-separated string of values to choose from.
* Repeated values increase their selection chance.
* Alternatively, use `value=weight` to assign explicit weights.

=== SetRoutingPolicyAction ===
Sets or resets the routing policy for future monster additions.
This does not add a monster — it modifies how PartyHandler.add_monster behaves.

'''Usage'''
<code>

set_routing_policy <npc_slug>[,policy_name]

</code>
'''Parameters'''
* <code>npc_slug</code>: NPC slug to apply the policy to.
* <code>policy_name</code>: Name of the routing policy defined in routing_policies.yaml.

'''Examples'''
* set_routing_policy player,starter_policy
* set_routing_policy player,event_policy
* set_routing_policy player # resets to 'default'

=== SetStepTrackerMilestoneShownAction ===
Marks a milestone on a step tracker as shown for a specific character.

'''Usage'''
<code>

set_step_tracker_milestone_shown <character>,<tracker_id>,<milestone>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or an NPC slug name (e.g., "npc_maple").
* <code>tracker_id</code>: Unique name for identifying the step tracker.
* <code>milestone</code>: Step milestone to mark as shown.

=== SetTeleportFaintAction ===
Set teleport faint data

'''Usage'''
<code>

set_teleport_faint <character>,<map_name>,<x>,<y>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>map_name</code>: The name of the map to validate against.
* <code>x</code>: The x-coordinate to validate against.
* <code>y</code>: The y-coordinate to validate against.

=== SetTemplateAction ===
Switch template (sprite and combat_sheet).

Please remember that if you change the combat_sheet,
it automatically changes the combat_back.

* <code>Example</code>: if you put xxx, it's going to be xxx_back.png.

* <code>By using default</code>:

set_template player,default

it's going to reassign the default sprite.

'''Usage'''

<code>

set_template <character>,<sprite>[,combat_sheet]

</code>
'''Parameters'''

* <code>character</code>:
Either "player" or npc slug name (e.g. "npc_maple").

* <code>sprite</code>:
Must be inside mods/tuxemon/sprites.
* <code>Example</code>: adventurer_brown_back.png -> adventurer.

* <code>combat_sheet</code>:
Must be inside mods/tuxemon/gfx/sprites/player.
* <code>Example</code>: adventurer.png -> adventurer.

=== SetTuxepediaAction ===
Set the key and value in the Tuxepedia dictionary.

'''Usage'''
<code>

set_tuxepedia <character>,<monster_slug>,<label>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>monster_slug</code>: Monster slug name (e.g. "rockitten").
* <code>label</code>: seen / caught

=== SetVariableAction ===
Updates the player's game variables by setting key-value pairs.

'''Usage'''
<code>

set_variable <variable>:<value>[,<variable>:<value>]

</code>
'''Parameters'''
* <code>variable</code>: The name of the variable.
* <code>value</code>: The assigned value for the variable.

This implementation supports multiple parameters, allowing multiple
variable assignments in one call.

=== SetWeatherAction ===
Sets the weather to a specific slug using the WorldWeatherManager.
If no slug is provided, it triggers a weather advancement check.

'''Usage'''
<code>

set_weather <weather_slug> # Sets weather directly
set_weather # Advances weather based on previsions

</code>
'''Parameters'''
* <code>slug</code>: Optional weather slug (e.g., "rain", "sunny", "foggy").

=== ShowMonsterAction ===
Change to MonsterInfoState.

This action transitions to the MonsterInfoState, displaying detailed
information about a specific monster.

'''Usage'''
<code>

monster_info_state <monster_variable>

</code>
'''Parameters'''
* <code>monster_variable</code>: The name of the game variable holding the monster's UUID.

=== SpawnMonsterAction ===
Breed a new monster.

Add a new monster, created by breeding the two
given mons (identified by instance_id, stored in a
variable) and adds it to the given character's party
(identified by slug). The parents must be in either
the trainer's party, or a storage box owned by the
trainer.

'''Usage'''
<code>

spawn_monster [npc_slug]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
the one who is going to receive the new born

=== StartBattleAction ===
Start a battle between two characters and switch to the combat module.

'''Usage'''
<code>

start_battle <character1>,<character2>[,music]

</code>
'''Parameters'''
* <code>character1</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>character2</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>music</code>: The name of the music file to play (Optional).

=== StartCinemaModeAction ===
Start cinema mode by animating black bars to narrow the aspect ratio.

For a cinematic experience, specify the width of the horizontal and
vertical black bars as a ratio of the screen resolution.
* <code>For example, to achieve a 2.39</code>: 1 aspect ratio on a 1920x1080 screen,
you would set the horizontal ratio to 0.42 (1920 / 1080 * (16/9 - 2.39/1))
and the vertical ratio to 0 (no vertical bars).

By default only bar up and down.

'''Usage'''
<code>

start_cinema_mode [aspect_y_ratio][,aspect_x_ratio]

</code>
'''Parameters'''
* <code>aspect_y_ratio</code>: The width of the horizontal black bars as a ratio of
the screen resolution. Default standard cinema mode.
* <code>aspect_x_ratio</code>: The width of the vertical black bars as a ratio of
the screen resolution. Default None.

=== StartDoubleBattleAction ===
Start a double battle between two characters and switch to the combat module.

'''Usage'''
<code>

start_double_battle <character1>,<character2>[,music]

</code>
'''Parameters'''
* <code>character1</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>character2</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>music</code>: The name of the music file to play (Optional).

=== StopCinemaModeAction ===
Stop cinema mode by animating black bars back to the normal aspect ratio.

'''Usage'''
<code>

stop_cinema_mode
</code>

=== StoreMonsterAction ===
Store a monster in a box.

Save the player's monster with the given instance_id to
the named storage box, removing it from the player party.

'''Usage'''
<code>

store_monster <variable>[,box]

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id.
* <code>box</code>: An existing box where the monster will be stored.

=== StorePartyAction ===
Store the entire party in a box.

Save all monsters from the character's party into the named storage box,
removing them from the party if successful.

'''Usage'''
<code>

store_party <character>[,box]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or an NPC slug (e.g. "npc_maple").
* <code>box</code>: An existing box where the monsters will be stored.
If omitted, defaults to KENNEL.

=== TeleportAction ===
Teleport a character to a specific map and tile coordinates.

If a screen transition is in progress, the teleport will be queued
and executed at the apex of the transition.

'''Usage'''
<code>

teleport <character>,<map_name>,<x>,<y>

</code>
'''Parameters'''
* <code>character</code>: Slug of the character to teleport.
* <code>map_name</code>: Name of the map to teleport to.
* <code>x</code>: X coordinate of the map to teleport to.
* <code>y</code>: Y coordinate of the map to teleport to.

=== TeleportFaintAction ===
Teleport the player to the point in the teleport_faint variable.

Usually used to teleport to the last visited Tuxcenter, as when
all monsters in the party faint.

'''Usage'''
<code>

teleport_faint <character>,<healing>[,trans_time][,rgb]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>healing</code>: Trigger healing string flag ("true", "1", "yes" for True),
* <code>trans_time</code>: Transition time in seconds - default 0.3
* <code>rgb</code>: color (eg red > 255,0,0 > 255:0:0) - default rgb(0,0,0)

* <code>eg</code>: "teleport_faint player,true,3"
* <code>eg</code>: "teleport_faint player,true,3,255:0:0:50" (red)

=== ToggleEvolutionBlockAction ===
Blocks or unblocks a specific evolution for a monster.

'''Usage'''
<code>

toggle_evolution_block <character> <monster_variable> <evolution_slug> <action>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>monster_variable</code>: Name of the variable storing the monster's instance ID.
* <code>evolution_slug</code>: The slug of the evolution to block/unblock.
* <code>action</code>: "block" to permanently block, "unblock" to unblock.

=== TradingAction ===
Select a monster in the player party and trade.

'''Usage'''
<code>

trading <variable>,<added>

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id (removed).
* <code>added</code>: Slug monster or Name of the variable where to store the monster
id (added).

eg. "trading name_variable,apeoro"
eg. "trading name_variable,name_variable"

=== TransferMoneyAction ===
Transfer money between entities.

'''Usage'''
<code>

transfer_money <slug1>,<amount>,<slug2>

</code>
'''Parameters'''
* <code>slug1</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>amount</code>: amount of money.
* <code>slug2</code>: Either "player" or character slug name (e.g. "npc_maple").

* <code>eg</code>: player,100,mom (player transfer 100 to mom)

=== TransitionTeleportAction ===
Combines the "teleport" and "screen_transition" actions.

Perform a teleport with a screen transition. Useful for allowing the player
to go to different maps.

'''Usage'''
<code>

transition_teleport <character>,<map_name>,<x>,<y>[,trans_time][,rgb]

</code>
'''Parameters'''
* <code>character</code>: Slug of the character to teleport.
* <code>map_name</code>: Name of the map to teleport to.
* <code>x</code>: X coordinate of the map to teleport to.
* <code>y</code>: Y coordinate of the map to teleport to.
* <code>trans_time</code>: (Optional) Transition time in seconds. Default is 0.3.
* <code>rgb</code>: (Optional) Transition color in RGB format (e.g. "255:0:0" for red).
Default is black (0,0,0).

=== TransitionTeleportReturnAction ===
Teleport a character back to their previously recorded location,
using a screen transition.

This action retrieves the last executed teleport request and sends
the character back to its source map and coordinates. It must be
used after a teleport that stored return data (e.g. source_map, source_x, source_y).

'''Usage'''
<code>

transition_teleport_return <character>,<facing>[,trans_time][,rgb]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>facing</code>: One of "up", "down", "left", "right". Case-insensitive.
* <code>trans_time</code>: (Optional) Transition time in seconds. Default is 0.3.
* <code>rgb</code>: (Optional) Transition color in RGB format (e.g. "255:0:0" for red).
Default is black (0,0,0).

* <code>Requirements</code>:
* A previous teleport must have been executed and stored in
`teleporter.last_teleport_request`.
* The previous request must include valid source map and coordinates.

* <code>Example</code>:
* <code>transition_teleport_return player,down,0.5,255</code>: 255:255

=== TranslatedDialogAction ===
Open a dialog window with translated text according to the passed
translation key. Parameters passed to the translation string will also
be checked if a translation key exists.

'''Usage'''
<code>

translated_dialog <text>[,avatar][,position][,style]

</code>
'''Parameters'''
* <code>text</code>: Text of the dialog.
* <code>avatar</code>: Monster avatar. If it is a number, the monster is the
corresponding monster slot in the player's party.
If it is a string, we're referring to a monster by name.
* <code>position</code>: Position of the dialog box. Can be 'top', 'bottom', 'center',
'topleft', 'topright', 'bottomleft', 'bottomright', 'right', 'left'.
Default 'bottom'.
* <code>h_alignment</code>: Alignment of text in the dialog box, it can be 'left', 'center'
or 'right'. Default 'left'.
* <code>v_alignment</code>: Alignment of text in the dialog box, it can be 'bottom',
'center' or 'top'. Default 'top'.
* <code>style</code>: a predefined style in db/dialogue/dialogue.json

=== TranslatedDialogChoiceAction ===
Ask the player to make a choice.

'''Usage'''
<code>

translated_dialog_choice <choices>,<variable>

</code>
'''Parameters'''
* <code>choices</code>: List of possible choices, separated by a colon ":".
* <code>variable</code>: Variable to store the result of the choice.

=== TriggerStatusAction ===
Triggers the current status effect of a monster (e.g., poison, burn, sleep).

'''Usage'''
<code>

trigger_status <variable>,<status_name>

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable containing the monster ID. If not specified,
all monsters in the party will be affected.
* <code>status_name</code>: Optional. If provided, only triggers the status effect if it matches
the monster's current status slug.

'''Examples'''
* "trigger_status name_variable,poison"
* "trigger_status name_variable"
* "trigger_status"

=== TuneRadioAction ===
Launches the NuPhoneRadio interface for a given character, optionally tuned
to a specific frequency.

This action transitions the game into a radio interface state, allowing the
player to access broadcasts associated with a specific NPC. It can launch
either the standard radio menu or the tuner interface, depending on whether
a frequency is provided.

This is typically used in scripted events to simulate tuning into a radio
station from a character's perspective or location, enabling dynamic
storytelling and immersive audio experiences.

'''Usage'''
<code>

tune_radio <character_slug>
tune_radio <character_slug>[,frequency]

</code>
'''Parameters'''
* <code>character_slug</code>: The slug of the character (NPC) whose context will be
used to determine available radio stations and broadcasts.
* <code>frequency</code>: If provided, launches the tuner interface and attempts to
tune directly to the specified frequency (in MHz). If omitted, the
standard radio menu is shown instead.

=== UnloadSoundAction ===
Unload a specific sound from memory cache, or all sounds if no filename is given.

'''Usage'''
<code>

unload_sound <filename>
unload_sound

</code>
'''Parameters'''
* <code>filename</code>: Name of the sound file to unload.
If omitted, all cached sounds will be removed from memory.

=== UnlockControlsAction ===
Unlock player controls

'''Usage'''
<code>

unlock_controls
</code>

=== UnpauseMusicAction ===
Unpause the current (paused) music playback.

'''Usage'''
<code>

unpause_music
</code>

=== UpdateCipherAction ===
Updates the list of unlocked letters for a character used by the CipherProcessor.

'''Usage'''

<code>

update_cipher <character>[,letter]

</code>
* <code>Parameters</code>:

* <code>character</code>:
Either "player" or npc slug name (e.g. "npc_maple").

* <code>letter</code>:
* <code>A single uppercase letter (or multiple separated by '</code>: ') to add to
the character's unlocked set. If omitted, no new letters will be added,
but the CipherProcessor will be updated with the current unlocked state.

=== UpdateTilePropertiesAction ===
Update tile properties by modifying movement settings or accessibility.

'''Usage'''
<code>

update_tile_properties <label>[,moverate]

</code>
'''Parameters'''
* <code>label</code>: The name of the property to update (e.g., surfable, walkable).
* <code>moverate</code>: The value of the movement rate (e.g., 1 for normal movement,
0 for inaccessible).

* <code>Example</code>:
"update_tile_properties surfable,0.5" sets the surfable property to 0.5
for relevant tiles.

=== UpdateTimeAction ===
Update time variables.

'''Usage'''
<code>

update_time player

</code>
'''Parameters'''
* <code>file</code>: File to load.

* <code>eg</code>: "update_time player"

=== VariableMathAction ===
Perform a mathematical operation on the player.game_variables dictionary.

Optionally accepts a fourth parameter to store the result, otherwise it
is stored in ``var1``.

'''Usage'''
<code>

variable_math <var1>,<operation>,<var2>,<result>
variable_math <var1>,<operation>,<var2>

</code>
'''Parameters'''
* <code>var1</code>: First operand.
* <code>operation</code>: Operator symbol.
* <code>var2</code>: Second operand.
* <code>result</code>: Variable where to store the result. If missing, it will be
``var1``.

=== WaitAction ===
Block the event chain for a given duration.

'''Usage'''
<code>

wait <seconds>

</code>
'''Parameters'''
* <code>seconds</code>: Duration in seconds for the event engine to wait.
The wait is measured using accumulated delta time (dt)
from the game loop, not wall clock time.

=== WildEncounterAction ===
Start a encounter with a single wild monster.

'''Usage'''
<code>

wild_encounter <monster_slug>,<monster_level>[,exp_mod]
[,mon_mod][,env][,rgb][,held_item]

</code>
'''Parameters'''
* <code>monster_slug</code>: Monster slug.
* <code>monster_level</code>: Level of monster.
* <code>exp_mod</code>: Experience modifier.
* <code>mon_mod</code>: Money modifier.
* <code>env</code>: Environment (grass default)
* <code>rgb</code>: color (eg red > 255,0,0 > 255:0:0) - default rgb(255,255,255)
* <code>held_item</code>: item held by the monster

=== WithdrawMonsterAction ===
Pull a monster from the given trainer's storage and puts it in their party.

* <code>Note</code>:
If the trainer's party is already full then the monster will be
deposited into the default storage box automatically.

'''Usage'''
<code>

withdraw_monster <variable>,<character>

</code>
'''Parameters'''
* <code>variable</code>: Name of the variable where to store the monster id.
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
the one who is going to receive the monster

Event Reference Condition

2026-02-02T15:48:14Z

Jaskrendix:

== Conditions ==

=== AFKStateCondition ===
Check if one or more AFK states (thresholds) have been met.

'''Usage'''
<code>

is afk_state <level>

</code>
'''Examples'''
* is afk_state example
* <code>is afk_state warn</code>: kick

=== BattleOutcomeCondition ===
Checks if a character has achieved a specific battle outcome
against an opponent.

'''Usage'''
<code>

is battle_outcome <fighter>,<outcome>,<opponent>

</code>
'''Parameters'''
* <code>fighter_slug</code>: The slug of the battle participant (e.g., "player").
* <code>outcome</code>: The desired battle outcome ("won", "lost", or "draw").
* <code>opponent_slug</code>: The slug of the opponent (e.g., "npc_maple").

* <code>Example</code>:
`is battle_outcome player,won,npc_maple`
Checks if the 'player' has won against 'npc_maple'.

=== BattleOutcomeCountCondition ===
Checks if a character has achieved a specific battle outcome a minimum number of times
against a specific opponent.

'''Usage'''

<code>

is battle_outcome_count <fighter>,<outcome>,<opponent>,<count>

</code>
'''Parameters'''

* <code>fighter_slug</code>:
The slug of the battle participant (e.g., "player").

* <code>outcome</code>:
The desired battle outcome ("won", "lost", or "draw").

* <code>opponent_slug</code>:
The slug of the opponent (e.g., "npc_maple").

* <code>count</code>:
Minimum number of times the outcome must have occurred.

* <code>Example</code>:

<code>

is battle_outcome_count player,won,npc_maple,2

Checks if the 'player' has won at least 2 times against 'npc_maple'.
</code>

=== BillExistsCondition ===
Check to see if a bill exists.

'''Usage'''
<code>

is bill_exists <character>,<bill_slug>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>bill_slug</code>: The slug of the bill

eg. "is bill_exists player,my_bill"

=== BillIsCondition ===
Check to see if a bill exists and has a certain amount.

'''Usage'''
<code>

is bill_is <character>,<operator>,<bill_slug>,<amount>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>bill_slug</code>: The slug of the bill
* <code>operator</code>: Numeric comparison operator. Accepted values are "less_than",
"less_or_equal", "greater_than", "greater_or_equal", "equals"
and "not_equals".
* <code>amount</code>: Amount of money or value stored in variable

eg. "is bill_is player,bill_slug,equals,50"
* <code>eg. "is bill_is player,bill_slug,equals,name_variable" (name_variable</code>: 75)

=== ButtonComboCondition ===
Check to see if a particular sequence of buttons was pressed.

'''Usage'''
<code>

is button_combo <buttons>

</code>
'''Parameters'''
* <code>buttons</code>: A sequence of button/intention keys (E.g. "up:down:interact").

=== ButtonCountCondition ===
Check to see how many time a particular button was pressed.

'''Usage'''
<code>

is button_count <button>,<operator>,<amount>

</code>
'''Parameters'''
* <code>button</code>: A button/intention key (E.g. "up").
* <code>operator</code>: Numeric comparison operator. Accepted values are "less_than",
"less_or_equal", "greater_than", "greater_or_equal", "equals"
and "not_equals".
* <code>amount</code>: The number of times the button was pressed.

=== ButtonHeldCondition ===
Check to see if a particular key was held for a certain number of frames.

'''Usage'''
<code>

is button_held <button>,<frames>

</code>
'''Parameters'''
* <code>button</code>: A button/intention key (E.g. "up").
* <code>frames</code>: The number of frames the button must be held.

=== ButtonPressedCondition ===
Check to see if a particular key was pressed.

'''Usage'''
<code>

is button_pressed <button>

</code>
'''Parameters'''
* <code>button</code>: A button/intention key (E.g. "INTERACT").

=== CameraAtCondition ===
Check to see if the camera is at the position on the map.

'''Usage'''
<code>

is camera_at <tile_pos_x>,<tile_pos_y>

</code>
'''Parameters'''
* <code>pos_x</code>: X position of the camera.
* <code>pos_y</code>: Y position of the camera.

=== CelestialIsCondition ===
Evaluates a comparison against the current phase of a celestial body
(e.g., moon, sun) as provided by the session's CelestialManager.

This allows scripts to react to fictional astronomical cycles defined
in `celestial_cycles.yaml`, such as checking whether the moon is full,
waxing, waning, etc.

'''Usage'''
<code>

is celestial_is <body>,<operation>,<phase>

</code>
'''Parameters'''
* <code>body</code>:
The name of the celestial body to evaluate. This must match one
of the cycle names defined in `celestial_cycles.yaml`, such as
"moon" or "sun".

* <code>operation</code>:
A comparison operator. Only string-based comparisons are valid
* <code>for celestial phases</code>:
* "equals" or "=="
* "not_equals" or "!="

* <code>phase</code>:
The expected phase name to compare against. This must match one
of the phase labels defined for the celestial body in the YAML
configuration.

'''Examples'''
<code>

is celestial_is moon,equals,full
is celestial_is moon,not_equals,new
is celestial_is sun,equals,high
</code>

=== CharAtCondition ===
Check to see if the character is at the condition position on the map.

'''Usage'''
<code>

is char_at [character]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").

=== CharAtPositionCondition ===
Check to see if the character is at the position on the map.

'''Usage'''
<code>

is char_at_position <character>,<tile_pos_x>,<tile_pos_y>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>tile_pos_x</code>: X position to set the character to.
* <code>tile_pos_y</code>: Y position to set the character to.

=== CharDefeatedCondition ===
Check to see the character has at least one tuxemon, and all tuxemon in their
party are defeated.

'''Usage'''
<code>

is char_defeated <character>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple")

=== CharExistsCondition ===
Check to see if a character object exists in the current list of NPCs.

'''Usage'''
<code>

is char_exists <character>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").

=== CharFacingCondition ===
Check to see where a character is facing.

'''Usage'''
<code>

is char_facing <character>,<direction>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>direction</code>: One of "up", "down", "left" or "right".

=== CharFacingCharCondition ===
Check to see the character is next to and facing a particular character.

'''Usage'''
<code>

is char_facing_char <character1>,<character2>

</code>
'''Parameters'''
* <code>character1</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>character2</code>: Either "player" or character slug name (e.g. "npc_maple").

=== CharFacingTileCondition ===
Check to see if a character is facing a tile position.

This is checked against all the tiles included in the condition object.

'''Usage'''
<code>

is char_facing_tile <character>[,value]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple").
* <code>value</code>: value (eg surfable) inside the tileset.

=== CharGenderCondition ===
Check whether a character's gender matches the expected value.

'''Usage'''
<code>

is char_gender <character> <gender>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or an NPC slug (e.g. "npc_maple")
* <code>gender</code>: Expected gender string to compare against the character's gender

=== CharHealedCondition ===
Check whether all monsters in the character's party are healed.

'''Usage'''
<code>

is char_healed <character>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or NPC slug name (e.g. "npc_maple")

=== CharInCondition ===
Check to see if the character is on a specific set of tiles.

'''Usage'''
<code>

is char_in <character>,<value>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple")
* <code>value</code>: value (eg surfable) inside the tileset.

=== CharInBoundaryCondition ===
Checks if a character is within a specific named boundary.

'''Usage'''
<code>

is char_in_boundary <character_name>,<boundary_name>

</code>
'''Parameters'''
* <code>character_name</code>: "player" or an NPC slug.
* <code>boundary_name</code>: The name of the boundary to check (e.g., "safe_zone").

=== CharMovedCondition ===
Check to see the player has just moved into this tile.

Using this condition will prevent a condition like "char_at" from
constantly being true every single frame.

* Check if player destination collides with event
* If it collides, wait until destination changes
* Become True after collides and destination has changed

These rules ensure that the event is true once player in the tile
and is only true once. Could possibly be better, IDK.

'''Usage'''
<code>

is char_moved <character>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple")

=== CharSpriteCondition ===
Check the character's sprite

'''Usage'''
<code>

is char_sprite <character>,<sprite>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or character slug name (e.g. "npc_maple")
* <code>sprite</code>: NPC's sprite (eg maniac, florist, etc.)

=== CheckCharParameterCondition ===
Check the parameter's value of the character against a given value.

'''Usage'''
<code>

check_char_parameter <character>,<parameter>,<value>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (eg. "npc_maple").
* <code>parameter</code>: Name of the parameter to check (eg. "name", "steps", etc.).
* <code>value</code>: Given value to check.

eg. "player,name,alpha" -> is the player named alpha? true/false

=== CheckEvolutionCondition ===
Check to see the player has at least one tuxemon evolving.
If yes, it'll save the monster and the evolution inside a list.
The list will be used by the event action "evolution".

'''Usage'''
<code>

is check_evolution <character>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").

eg. "is check_evolution player"

=== CheckMaxTechCondition ===
Condition to check whether a character (player or NPC) has at least one
Tuxemon with more techniques than a specified threshold.

This condition is used in event scripting to trigger actions based on
the number of techniques a Tuxemon possesses. If the condition is met,
the matching monsters are stored in the session's `event_data` dictionary
under the key `"check_max_tech"`.

'''Usage'''
<code>

is check_max_tech <character>[,nr]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or NPC slug name (e.g. "npc_maple").
* <code>nr</code>: Optional integer specifying the minimum number of techniques.
Defaults to the config_monster.max_moves.

'''Examples'''
* "is check_max_tech player"
* "is check_max_tech npc_maple,2"

=== CheckMissionCondition ===
Check mission status for one or more missions.

'''Usage'''
<code>

is check_mission <character>,<method>,<status>[,<mode>]

</code>
* <code>Parameters</code>:
* <code>character</code>: Either "player" or NPC slug (e.g. "npc_maple")
* <code>method</code>: Mission slug(s), colon-separated (e.g. "mission1:mission2") or "all"
* <code>status</code>: One of ["pending", "completed", "failed"]
* <code>mode (optional)</code>: "any" (default) or "all"
"any" returns True if at least one mission matches status
"all" returns True only if all listed missions match status

'''Examples'''
* "is check_mission player,mission1,completed"
* "is check_mission player,mission1:mission2,completed,all"
* "is check_mission player,all,pending"
* "is check_mission npc_maple,missionA:missionB,failed,any"

=== CheckPartyParameterCondition ===
Check the given attribute of the party.

'''Usage'''
<code>

check_party_parameter <character>,<attribute>,<value>,<operator>,<times>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>attribute</code>: Name of the monster attribute to check (e.g. level).
* <code>value</code>: Value to check (related to the attribute) (e.g. 5 - level).
* <code>operator</code>: Numeric comparison operator. Accepted values are "less_than",
"less_or_equal", "greater_than", "greater_or_equal", "equals"
and "not_equals".
* <code>times</code>: Value to check with operator (how many times in the party?).

eg. "check_party_parameter player,level,5,equals,1"
* <code>translated</code>: "is there 1 monster in the party at level 5? True/False"

=== CheckTeleportFaintCondition ===
Check to see if check_teleport_faint exists and has a particular value.

If the teleport_faint does not exist it will return ``False``.

'''Usage'''
<code>

is check_teleport_faint character,[map_name],[x],[y]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>map_name</code>: The name of the map to validate against.
* <code>x</code>: The x-coordinate to validate against.
* <code>y</code>: The y-coordinate to validate against.

=== CheckWorldCondition ===
Evaluates specific world conditions against expected values.

This condition can check various parameters of the game world, such as
overlay colors (layer) and speech bubbles (bubble).

'''Usage'''
<code>

check_world <parameter>,<value>

</code>
'''Parameters'''
* <code>parameter</code>: The name of the world attribute to check.
* <code>value</code>: The expected value to compare against.

'''Examples'''
* "check_world layer"
* Ensures the overlay color is empty.

* "check_world bubble,npc_maple"
* Checks if NPC "npc_maple" currently has a speech bubble.

=== CooldownDaysCondition ===
Checks if a specified number of days has passed since the event last ran.

'''Usage'''
<code>

is cooldown_days <timeframe>,<variable>

</code>
'''Parameters'''
* <code>timeframe</code>: The number of days the event should be on cooldown.
* <code>variable</code>: The game variable where the cooldown date is stored.

=== CurrentStateCondition ===
Check to see if one or multiple state/states has/have
been started or not.

'''Usage'''
<code>

is current_state <state>

</code>
'''Parameters'''
* <code>state</code>: Either "CombatState", "DialogState", etc

* <code>eg</code>: "is current_state CombatState"
* <code>eg</code>: "is current_state CombatState:DialogState"

=== EnvironmentIsCondition ===
Check that the currently active environment slug corresponds to the expected value.

'''Usage'''
<code>

is environment_is <slug>

</code>
'''Parameters'''
* <code>slug</code>: The environment slug to check against the active environment.

'''Examples'''
* is environment_is grass
* is environment_is cave

=== FactionReputationCondition ===
Checks if an NPC's reputation meets a threshold.

'''Usage'''
<code>

is faction_reputation <character>,<faction_slug>,<operator>,<threshold>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>operator</code>: Numeric comparison operator. Accepted values are "less_than",
"less_or_equal", "greater_than", "greater_or_equal", "equals"
and "not_equals".
* <code>threshold</code>: A string representation of an integer (e.g. "30", "-100").
Will be parsed and used as a numeric threshold in comparison.

=== HasBagCondition ===
Check to see how many items are in the character's bag.

'''Usage'''
<code>

is has_bag <character>,<operator>,<value>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>operator</code>: Numeric comparison operator. Accepted values are "less_than",
"less_or_equal", "greater_than", "greater_or_equal", "equals"
and "not_equals".
* <code>value</code>: The value to compare the bag with.

=== HasItemCondition ===
Check to see if a character inventory contains something.

'''Usage'''
<code>

is has_item <character>,<item>[,operator][,quantity]

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>item</code>: The item slug name (e.g. "item_cherry").
* <code>operator</code>: Numeric comparison operator. Accepted values are "less_than",
"less_or_equal", "greater_than", "greater_or_equal", "equals"
and "not_equals".
* <code>quantity</code>: Quantity to compare with.

=== HasKennelCondition ===
Check to see how many monsters are in the character's kennel.

'''Usage'''
<code>

is has_kennel <character>,<kennel>,<operator>,<value>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>kennel</code>: The kennel name.
* <code>operator</code>: Numeric comparison operator. Accepted values are "less_than",
"less_or_equal", "greater_than", "greater_or_equal", "equals"
and "not_equals".
* <code>value</code>: The value to compare the party with.

=== HasMonsterCondition ===
Check to see if a character has a monster in its party.

'''Usage'''
<code>

is has_monster <character>,<monster>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>monster</code>: Monster slug name (e.g. "rockitten").

=== HasPartyBreederCondition ===
Check to see if the character has a male and female
monsters not basic (first evolution stage) in the party.

'''Usage'''
<code>

is has_party_breeder <character>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").

=== HasTechCondition ===
Check to see if the player has a technique in his party.

'''Usage'''
<code>

is has_tech <technique>

</code>
'''Parameters'''
* <code>technique</code>: Technique slug name (e.g. "bullet").

=== HasTuxepediaCondition ===
Check if a monster is registered in Tuxepedia.

'''Usage'''
<code>

is has_tuxepedia <character>,<monster>,<label>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>monster</code>: Monster slug name (e.g. "rockitten").
* <code>label</code>: Either "seen" or "caught".

=== KennelCondition ===
Check if a kennel is hidden, visible, or exists.

'''Usage'''
<code>

is kennel <character>,<kennel>,<option>

</code>
'''Parameters'''
* <code>character</code>: The character to check (either "player" or an NPC slug
name, e.g. "npc_maple").
* <code>kennel</code>: The name of the kennel to check.
* <code>option</code>: The expected visibility of the kennel ("hidden" or
"visible") or existence of it ("exist").

=== LocationInsideCondition ===
Check to see if the player is in a certain location type.

'''Usage'''
<code>

is location_inside

</code>
eg. "is location_inside"

=== LocationNameCondition ===
Check to see if the player is in a certain location name.

'''Usage'''
<code>

is location_name <slug>

</code>
'''Parameters'''
* <code>slug</code>: Slug name. It's the name inside the maps.
eg. "<property name="slug" value="routeb"/>"
slug = routeb

eg. "is location_name routeb"
* <code>eg. "is location_name routeb</code>: routea"

=== LocationTypeCondition ===
Determines whether the player is currently in a specified location type.

'''Usage'''
<code>

is location_type <slug>

</code>
'''Parameters'''
* <code>slug</code>: A string identifier for the location type.
* <code>Acceptable values</code>: "all" (matches any location)

* <code>Example usages</code>:
* "is location_type clinic" -> Checks if the player is in a clinic.
* "is location_type town:shop" -> Checks if the player is in either
a town or a shop.

The condition evaluates whether the player's current map type matches
any of the specified location types.

=== MoneyIsCondition ===
Check to see if the character has a certain amount of money (pocket).

'''Usage'''
<code>

is money_is <character>,<operator>,<amount>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>operator</code>: Numeric comparison operator. Accepted values are "less_than",
"less_or_equal", "greater_than", "greater_or_equal", "equals"
and "not_equals".
* <code>amount</code>: Amount of money or value stored in variable

eg. "is money_is player,equals,50"
* <code>eg. "is money_is player,equals,name_variable" (name_variable</code>: 75)

=== MonsterFlairCondition ===
Check if any monster in the character's party has a flair matching the
given category and name.

'''Usage'''
<code>

is monster_flair <character>,<category>,<name>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or an NPC slug name (e.g. "npc_maple").
* <code>category</code>: Category of the flair to check.
* <code>name</code>: Name of the flair to match.

* <code>Behavior</code>:
* Returns True if any monster in the character's party has a flair
in the given category with the specified name.
* Returns False if no match is found or the character is invalid.

=== MusicPlayingCondition ===
Check to see if a particular piece of music is playing or not.

'''Usage'''
<code>

is music_playing <music_filename>

</code>
'''Parameters'''
* <code>music_filename</code>: Name of the music.

=== OneOfCondition ===
Check to see if at least 1 among multiple values in a variable
is True.

If the variable does not exist it will return ``False``.

'''Usage'''
<code>

is one_of <variable>[,values]

</code>
'''Parameters'''
* <code>variable</code>: The variable to check.
* <code>values</code>: Value to check for (multiple values separated by ":").

* <code>eg. "is one_of name_variable,option1</code>: option2:option3"

=== PartyInfectedCondition ===
Check to see how many monster are infected in the character's party.

'''Usage'''
<code>

is party_infected <character>,<plague_slug>,<value>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>plague_slug</code>: The slug of the plague to target.
* <code>value</code>: all, some or none.

=== PartySizeCondition ===
Check the character's party size.

'''Usage'''
<code>

is party_size <character>,<operator>,<value>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>operator</code>: Numeric comparison operator. Accepted values are "less_than",
"less_or_equal", "greater_than", "greater_or_equal", "equals"
and "not_equals".
* <code>value</code>: The value to compare the party size with.

=== PartyStatusCondition ===
Check how many monsters in a character's party have a specific status.

'''Usage'''
<code>

is party_status <character>,<operator>,<value>,<status_name>

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>operator</code>: Numeric comparison operator. Accepted values are "less_than",
"less_or_equal", "greater_than", "greater_or_equal", "equals"
and "not_equals".
* <code>value</code>: Integer to compare against.
* <code>status_name</code>: Slug of the status to check (e.g. "poison").

=== StepTrackerCondition ===
Evaluates whether a step tracker exists for a character
and if a milestone has been triggered and not yet marked as shown.

'''Usage'''
<code>

is step_tracker character,tracker_id,milestone

</code>
'''Parameters'''
* <code>character</code>: Either "player" or an NPC slug name (e.g., "npc_maple").
* <code>tracker_id</code>: Unique name for identifying the step tracker.
* <code>milestone</code>: Step milestone to check.

=== TilePropertyUpdatedCondition ===
Checks whether all relevant tiles in the world have been
modified with a specific property.

'''Usage'''
<code>

is tile_property_updated <label>,<moverate>

</code>
'''Parameters'''
* <code>label</code>: The property name to check (e.g., terrain type).
* <code>moverate</code>: The expected movement rate value.

=== TimeIsCondition ===
Evaluates a comparison against a real-time property provided by the
session's TimeHandler. This allows scripts to react to the current
hour, season, weekday, stage of day, and other time-based values.

'''Usage'''
<code>

is time_is <property>,<operation>,<value>

</code>
'''Parameters'''
* <code>property</code>:
* <code>The name of a time property to evaluate. Valid options include</code>:
"date", "hour", "day_of_year", "year", "weekday", "leap_year",
"daytime", "month", "day", "stage_of_day", and "season".

* <code>operation</code>:
A comparison operator supported by the `compare` helper
(e.g., "equals", "not_equals", "greater_than", "less_than").

* <code>value</code>:
A literal value to compare against. Numeric values are compared
numerically (e.g., hour > 17), while non-numeric values are
compared as strings (e.g., season equals winter).

* <code>Example</code>:
<code>

is time_is hour,greater_than,17
is time_is season,equals,winter
is time_is stage_of_day,equals,dusk
is time_is date,equals,4-30
</code>

=== TimestampCooldownCondition ===
Checks if a specified number of seconds has passed since the event last ran.

This allows for more precise cooldowns than the "once per day" check.

'''Usage'''
<code>

is timestamp_cooldown <timeframe>,<variable>

</code>
'''Parameters'''
* <code>timeframe</code>: The number of seconds the event should be on cooldown.
* <code>variable</code>: The game variable where the cooldown timestamp is stored.

=== ToUseTileCondition ===
Check if we are attempting to interact with a map condition tile.

'''Usage'''
<code>

is to_use_tile
</code>

=== TrackerCondition ===
Check to see if tracker exists.

'''Usage'''
<code>

is tracker character,map_name

</code>
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>map_name</code>: The name of the map to validate against.

=== TrueCondition ===
This condition always returns true.

'''Usage'''
<code>

is true
</code>

=== TuxepediaCondition ===
Check Tuxepedia's progress.

'''Usage'''
<code>

is tuxepedia <operator>,<percentage>[,total]

</code>
'''Parameters'''
* <code>operator</code>: Numeric comparison operator. Accepted values are "less_than",
"less_or_equal", "greater_than", "greater_or_equal", "equals"
and "not_equals".
* <code>percentage</code>: Number between 0.1 and 1.0
* <code>total</code>: Total, by default the tot number of tuxemon.

=== VariableHighestCondition ===
Check if a specific variable is the highest among the others.

'''Usage'''
<code>

is variable_highest <key_to_check>,<keys_to_check>

</code>
'''Parameters'''
* <code>key_to_check</code>: Key to check.
* <code>keys_to_check</code>: List of the keys among to check separated by ':'

* <code>Example</code>:
* <code>is variable_highest jimmy,arthur</code>: jimmy:clara

=== VariableIsCondition ===
Check an operation over a variable.

'''Usage'''
<code>

is variable_is <value1>,<operation>,<value2>

</code>
'''Parameters'''
* <code>value1</code>: Either a variable or a number.
* <code>operation</code>: Numeric comparison operator. Accepted values are "less_than",
"less_or_equal", "greater_than", "greater_or_equal", "equals"
and "not_equals".
* <code>value2</code>: Either a variable or a number.

=== VariableLowestCondition ===
Check if a specific variable is the lowest among the others.

'''Usage'''
<code>

is variable_lowest <key_to_check>,<keys_to_check>

</code>
'''Parameters'''
* <code>key_to_check</code>: Key to check.
* <code>keys_to_check</code>: List of the keys among to check separated by ':'

* <code>Example</code>:
* <code>is variable_lowest jimmy,arthur</code>: jimmy:clara

=== VariableSetCondition ===
Checks if one or more player game variables exist and optionally match
specified values.

If a variable does not exist, the condition returns `False`.

'''Usage'''
<code>

is variable_set <variable>[:value],[<variable>[:value] ...]

</code>
'''Parameters'''
* <code>variable</code>: The variable to check.
* <code>value</code>: Optional value to check against. If omitted, the condition
only checks for the variable's existence.

The condition returns `True` if all specified variables exist and
match their given values (if provided). Otherwise, it returns `False`.

Event Reference Behavior

2026-02-02T15:44:57Z

Jaskrendix:

== Behaviors ==

=== DoorBehavior ===
Expand a `door` behavior into the conditions and actions required
to transition a character through a doorway or portal.

* <code>This behavior triggers when</code>:
* The character is standing on the door tile.
* The character is facing the required direction.

Once triggered, the character is teleported to the specified
destination coordinates and oriented to the given direction.

'''Usage'''
<code>

door <character>,<destination>,<x>,<y>,<direction>

</code>
'''Parameters'''
* <code>character</code>: The character slug (e.g. "player" or an NPC).
* <code>destination</code>: The map slug to teleport to.
* <code>x</code>: X-coordinate on the destination map.
* <code>y</code>: Y-coordinate on the destination map.
* <code>direction</code>: The direction the character must face to activate
the door, and the direction they will face after teleporting.

'''Examples'''
* door player,house_interior,5,3,up
* door npc_guard,town_square,10,12,right

=== TalkBehavior ===
Expand a `talk` behavior into the conditions and actions required
to initiate an interaction between the player and an NPC.

* <code>This behavior triggers when</code>:
* The player is facing the specified NPC.
* The player presses the INTERACT button.

Once triggered, the NPC will automatically turn to face the player.

'''Usage'''
<code>

talk <npc>

</code>
'''Parameters'''
* <code>npc</code>: The slug/name of the NPC the player can talk to.

'''Examples'''
* talk npc_maple
* talk shopkeeper

Event Reference Behavior

2026-02-02T15:42:04Z

Jaskrendix:

== Behaviors ==

=== DoorBehavior ===
Expand a `door` behavior into the conditions and actions required
to transition a character through a doorway or portal.

* <code>This behavior triggers when</code>:
* The character is standing on the door tile.
* The character is facing the required direction.

Once triggered, the character is teleported to the specified
destination coordinates and oriented to the given direction.

'''Usage'''
<code>

door <character>,<destination>,<x>,<y>,<direction>

</code>
'''Parameters'''
* <code>character</code>: The character slug (e.g. "player" or an NPC).
* <code>destination</code>: The map slug to teleport to.
* <code>x</code>: X-coordinate on the destination map.
* <code>y</code>: Y-coordinate on the destination map.
* <code>direction</code>: The direction the character must face to activate
the door, and the direction they will face after teleporting.

'''Examples'''
door player,house_interior,5,3,up
door npc_guard,town_square,10,12,right

=== TalkBehavior ===
Expand a `talk` behavior into the conditions and actions required
to initiate an interaction between the player and an NPC.

* <code>This behavior triggers when</code>:
* The player is facing the specified NPC.
* The player presses the INTERACT button.

Once triggered, the NPC will automatically turn to face the player.

'''Usage'''
<code>

talk <npc>

</code>
'''Parameters'''
* <code>npc</code>: The slug/name of the NPC the player can talk to.

'''Examples'''
talk npc_maple
talk shopkeeper