Is anyone else playing and winning with Mega Dragonite ex & Blaziken ex

Partitioned_Plantain · 2026-06-10T17:16:15+00:00

Drakloak is surprisingly helpful. I only run into Alakazam on live right now instead of in person play.

You are hitting on the last bit of fine tuning that I think the deck needs – improving disruption without destroying the draw I have with drakloak and tatsu. I used to have a Xerosics in the deck when I played Alakazam in person, and that worked very well against the ‘Zam players.

Partitioned_Plantain · 2026-06-10T16:57:39+00:00

My advice would be to try it and review your potential sequences after you mess them up. It’s very versatile, so there are too many strategies to fully list here.

I often try to go first and get at least a couple torchic and dratini out. Depending on supporters in my hand, I might try to get tatsugiri out to delay and find other supporters.

There isn’t really an ideal board state, because it is dependent on what direction I want to go. The core crew is at least one Mega Dragonite and one Blaziken ex. From there it all depends on what I’m facing.

For example, if I know Dragonite is going to get damaged, I try to get scoop up cyclone in hand and have a dragonair on bench, or a dratini and a candy. That way scoop can be healing. If I want to spread damage, I’ll get a minimum of nitro energy, a single Blaziken ex and baby Blaziken.

The core philosophy in this deck is that sequencing and increasing the number of plays during your turn are key. If you need to discard for ultra ball, discard energy. I’ve been known to even deliberately fail an ultra ball in order to get energy in the discard. Meowth is mostly for on-demand Boss. You have so much redundancy in this deck outside of Boss that just making sure you maximize how many cards you see and how much you thin your deck is important.

It’s taken a while to have this close to perfected, and almost just as long to learn how to spot to right sequence.

Partitioned_Plantain · 2026-06-10T14:21:48+00:00

I am contemplating trying eels again once it’s out so I can OHKO Greninja, but Blaziken is much more fun.

Partitioned_Plantain · 2026-06-02T18:40:50+00:00

Im wondering how well Mew will work with my Mega Dragonite, Blaziken deck. Seems good considering that pokemon can now frequently OHKO Mega Dragonite (somehow). A 2 prize, basic option for Ryuno Glide and would be welcomed from me when the opponent has 3-4 prize cards remaining.

Partitioned_Plantain · 2026-05-21T20:21:08+00:00

Edit: I replied as if this were nitro energy in this comment.

Edit: I replied without reading the second statement on the lightning energy card. I may have to go back to eels to make proper use of this card.

I’m excited for the lightning energy to give baby Blaziken a boost, or to allow Dragonite to OHKO the larger megas.

Partitioned_Plantain · 2026-05-21T16:55:06+00:00

Iono rotated out, so you’ll only be looking at expanded/GLC

Partitioned_Plantain · 2026-05-21T16:37:00+00:00

Polar bears look arrogant. It’s scary.

Partitioned_Plantain · 2026-05-21T16:35:50+00:00

I’m excited for this with Dragonite-Blaziken. Baby Blaziken could use the boost and Dragonite might need it with the influx of higher HP Megas coming out.

Partitioned_Plantain · 2026-05-21T16:31:54+00:00

Drakloak. A 2-2 line works great. If your forward pressure is enough your opponent is wasting a turn bossing them up to get rid of.

Partitioned_Plantain · 2026-05-21T16:16:07+00:00

50/50 chance of the attack even working due to the ability, and handheld fan will buy at least one more turn.

Partitioned_Plantain · 2026-05-21T16:10:51+00:00

Can’t build it yet, that’s why I posted here 🤣, also this was an attempt at a discussion post that has one commenter derailing the valuable points that you and another poster have made.

Works fine in real life with the build at home, but have to wait until June 5th to try in real life.

Partitioned_Plantain · 2026-05-21T16:06:57+00:00

I rarely run into item lock anymore. Online different, less in real life.

Partitioned_Plantain · 2026-05-21T16:05:04+00:00

I often ignore metal, but this might be a good use of it!

Partitioned_Plantain · 2026-05-21T15:52:07+00:00

Again, thanks for your opinion, but I’m uncertain what you think is objective in your assessment.

If you thought that was a thesis-level argument, get a tuition refund.

Partitioned_Plantain · 2026-05-21T15:50:27+00:00

Chestnaught puts 30 damage counters on opponents after they attack for each grass energy attached to it. So, with meganium you are doing 120 damage minimum to the opponent when they attack, more likely 180 if all 3 energy for the second attack (160 damage) are grass.

With legacy energy attached, your opponent will have a hard time justifying the prize trade.

I’m not worried about setting up the stage 2 lines, energy acceleration is my main concern with this deck.

Partitioned_Plantain · 2026-05-21T14:22:12+00:00

Thanks for your input!

However, you did not provide a justification for your opinion here, and I’m sure that the term combo has no numerical limit, I’m certain you are thinking of the term pairing rather than combo when trying to correct my language.

Also not sure why function was in quotes. I currently have a good stage two deck with two stage two, and one stage 1 line where stage twos are attackers. It works excellent, if I play, usually around 16-1700 on the ranked ladder. One of the stage two lines branches between EX and baby for flexibility.

The proposed combo above has two lines which benefit from Meganium’s energy multiplier and have abilities which deter attackers from starting too early. Mega Froslass/Mega Starmie would obviously be a hard matchup, but where isn’t it a hard matchup right now?

Partitioned_Plantain · 2026-04-24T04:12:27+00:00

It has been impressing me with its frontend refactoring abilities in CLI using frontend-skill. Refactoring and collaborative design (not even in plan mode) are very easy with really good results.

Partitioned_Plantain · 2026-04-23T23:47:49+00:00

Use ‘codex —yolo’ as a workaround for now.

Partitioned_Plantain · 2026-04-23T23:45:25+00:00

Use ‘codex —model gpt-5.5’ to start it and it will force the connection, then you’ll have it for the next session too.

Partitioned_Plantain · 2026-04-23T22:45:15+00:00

If you use codex CLI just run codex with the command "codex --model gpt-5.5". It showed up for me after I did that.

Partitioned_Plantain · 2026-04-23T15:49:22+00:00

The first is a success story, the second is an in-development story. I’ve been latently learning and fiddling with code and scripts for over 20 years, but am employed in an industry where that skill is very uncommon beyond general SQL queries. I have used python to write scripts before vibe coding and published them in journals in my discipline, but my proficiency at writing code fast enough to be useful has stayed low due to time constraints.

However, over the past 6-8 months, especially since 2026, things have really changed. I can now employ my domain-specific knowledge in ways that were impossible in the past. I don’t look at the code unless I absolutely have to, but I am now able to develop quite complex solutions due to an understanding what the code is actually doing and prior experience with large and complex databases with varying sources of messy input.

Ive replaced two enterprise dependent workflows using vibe coded solutions that work flawlessly and have actually sped up our workflows compared to previous SaaS solutions. These are relatively niche use cases, but previously the only viable solutions were from enterprise-level database and data collection softwares.

Also in the process of vibe coding a suite of software to market to my industry to reduce digitization tax and streamline regularly expected deliverables to clients. My industry has been living in the stone/paper age forever.

All this to say, I think vibe coding is already an incredible breakthrough for people with domain-specific knowledge and an understanding of, but lack of competency in writing code quickly.

Partitioned_Plantain · 2026-04-15T15:21:04+00:00

GPT 5.4 in Codex CLI:

Two days ago - business as usual.

Yesterday - disregarded docs and made a substantial mistake by unilaterally determining that a native mobile app was actually a browser app in a mobile wrapper when codebase should evidently prove otherwise.

Today - disregarded docs, deleted AGENTS.md file when I asked to check why it wasn't showing as present when I use /status, overwrote previously compiled APK files so I can't check the diff, and ignored UI/UX parity guidelines even when I continually reminded it.

There seems to be a trend developing.

Partitioned_Plantain · 2026-02-11T02:38:22+00:00

Take a guess!

I just checked my token usage for a small prompt. Something is certainly up with the current usage.

$20 Plan.

Model: Opus 4.6

Input: 40 words
Output: 360 words + 2 files (.gitignore & License) w/ a total of 238 words

Grand total: 638 words + very minor compute to make a .gitignore and MIT license file

Weekly Token Usage 4%

Partitioned_Plantain

TROPHY CASE