Forgetax +99 Sword Setup Guide: Farm Tickets and Prepare Holy Relics

1. Start With an Established Post–May 5 Run

This Forgetax guide covers a late-run strategy: deliberately break eligible swords to accumulate permanent draw tickets, preserve enough sword value to pay tribute, and prepare for a holy relic setup intended to support a +99 sword attempt.

The supplied transcript does not show a completed +99 sword or a successful holy relic combination. It ends while Dabble is still farming tickets and reconsidering the build. Follow this as a demonstrated farming method and preparation guide, not a guaranteed route to +99.

The starting position matters. Dabble has already survived through May 5, described as the initial target, and is continuing into an endless-style portion of the run. The build already has substantial wealth, several interacting relics, and a board containing 60 tickets, including nine break tickets.

Before copying the aggressive forging:

• Check your current tribute requirement.
• Identify a sword you can reserve for that payment.
• Confirm that your relics support permanent-ticket farming.
• Separate disposable farming swords from valuable tribute candidates.

Dabble can afford to sacrifice expensive swords because the run is already wealthy. Those decisions are not presented as a fresh-run opening strategy.

2. Assemble the +7 Sword Farming Engine

The initial setup combines swords issued at +7, bonuses that activate at that enhancement level, extra supplies, and protection against early breaks.

The transcript’s pronunciation of the ticket-granting scabbard’s name is unclear. Identify it by its effect rather than confusing it with Dawn Scabbard, which is discussed later for enhancement inheritance.

Dabble describes receiving up to six swords per day: three standard swords, one from Supply Permit, and up to two from Undertaker’s Ledger.

The central interaction is straightforward: Lifetime Contract supplies eligible swords immediately, and the scabbard converts their eventual destruction into permanent tickets. Extra supplies keep that cycle moving.

Keep the initial break protection while establishing the loop. Removing it becomes a later adjustment, not the starting requirement.

3. Forge Disposable Swords Into Permanent Tickets

With the engine active, repeatedly forge swords you are willing to lose. The objective is no longer to preserve every promising weapon; it is to improve the draw board over the remainder of the run.

Use this sequence:

1. Choose a disposable sword. Favor the supplied +7 swords because they already meet the farming threshold.
2. Watch its enhancement level. Damage can knock a sword below +7. Dabble continues forging lower-level swords until they return to eligibility.
3. Keep forging toward an actual break. A protection effect may absorb an earlier break instead of destroying the sword.
4. Check the permanent ticket gained. Success and great additions are especially welcome in the demonstrated run.
5. Repeat with another sword, while keeping tribute covered.

For swords that do not start at +7, reach that level before relying on the scabbard’s effect. Dabble tests worn swords this way and obtains permanent success tickets after getting them into the eligible range.

Understand what each ticket contributes

The creator’s reasoning is that adding tickets to non-break outcomes reduces the relative share represented by break tickets. That makes even an unwanted damage ticket useful for reducing the board’s break proportion.

However, fewer breaks do not automatically mean better value growth.

Damage becomes a recurring weakness. Dabble notes that accumulating damage tickets also makes further damage-related permanent additions more likely, and repeatedly struggles with swords whose value is not growing well.

Save consumables during ordinary farming. Early in the run, Dabble deliberately avoids spending them on swords intended for destruction.

4. Secure Tribute Before Chasing Bigger Swords

Permanent-ticket growth does not remove the tribute requirement. Dabble repeatedly pauses the farming loop to preserve or turn in a valuable sword.

Make that your checkpoint:

1. Check the payment currently required.
2. Set aside a sword that covers it.
3. Continue farming with the remaining stock.
4. Turn in the reserved sword rather than exposing your only payment option to another forge attempt.

The transcript mentions requirements around 400,000, then later 500,000. These are examples from this run, not fixed targets for every day. Dabble explicitly remains uncertain about how the requirements scale.

Several successful turn-ins demonstrate the build’s earning potential:

These outcomes are examples, not minimum values you must reach.

Dabble also spends heavily at a shop, buying Ghost Delivery Notes, other supplies, and available swords. The practical lesson is to maintain farming stock while respecting your current finances—not to copy those purchases without the same wealth.

Do not adopt the creator’s changing risk thresholds as safety rules. Dabble keeps forging at various points below 30%, 20%, or 10% displayed break chance, but a sword still breaks during the low-risk sequence after the relic swap.

Chalk is used when trying to secure sufficient value, but the transcript does not clearly explain its mechanics. It also shows a break during a greedy extra attempt involving red chalk. Consumable use is not demonstrated as a guarantee of safety.

5. Adjust Relics, Then Check the Holy Setup’s +0 Requirement

Once the permanent board has grown, Dabble considers whether too much break protection is slowing the farming loop. A sword that survives longer may build value, but it also delays the permanent ticket awarded when it finally breaks.

The demonstrated change is to replace Unyielding Cornerstone with Sickle and Hammer. Dabble prefers retaining Phoenix Ash’s value penalty over converting the first break into damage.

Sickle and Hammer is described as setting each outcome’s base ticket count to five. Dabble expects fewer break tickets and more great opportunities, alongside other changes to the base distribution.

After equipping it, the board display causes some confusion. The useful instruction is to inspect the resulting counts and displayed chance yourself rather than assuming the swap changes only breaks. Dabble judges the reduced break chance worthwhile, but soon has to scramble to secure tribute value.

Prepare for the holy relic transition

Dabble proposes farming toward 100 total tickets before trying the holy setup. That is a chosen experiment target, not a confirmed activation requirement. The supplied transcript reaches 86 tickets before ending.

The later discussion centers on Dawn Scabbard and a broken holy sword component. The inheritance effect is described as passing 40% of a broken sword’s enhancements to the next unforged +0 sword. The accompanying description mentions forced frenzy charges, but the explanation is incomplete.

The critical compatibility problem is the +0 recipient requirement. Lifetime Contract supplies +7 swords, so the existing farming engine does not provide the recipient Dabble needs.

Before attempting that transition:

• Secure a tribute sword first.
• Finish any farming you want from the available +7 stock.
• Reconsider Lifetime Contract so the setup can receive a qualifying +0 sword.
• Check the complete relic descriptions before committing.

Dabble also considers removing Supply Permit and Undertaker’s Ledger to free slots. Those are proposed changes, not a completed final build. The transcript does not establish the holy pair’s full combined behavior or demonstrate reaching +99.

6. FAQ

Does this method guarantee a +99 sword?

No. Dabble aims for +99, but the supplied transcript ends during preparation. It demonstrates permanent-ticket farming and identifies a holy-setup compatibility problem without showing the final result.

Why keep damage tickets if damage hurts sword value?

They still add a non-break outcome to the board, reducing the relative share of break tickets. The tradeoff is that damage can interfere with value growth, which becomes a noticeable problem during the run.

Why does Lifetime Contract conflict with the holy inheritance plan?

Lifetime Contract issues +7 swords, while the inheritance effect discussed requires the next unforged sword to be +0. Dabble realizes the existing supply setup must be reconsidered before that interaction can work as intended.

Source: Dabble’s Forgetax run.