# seed-strategy

🧠 **Combat primer.** Read once, win twice as often.

### Stats that matter (v1)

* **STR** — damage bonus + minimum damage floor
* **DEX** — to-hit, armour class, *initiative*. Higher DEX swings first. Matters more than people realise
* **CON** — starting HP and armour class
* **INT / WIS / CHA** — dump stats. Reserved for future content (spells, crits, taunts)

### Combat resolution (per round)

1. Higher DEX swings first
2. Hit lands when `d20 + DEX ≥ defender's armour class`
3. Crit on natural 20
4. First to 0 HP loses. Same-round zero = tie, pot splits 50/50

### Practical tips

* **Farm easy wins early.** Match into your Rating band. Don't punch up until your BRAWL stack absorbs a bad streak.
* **Read the combat log on losses.** Bad rolls or structural disadvantage? Low DEX means always last to swing — that's not luck, that's fate.
* **Know your weapon.** Bazooka and Rail Gun (Epic) have damage ceilings that trivialise the fights they hit. They miss harder too.
* **Stop dueling on a 2-loss streak.** Resurrection costs scale with wins — you do not want to find out the hard way.
* **Bulk-mint pays off.** 5 in one tx → +1 bonus, 10 → +3 bonus, 20 → +7 bonus. Cheaper per-brawler and one gas fee.

### Founder perks (token IDs 1-100)

* **25%** off every duel stake (default; configurable per season)
* **First resurrection free** — die once on the house
* **+20 BRAWL bonus** on mint (on top of the standard 50 BRAWL airdrop, so 70 total)
* Permanent **★ FOUNDER** badge — gold for 1-50, cyan for 51-100

***

**Talk strategy here.** Post fight tx hashes with a quick note for the post-mortem — what worked, what got you smoked.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.baseicbrawlers.com/marketing/discord/messages/seed-strategy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.