Why Fight Dirty [Stealth Archer LitRPG] Is Climbing Royal Road Right Now

How did Fight Dirty launch?

Readers were waiting before chapter 1. Fight Dirty began as a point-of-view character that Perseus XXVII. cut from Traitor Hero, his other System-invasion LitRPG, and kept writing as an exercise. He already had two serials on Royal Road, compared in the table below.

The announcement rode on a real update. On October 5, 2026, Traitor Hero posted three chapters, its first since September 7. The author's note under the last of them introduced the new serial and asked readers to follow it and try a few chapters.

The note also explained the name. "Its actual name is Sneaky Bastard, but RoyalRoad thinks that name is unacceptable profanity," he wrote.

Both went up in the same hour. The chapter carrying the note went up at 11:15 UTC. Fight Dirty's launch batch went up between 11:12 and 11:23 UTC the same morning.

The returning readers showed up fast. The first reviews came within three hours. The author's note under chapter 12 already offered ten more chapters on Patreon, and every note since repeats that offer.

A few days later he wrote on Traitor Hero that he was "genuinely surprised by the generally positive reception despite its style being so far removed from what I usually write."

How fast did Fight Dirty climb Rising Stars?

The author's notes track the climb, charted below. When it reached #2 he wrote under chapter 19, "That's a high score for me. Both Hohenfels and Traitor Hero capped out at #3."

He did it without swaps. His profile says "I'm not interested in shout-out swaps, because they ruin my immersion when I binge stories."

It posts less than its neighbors. After launch the pace settled at one chapter every two or three days, at different hours. The serials either side of it on the main Rising Stars list post daily or nearly so.

Fight Dirty launched with the biggest batch of the top three and posts the least often. For how the list itself moves, see how Royal Road's Rising Stars works.

What do the title, blurb, tags and cover promise?

The title does two jobs. Fight Dirty is the attitude. The bracket names the build and the genre, so a LitRPG reader scanning Rising Stars knows what they are getting before they click.

The blurb is about 100 words. It opens on a gamer joke, "The stealth archer is inevitable," which anyone who has played a fantasy RPG will recognize.

Then it stacks the squeeze in short beats. Earth has been integrated into the System. His class burns through arrows. Food is running out. His only ally is a blind old woman in a boarded-up coffee shop.

One more line makes the world dangerous in a LitRPG way. Gangs are carving up the city, and everyone has learned that killing people gives EXP. It sells the hero's flaws as strengths (risk-taking, shameless opportunism, flexible morals) and closes on the title phrase.

It also leaves something out. Both of the author's other serials end their blurbs with a "What to expect" list, and so do Doomsday Pivot! and Dungeon Expert Eric. Fight Dirty has none.

The squeeze does that job here. Arrows, food and one ally tell you the story is about scarcity and risk. More on this in how to write a web fiction blurb.

The tags run to 13. The first three are LitRPG, Urban Fantasy and Progression, and the list includes System Invasion, Anti-Hero Lead and Secret Identity.

Anti-Hero Lead does the most work. It warns readers about the hero's morals before chapter 1, which is the one thing the lowest review objects to.

The cover shows a figure from behind in a long coat, a bow across his back, on a harbor at night with shipping containers and a crane. That is the setting of chapter 1.

The title sits at the top in large, rough white letters that stay readable at thumbnail size. The figure's turned back fits a stealth hero with a secret identity. See Royal Road cover design that converts for the general rules.

How does chapter 1 hook readers?

There is no prologue. Chapter 1, Cold Beans, is about 1,800 words. It opens in first-person present tense with Lukas watching a guard outside a gang-held harbor warehouse full of hoarded food.

Within the first lines the System appears as a short status tag on the guard, ~ Marauder, Level 9. A few paragraphs later comes his energy meter, ~ EN: 6/10, and the reason it matters. Without food he can't refill it.

One page sets up everything. You know the genre (levels, skills, monsters), the setting (a city after System integration), the danger (goblins, a gnoll, and gangsters who kill people for experience points) and the want (a decent meal).

The want is small and physical, and everything in the chapter hangs off it. Spending Energy on a stealth skill is a gamble with the meal he hasn't found yet.

The chapter ends on a character beat. Back at the coffee shop, the old woman, Christa, heals a wounded fighter whose friend brings him to the door after dark. As they turn to leave, Lukas stops them and asks for payment, and that word ends the chapter.

It tells you more about him than a page of backstory would, and it delivers the blurb's promise of shameless opportunism on the chapter's last line. For a fuller template, see the Royal Road chapter 1 template.

What do early readers love about it?

Five themes come up in the reviews, and the cards below give readers' own words.

• It starts fast. Readers like how little setup comes before the action.
• The system stays out of the way. Nobody asks for more stat screens.
• The lead is capable without being overpowered. One reviewer praises "a main character who understands his limits."
• The close first-person voice pulls readers through. Because you know only what Lukas knows, one reviewer says, "you learn alongside him."
• Readers followed the author. "Came here from the Author's other work," one review says, and another calls Fight Dirty "worth paying for more."

The humor helps too. In chapter 6 Lukas gives a gang boss the alias Shade, and the boss mocks it on the spot. A reviewer calls that "self aware storytelling," and it keeps a grim setting readable.

What do readers criticise?

The criticism so far is about the hero and the missing background. No review complains about the system mechanics. The table below puts each complaint next to the score its reviewer gave.

• The body count splits readers. The 2.5-star reviewer tallies the people Lukas has killed while still under level 10 and calls the setup "a cruel, unsatisfying, and unempathetic system and structure for the story." The Anti-Hero Lead tag and the blurb flag this, and other reviewers enjoy it.
• The other three come from 5-star reviews. The reviewer who missed the background says it lets you slide straight into the main story. The one who finds Lukas flat sees him growing into a mercenary with standards.

See how to handle negative reviews on Royal Road.

How is the progression system built?

System text is short and marked. Every System line starts with a tilde and sits on its own line. Level tags, Energy readings and kill notices with the EXP awarded all look the same.

Skills appear in square brackets when Lukas uses them. You can skim them or read them, and the prose rarely stops for a table.

Attributes are small numbers, as the table below shows. With values that small, a single point is something the reader can feel.

Energy is the economy. Skills cost Energy, Energy needs food, and food is what the gangs are hoarding. The System's resource and the survival problem are the same thing, so every fight is also a budget decision.

The class choice is planted early and paid off at the end of the launch batch. Chapter 4 shows a Tier II class, Hunter, priced above what Lukas has. He saves toward it and buys one of its skills in chapter 6.

In chapter 12, the last of the launch chapters, he takes Hunter at a lower price, because the skills he already owns count toward it. Readers who binged the launch batch finished on a payoff they had watched build for eight chapters.

A second class arrives with a cost. In chapter 15 Lukas takes a Tier I class, Nox, from an entity he suspects is a goddess, the Veiled Lady. The System leaves him in her debt. Debt gives the hero new power and the story a new hook in the same scene.

The full stat sheets live outside the chapter. Author's notes under chapters 2, 4, 6, 12 and 15 link to Lukas's current stats on the author's own Generia site, with a separate snapshot for each.

The site also documents the rules and lists classes up to Tier III, well past where Lukas is. Readers who love numbers get the whole sheet. Everyone else gets a story with "no constant stat sheets."

Chapters are short, which suits a binge and a phone screen. See how long Royal Road chapters should be.

Exposition is held back. First-person present means you know only what Lukas knows. One reviewer liked learning alongside him and another missed the background. The trade keeps the early chapters moving.

The arc is a climb through the underworld. The launch chapters stay on scavenging and survival around the harbor, then Lukas starts taking paid jobs from an underworld boss. Reviewers see where it is heading.

What should you borrow for your own serial?

1. Launch where your readers already are. If you have a serial running, announce the new one in the author's note of a real update and post the new serial in the same hour. Fight Dirty's announcement rode on Traitor Hero's first chapters in four weeks.
2. Launch with enough to binge, and end the batch on a payoff. Twelve chapters, about 20,000 words, ending on a class choice set up in chapter 4. See how many chapters to stockpile before launching.
3. Put the build in the title. A bracket naming the class fantasy and the genre tells a Rising Stars browser what the book is at a glance.
4. Make the System's resource the plot's problem. Energy, arrows and food are one budget, so every fight costs something.
5. Keep System text short in the chapter and the full sheet in the author's note. Readers who want the numbers click through, and the rest keep reading. How to track LitRPG stats covers keeping that sheet accurate.
6. Open on a small, physical want. A meal is easier to care about on page one than a world-ending threat.
7. End chapter 1 on a line that defines your lead. Fight Dirty ends on a demand for payment.
8. Use small numbers. Attributes of 4 to 6 make each point count and leave plenty of room to grow. See how to pace power progression.
9. Keep your Patreon offer steady. Every note since chapter 12 offers the same ten chapters ahead, so readers know exactly what they get. His Patreon sells each serial's advance chapters as its own tier, shown below.

What should you not copy?

• A 12-chapter drop with nobody waiting. It worked here because thousands of readers already followed the author's other serials, and the announcement reached them that same morning. With no audience yet, a steady schedule may matter more than a big first day. Dungeon Expert Eric, #3 on the same list, launched with 4 chapters and posts daily.
• Three chapters a week as a newcomer. Fight Dirty's pace, charted below, leans on readers who already trust the author. Most of the serials beside it post daily.
• Skipping the expectations list if readers don't know you. A known author can let the hook speak. A short "What to expect" list can tell new readers about the hero's morals and how many stat screens to expect.
• A ruthless lead you haven't committed to. Fight Dirty signals its anti-hero in the tags and the blurb, and still draws the body-count review. If your lead kills freely, say so up front and give readers a reason to stay with him.
• The premise itself. A stealth archer in an urban System invasion is this author's twist in this author's world. Find a one-sentence twist of your own.
• A title Royal Road may refuse. Fight Dirty's first name was treated as profanity. Check yours against the site's rules before launch day.

What does a Fight Dirty style launch checklist look like?

1. Write the hook as one sentence with the build in it, and put the build and genre in the title bracket.
2. Pick tags that warn as well as sell, such as Anti-Hero Lead if your lead is ruthless.
3. Make the cover show the chapter 1 setting, with a title readable at thumbnail size.
4. Open chapter 1 in motion, with a System element in the first lines and a small, concrete want.
5. End chapter 1 on a line that defines your lead.
6. Bank enough chapters to binge, and end the launch batch on a payoff you planted earlier.
7. Choose a post-launch schedule you can keep for months, and keep it.
8. If you already have readers, announce the launch in the author's note of a real update and post in the same hour.
9. Keep System lines short in the prose and the full stat sheet in a linked note.
10. If you run a Patreon, put the same clear offer in every author's note.
11. Read every review in the first two weeks and write down what readers name, good and bad.

Where PlotWrite fits. Perseus XXVII. keeps a statblock for Lukas at chapters 2, 4, 6, 12 and 15, plus a rules site for the whole world. Keeping that ledger by hand is work, and it's where LitRPG serials slip, with a stat that drops between chapters or a skill bought twice.

PlotWrite's Story Bible holds what is true at each chapter for every character, skill and item, and Check chapter flags contradictions before you post. It works with the Claude or ChatGPT plan you already pay for, and the memory and checks need no AI tag on Royal Road.