A safe Solasta II party is not one mandatory list of four classes. It is four characters that collectively hold two lanes, recover a fallen sibling without losing the round, attack beyond melee range, and pass the checks that move exploration and dialogue. Fighter, Rogue, Cleric, and Wizard can do that; so can several less traditional lineups if the functions still exist.
The research cutoff is July 20, 2026. It covers the Windows Early Access client through official hotfix v0.3.8.100677. The current store state is a portion of Act I, a four-character player party, six starting classes, SRD 5.2 rules, and a level cap of 4. Balance, subclasses, feats, and implementation details can change; the live character preview and newer Tactical Adventures notes take priority.
Audit jobs before choosing class names
Write four checks beside the party before pressing Start:
- Can two characters remain exposed? Several encounters approach from more than one side. One armored body is not enough if a mobile enemy walks around it.
- Can somebody restore a downed ally now? A bonus-action heal is ideal, but Lay on Hands, a potion in every inventory, and revival supplies are valid layers.
- Can two characters contribute at range? The second does not have to be a full caster. A bow, cantrip, or prepared ranged attack prevents an unreachable target from wasting half the party’s turn.
- Who owns Dexterity, Intelligence, Wisdom, and Charisma checks? One character does not need every skill, but the group should have a credible specialist for locks and traps, knowledge, perception, and conversation.
If all four answers are clear, the party is probably viable. If one answer is “the healer will fix it,” test again: the healer may be the character already down.
Build a front pair, not a lone tank
A front pair is defined by survivability and control of space, not by a class badge. Fighter and Paladin are the obvious pair. A heavy-armored Cleric can replace either. A defensive subclass or a high-AC hybrid may do the same job if it can survive focus fire and still perform its main action.
Give the pair different tools. One can carry the highest armor and shield available; the other should have reach, movement, control, or a reliable ranged option. Place them one or two tiles apart at a doorway or climb. That blocks two approach squares without clustering all four characters inside the same area effect.
Do not measure toughness only by hit points. Armor Class changes how often the hit lands, Constitution changes how many hits remain, saving throws decide whether a defender loses its turn, and a concentration spell can disappear when the defender is struck. Open the combat log after a surprising hit and read the attack bonus, roll mode, cover, and condition instead of assuming the armor is broken.
The current level cap is 4, so a build that only becomes coherent at level 5 is not an Early Access solution. Judge the character at levels 1, 3, and 4: base class, subclass, then feat. Future features described by a subclass announcement are not current tools merely because the developer plans them for level 7 or 10.
Give every fragile character an exit
The two rear characters need more than damage. Each should have at least one way to avoid losing a whole round when an enemy reaches them:
- a bonus-action disengage or movement feature;
- a defensive reaction such as Shield;
- a control effect that removes the enemy’s reaction;
- a one-handed ranged set that can be swapped without rebuilding inventory mid-fight;
- or a frontliner positioned to block the direct path.
Weapon swapping between prepared sets is free, but movement away from a melee threat can trigger an opportunity attack. Do not click the destination first and hope. Check whether the target still has a reaction, use a disabling effect if available, or Dodge while the party removes the threat.
Ready Action also consumes the character’s reaction when it triggers. That trade matters: a frontliner holding a melee attack may give up the opportunity attack that would otherwise punish movement. A caster readying a single-target spell may give up Shield or another defensive reaction. Use Ready when the trigger is likely before the next turn, not as a generic “do something later” button.
Let backgrounds connect stats to campaign checks
In the current rules, the background carries ability-score options, skills, an Origin Feat, and personality weight. Start with the class’s primary ability, then ask what the party still lacks. A Rogue with high Dexterity can own locks and traps; a Wizard can anchor Intelligence checks; a Cleric can cover Wisdom and Perception; a Paladin or Sorcerer can lead Charisma scenes. These are examples, not fixed assignments.
Do not give three siblings the same social personality just because one background has an attractive feat. Solasta II selects speakers across the family, and a narrow set of personalities, skills, and languages reduces the alternatives offered in conversation and exploration. Spread languages as well as numerical bonuses; a document nobody can read is a party-level failure.
For point-buy planning, a primary score of 17 can be efficient if a level-4 feat shown in the live client adds +1 to that same ability, reaching 18 and its next modifier. Do not force 17 when the feat you actually want has no matching increase. Confirm the level-up preview, because Early Access tuning can move or rewrite feats.
Community background guides disagree about the best pairing for several classes and currently carry Steam removed/incompatible warnings. The stable rule is narrower: the background must allow the abilities your class uses, its feat must not duplicate a feature you already own, and its skills should fill a party gap. That test survives balance changes better than a ranked background table.
Make round one change the battlefield
Four isolated attacks are often a weak opening. A productive first round creates a position the enemy must solve:
- Enter Cautious Mode before contact when the encounter permits it.
- Check light, line of sight, cover, climb points, and enemy spawners before selecting the first attack.
- Put the front pair on the approach, not deep inside the enemy group.
- Use a buff, control spell, or mastery effect that improves later attacks.
- Remove the enemy that creates more enemies, attacks from outside the formation, or can disable multiple characters.
Let melee enemies Dash toward the formation when possible. A creature that spent its action reaching you did not spend it dealing damage. That is usually better than sending a fragile character forward to gain one attack and receive four in return.
Vertical maps make pushing and chokepoints valuable, but inspect the landing and route before committing. A push that merely moves a healthy enemy away from the frontliner can make the next ally’s melee turn worse. A push that drops the target, breaks a formation, or clears a threatened caster changes the round.
Spend movement, bonus action, action, and reaction in that order
You do not have to move all at once. Step into line of sight, make the attack, then spend the remaining movement on cover. Before choosing Ready Action, use any intended movement and bonus action because Ready ends the turn immediately.
Bonus actions are not free flavor. Drinking a potion, Healing Word, Lay on Hands in the 2024 implementation, Rogue movement tools, Innate Sorcery setup, and Divine Smite may compete for that slot. If a Paladin plans to smite, do not spend the bonus action first and then discover the damage option is unavailable. If the target has only a few hit points, keep the spell slot for something that will survive the basic hit.
Likewise, do not spend the reaction automatically. Ask what the character protects with it this round: an opportunity attack, a readied strike, Shield, or a subclass defense. The combat log records why a reaction did or did not occur and is the fastest way to distinguish a rules interaction from a bug.
When attacks miss, diagnose the roll
Accuracy problems usually have a visible cause. Hover the failed attack in the combat log and check these in order:
- Light and vision: illuminate the target or move a character whose vision can handle the space. Do not assume every ancestry sees the same scene.
- Weapon ability: finesse and ranged weapons normally use Dexterity; other weapons normally use Strength. A proficiency tag also matters.
- Line of sight and cover: a clear camera view is not necessarily a clear attack line. Move sideways before spending the action.
- Advantage and disadvantage: one source of each can cancel. Adding another advantage does not necessarily repair the roll.
- Spell components: some spells require a free hand, a focus, or a named material. Read the spell card before selecting it at level-up.
Guidance is valuable before ability checks, not a reason to leave every skill at a poor modifier. Bless improves attacks and saving throws but consumes concentration. Light solves a vision problem but may reveal a sneaking party. Each tool fixes a specific failure; none is a permanent “always on” answer.
Recover the round, not the whole health bar
When a sibling reaches zero hit points, the immediate goal is to restore a legal turn and stop the death-save spiral. A small bonus-action heal can be better than a large action heal because the rescuer still acts and the revived character returns to initiative. Stabilize if healing cannot reach them. Keep a potion on each character so recovery does not depend on opening another sibling’s inventory under pressure.
Carry Aether Pearls or Scrolls of Revivify when vendors offer them. The campaign can end if a main party member dies and nobody can restore them. Revival stock is separate from ordinary healing stock; spending the last Pearl on a reward calculation can leave no answer to a permanent death.
After combat, loot before resting. A short rest spends Hit Dice and restores class features that explicitly return on a short rest. A long rest restores the broader resource set, enables level-up when available, and consumes Food Rations. Do not long-rest by habit after every small fight if the world-map trip ahead will leave the group without food.
Two sample parties pass the same audit differently
Fighter, Paladin, Rogue, Wizard: Fighter and Paladin form the front pair. Paladin covers emergency recovery and Charisma, Rogue owns Dexterity tools and mobile damage, and Wizard supplies Intelligence, control, light, and area damage. This group has fewer routine Wisdom tools, so give Perception and Insight deliberate attention through ancestry, background, or skill selection.
Fighter, Cleric, Rogue, Sorcerer: Fighter and an armored Cleric hold space. Cleric supplies Wisdom and ranged recovery; Rogue supplies Dexterity and tools; Sorcerer supplies Charisma, flexible spell pressure, and a second ranged lane. This group can lack deep Intelligence coverage, so build one sibling to handle Arcana, History, and Investigation rather than discovering the gap at the first locked lore check.
Paladin, Cleric, Sorcerer, and Wizard can also work if backgrounds or ancestry cover traps and locks. Fighter, Paladin, Sorcerer, and Wizard can work if recovery and Dexterity tools are explicit. The point is not to replace one mandatory quartet with another; it is to see which job disappears when a class changes.
Do not build around a known broken interaction
The June 22 hotfix lists Ambidextrous and Follow-Up Strike as known issues that do not work properly. Until a newer official note says otherwise, do not make either feat the only reason a character’s damage loop functions. The same current patch fixed attack names disappearing from the combat log, so update the client if the diagnostic names in this guide are missing.
Update 0.5 also made the off-hand bonus attack conditional on first using a Light weapon for the triggering attack, fixed several subclass and spell interactions, and changed the character creator substantially. Saved characters and a previous-version branch exist for recovery, but a build copied from a launch-week guide may no longer reproduce. Re-read the live action cost, condition, and component on every load-bearing feature.
Sources & credits
AppID 2975950, the four-character party, SRD 5.2 positioning, six Early Access classes, level-4 cap, official screenshots, class intentions, Ready Action limits, and the current known-issue boundary were checked against the official Solasta II Steam page, Tactical Adventures’ official Steam announcements, and the official Solasta site. UI behavior and party heuristics were cross-checked among readable beginner references and community guides; removed/incompatible Steam guides were used only as cautious secondary checks. The image is an unmodified official Steam JPG.