My Fairy Princess Combat Styles and Divine Weapons

Steam copy promises a wealth of combat styles and divine weapons to wield. The live demo is more conservative than the marketing, but it does print: a three-person party, a red HP bar, a blue bar, F for Confirm, Esc for Cancel, and a boar at 382 HP. This page is the combat-style dossier — what the demo teaches about stances, weapons, party roles, and what KDream has reserved for 1.0. Pair it with the combat guide for encounter rules and the ending planner if you are steering a hero route.

The store copy frames combat through six verbs: melee slash, ranged draw, alchemy toss, social distraction, stealth bypass, and cultivation spell. Read that as the parent’s palette, not as a class system. The demo has no class UI; the public forest screenshot reads as three body positions and a heart-shaped HP, not as a skill tree. Until KDream publishes a stance list, treat every named style as a verb your daughter can can lean into, not a fixed job. The verification we already have: HP and a second resource both print, both matter, both are visible on the public assets, and both are likely to survive into 1.0.

Three cameras, three combat modes (one for now)

Steam’s demo store page now lists a Turn-Based Combat tag alongside Life Sim and Dating Sim. An official forest screenshot shows live HP numbers and a Confirm / Cancel UI. Both can be true: the demo may switch modes by region (forest clearing vs town ambush), by encounter type (boss vs skirmish), or by season. Until KDream publishes a mode list, do not label the whole game as one system.

Three cameras you will see in the demo:

• Meadowville town camera — top-down, no combat UI.
• Forest clearing camera — side-on, party portraits, heart-shaped HP, F to confirm a swing.
• Boss / event camera — the same forest shot at a higher version line (v0.4.x); possibly the place where Turn-Based rules kick in.

The version line matters. Town screenshots are v0.1.x; at least one combat screenshot is v0.4.103. Two weeks of patches between them explain the UI drift. Log the watermark when you report a combat bug — see demo notes.

Combat styles Steam hints at

Steam and KDream’s playtest post both name combat as a system the parent can shape. The marketing copy is light on names but heavy on verbs:

• Martial arts / wand-shift — the daughter swinging a blade at a wolf for −46 damage. Most-photographed verb in public assets.
• Support / staff — the teal-clad party member with a long object that reads as a staff or brush. Spirit or Mind-coded in most HUDs.
• Tool / medicine — the wooden case on the third party member, likely a healer-adjacent role.
• Social / charm — festival encounters where Mood and Kinship act as the weapon.
• Stealth / blade-short — a quick-draw slot that resolves encounters without HP trades.
• Divine weapons — Steam copy says you can draw a divine weapon and reason with trouble. That is flavor for now, possibly a literal ult-meter in 1.0.

What is not confirmed:

• A class system. Do not assume healer / mage / warrior.
• A skill tree. Do not chase a 500% AP build from a YouTube thumbnail.
• Stance names. The HUD does not yet print stance labels.

What is confirmed:

• A party of three enters combat together.
• HP and a second resource (blue bar, 9 / 39 in the public shot) matter.
• Confirm / Cancel are explicit.
• Boar fights use the same UI as wolf fights.

Party roles as a stand-in for classes

Because the demo has no class names, treat party roles as the unit of choice:

• Daughter — body stat / Power, the high swing, the −46 on a wolf. Always the front-line carry.
• Companion A (staff) — likely support / control. Likely Spirit / Mind. The party member that turns a boar fight into a wolf fight.
• Companion B (case) — likely healer / utility. Likely support / knowledge-adjacent. The party member that lets the daughter swing twice in a row.

When you choose a party member, ask: is this a blade, a brush, or a kit? Each answers a different question. A blade wants more wilds. A brush wants to be paired with a kit. A kit wants someone who can take a hit while it works.

For hero ending routes (ending paths) build the blade. For healer ending routes, keep the kit alive. For enchantress / prodigy, treat combat as a story you read, not a fight you push.

The blue resource: what 9 / 39 might mean

The blue bar in the public screenshot is small (9 / 39) and adjacent to a small shield icon. Candidates the demo does not yet confirm:

• Mana / qi for spell casts.
• Block meter that fills on a successful defend.
• Stamina that drains on skill use.
• Combo meter for the next divine-weapon swing.

Treat it as the resource that costs more than HP to manage. Pick fights where you have full blue, not low where you have headroom. Spend blue last, not first. If the bar is small at start of fight, retreat and regroup; a depleted blue bar at fight start means a likely loss even at full HP.

Enemies the demo shows

The public combat screenshot names three enemies by HP alone:

• Wolf — 176 HP, fast swing. The opening foe in many party sims.
• Vine spirit — 427 HP, plant-coded, likely weak to fire / blade.
• Boar — 382 HP, slow but tanky.

These are samples. Do not build a tier bestiary from three data points. Do remember the shape: HP values are in the low hundreds, so a heal is worth three swings, not one. Plan AP for that.

Divine weapons: how to read the line

Steam’s most-quoted line is you may draw a divine weapon and reason with the trouble. That is a poetic way to say: a weapon unlocks a dialogue option that lets combat end without murder. The demo does not yet print that prompt, but the line is the most-likely place a xianxia ending writes itself.

Practical rules until 1.0:

• Treat divine weapons as post-combat unlocks, not pre-combat gear.
• One divine-weapon moment per chapter, at most.
• If a fight ends in a dialogue instead of a finisher, that is a flag for a possible transcendence lean. Track it in the ending planner.
• Divine weapons are the most-likely place a healer and a hero build cross paths. A healer who draws a blade in a final fight and chooses the dialogue option is the closest thing the game has to a hidden ending.

Combat style recommendations by ending lean

Hero. Lean blade, lean wilds, full party. Spend Mood like gold. Healer. Keep the kit alive. Trade one swing for one heal. Do not over-extend. Enchanter. Skip combat on busy days; make every fight a scene, not a stat. Prodigy. Combat only when it teaches a lesson. Read the combat encyclopedia after each fight. Mortal peace. Combat is a chore, not an identity. One block per week. Transcendence. Combat is a meditation. Always pick the dialogue option when it appears.

The activity ranking has a longer version of this list. The ending planner is where you mark which style you are saving.

What to report to KDream when combat feels wrong

Bring to princess help or Steam discussions:

1. Watermark version line.
2. Mode: town / forest / boss.
3. Party composition.
4. Blue bar value at start vs end of fight.
5. Was a dialogue prompt offered?

KDream’s playtest post asked for care. Combat reports with care are the ones that become 1.0 patches. See links for the channels and demo notes for the patch cadence.

A note on Princess Maker comparisons

Princess Maker 1 (1991) had a small set of combat jobs (knight, magician, priest). Princess Maker 2 (1993) widened the list dramatically. My Fairy Princess is more verbose about combat than Princess Maker 2 was about combat. The verbal emphasis does not mean the system is wider. It means the system is meant to be read as a philosophy choice. A combat style is who your daughter is, not a job title on her sheet.

What this wiki will add here

• Confirmed stance labels when 1.0 publishes them.
• A combat log of every public asset, with HP and blue bar values.
• A new-cycle inheritance rule for stance ranks.

Until then, raise her through a year with intention. Combat is the chapter. The years are the actual upbringing.