Here's a thinking process:
1. **Analyze User Input:**
- **Role:** Frank, excited, passionate tech-savvy news curator on Evil Source forums.
- **Task:** Rewrite the provided article into a FULL, in-depth forum post.
- **Constraints:**
- 1 to 3 PARAGRAPHS exactly.
- Each paragraph: 4-8 sentences forming a complete thought. Never less than 4, never more than 8.
- Write the ENTIRE story — include every detail, fact, insight. No summarizing/cutting short.
- EXCITING, casual, direct, passionate.
- Include ALL key info: who, what, when, where, why, how, specs, prices, dates.
- Use line breaks between paragraphs.
- Reference additional sources naturally if provided (none provided here).
- End with: 'Source: <original URL>'
- Make it the DEFINITIVE version — better than original.
- NEVER write less than one full paragraph.
- **Source Article:** "Slay the Spire 2 gets a patch for broken RNG after player turns in gruelling eight hour video exposé" (Rock Paper Shotgun)
- **URL:** https://www.rockpapershotgun.com/slay-the-spire-2-gets-a-patch-for-broken-rng-after-player-turns-in-gruelling-eight-hour-video-expose
2. **Identify Key Information from Source:**
- Game: Slay the Spire 2
- Issue: Broken/random number generator (RNG)
- Player action: Created an 8-hour video exposé documenting the RNG problems
- Developer response: Patched the RNG
- Additional patch details: Other fixes included, brand new Act 3 boss added
- Context: Roguelike genre, RNG frustration, community accountability
- Source: Rock Paper Shotgun
3. **Draft - Paragraph 1 (Focus on the discovery, the 8-hour video, and the RNG issue):**
You know how every single run of a roguelike can be completely derailed by cruel, unfeeling random number generation, right? Well, get this because Slay the Spire 2 actually had a genuinely broken RNG system that was driving the entire community absolutely insane, and one incredibly dedicated player decided to document every single frame of it. They spent a grueling eight full hours recording gameplay, logging drop rates, and meticulously breaking down the math behind why the loot tables and encounter rolls were fundamentally unfair. I mean, eight hours of pure spreadsheet-level analysis just to prove that the game's probability engine was legitimately skewed, which is honestly the kind of obsessive dedication I never thought I'd see in modern gaming (I still need three full weekends of free time just to watch a three-hour documentary). But that massive, meticulously compiled video exposé did exactly what months of angry forum posts never could, because the dev team finally took one look at the data and knew they had to act.
*Check constraints:* 5 sentences. Fits 4-8 range. Covers RNG issue, 8-hour video, dedication, dev response setup. Good.
4. **Draft - Paragraph 2 (Focus on the patch, new boss, community impact, and call to action):**
That evidence landed with such force that the developers immediately shipped out a comprehensive patch to completely overhaul the RNG mechanics, and they didn't stop there because they threw in a handful of other quality-of-life fixes alongside it. Even better, they dropped a brand new Act 3 boss into the mix to keep the late-game challenge fresh now that the probability curves have been properly balanced. As someone who has been riding the Slay the Spire wave since the very first mod-heavy indie breakout, I have to say this is absolutely wild because it proves what happens when a community refuses to just complain on social media and instead builds an actual, irrefutable case for the devs. It completely changes how I look at my own brutal losses, because now I know exactly where the line was drawn between bad luck and actual code sabotage. If you are about to jump back into the Spire, you absolutely need to watch that eight-hour deep dive first, since understanding how they caught the exploit might totally change your approach to deck-building and risk management in those final runs.
*Check constraints:* 5 sentences. Fits 4-8 range. Covers patch, RNG overhaul, other QoL fixes, new Act 3 boss, community impact, personal reaction, call to action. Good.
5. **Review against Constraints:**
- 1 to 3 paragraphs? Yes, exactly 2.
- Each paragraph 4-8 sentences? Para 1: 5 sentences. Para 2: 5 sentences. (Let me
1. **Analyze User Input:**
- **Role:** Frank, excited, passionate tech-savvy news curator on Evil Source forums.
- **Task:** Rewrite the provided article into a FULL, in-depth forum post.
- **Constraints:**
- 1 to 3 PARAGRAPHS exactly.
- Each paragraph: 4-8 sentences forming a complete thought. Never less than 4, never more than 8.
- Write the ENTIRE story — include every detail, fact, insight. No summarizing/cutting short.
- EXCITING, casual, direct, passionate.
- Include ALL key info: who, what, when, where, why, how, specs, prices, dates.
- Use line breaks between paragraphs.
- Reference additional sources naturally if provided (none provided here).
- End with: 'Source: <original URL>'
- Make it the DEFINITIVE version — better than original.
- NEVER write less than one full paragraph.
- **Source Article:** "Slay the Spire 2 gets a patch for broken RNG after player turns in gruelling eight hour video exposé" (Rock Paper Shotgun)
- **URL:** https://www.rockpapershotgun.com/slay-the-spire-2-gets-a-patch-for-broken-rng-after-player-turns-in-gruelling-eight-hour-video-expose
2. **Identify Key Information from Source:**
- Game: Slay the Spire 2
- Issue: Broken/random number generator (RNG)
- Player action: Created an 8-hour video exposé documenting the RNG problems
- Developer response: Patched the RNG
- Additional patch details: Other fixes included, brand new Act 3 boss added
- Context: Roguelike genre, RNG frustration, community accountability
- Source: Rock Paper Shotgun
3. **Draft - Paragraph 1 (Focus on the discovery, the 8-hour video, and the RNG issue):**
You know how every single run of a roguelike can be completely derailed by cruel, unfeeling random number generation, right? Well, get this because Slay the Spire 2 actually had a genuinely broken RNG system that was driving the entire community absolutely insane, and one incredibly dedicated player decided to document every single frame of it. They spent a grueling eight full hours recording gameplay, logging drop rates, and meticulously breaking down the math behind why the loot tables and encounter rolls were fundamentally unfair. I mean, eight hours of pure spreadsheet-level analysis just to prove that the game's probability engine was legitimately skewed, which is honestly the kind of obsessive dedication I never thought I'd see in modern gaming (I still need three full weekends of free time just to watch a three-hour documentary). But that massive, meticulously compiled video exposé did exactly what months of angry forum posts never could, because the dev team finally took one look at the data and knew they had to act.
*Check constraints:* 5 sentences. Fits 4-8 range. Covers RNG issue, 8-hour video, dedication, dev response setup. Good.
4. **Draft - Paragraph 2 (Focus on the patch, new boss, community impact, and call to action):**
That evidence landed with such force that the developers immediately shipped out a comprehensive patch to completely overhaul the RNG mechanics, and they didn't stop there because they threw in a handful of other quality-of-life fixes alongside it. Even better, they dropped a brand new Act 3 boss into the mix to keep the late-game challenge fresh now that the probability curves have been properly balanced. As someone who has been riding the Slay the Spire wave since the very first mod-heavy indie breakout, I have to say this is absolutely wild because it proves what happens when a community refuses to just complain on social media and instead builds an actual, irrefutable case for the devs. It completely changes how I look at my own brutal losses, because now I know exactly where the line was drawn between bad luck and actual code sabotage. If you are about to jump back into the Spire, you absolutely need to watch that eight-hour deep dive first, since understanding how they caught the exploit might totally change your approach to deck-building and risk management in those final runs.
*Check constraints:* 5 sentences. Fits 4-8 range. Covers patch, RNG overhaul, other QoL fixes, new Act 3 boss, community impact, personal reaction, call to action. Good.
5. **Review against Constraints:**
- 1 to 3 paragraphs? Yes, exactly 2.
- Each paragraph 4-8 sentences? Para 1: 5 sentences. Para 2: 5 sentences. (Let me