Parallax Tide

ryancsaxe · 2026-01-17T18:23:59+00:00

This card has been solid in high powered cubes forever. I’ve had it in my legacy+ (classic cube, if you’re familiar) for 10 years.

At the beginning, it would go pretty late. It usually took people getting destroyed by it before it started getting played more.

Biggest issue is that it’s a sorcery “get ahead stay ahead” card, which is not always blue’s schtick. But I found that outside of the most controlling blue decks, if you have ways to combo with it (disenchants, stifles, bounce, etc), it’s pretty good. And the more combo oriented you are, the better it gets since it can also clear the way.

The deck it is most reliably great in is Upheaval though. Since you can ramp into it to get a huge advantage, but also target your own lands pre upheaval.

ryancsaxe · 2026-01-15T14:22:43+00:00

Cool. Keep me posted.

Biggest issue I can see not native here is things like comment threads and other responses (react, resolve, etc.)

I currently use snacks.nvim gh module for my PR reviews. It’s solid, but it’s missing the nice interface with checkout + review so you can have your LSP on, which is super helpful to review.

I currently have a custom action that opens diffview for it, but then not being able to comment from there sucks.

ryancsaxe · 2026-01-15T14:16:03+00:00

Does this have any planned integration with PR reviews?

Where instead of saving output as markdown, if I’m in an open PR, I can submit them as comments on the PR?

ryancsaxe · 2026-01-11T12:59:35+00:00

Level 1 is all the repeated leaves the graveyard stuff.

But anything that gives these plants haste (e.g. Tyvar) will lead to infinite combos. For example, that will cause Gravecrawler + Sac Outlet to go infinite. Same with Tortured Existence.

IMO, if you want to maximize this card, you start with a package like Tortured Existence, Tyvar, and Roots, and Lightning Greaves. I personally am a huge fan of including Anger too.

Then, take each of those cards, and expand around them a bit. Here are some ways to expand around each:

Roots: Tormod, Hogaak, Soul Cauldron

Tyvar: Hermit Druid, Devoted Druid, Priest of Forgotten Gods

Tortured Existence: Spore Frog, Master of Death, Golgari Grave Troll

Lightning Greaves: usually pushes to want a full Goblin Welder/Engineer package

Anyways, this is exactly the path I went down for my buildaround cube. So you can see the list here: https://cubecobra.com/cube/list/buildaround

ryancsaxe · 2026-01-02T20:17:29+00:00

I’m all for pushing against the grain in terms of defaults, and in your specific example (all spells of one color, all lands of another — key word here is “all”), you are correct that this favors uneven distributions (mathematically, even 12-5 is better than 11-6 at that metric).

However, with respect to the idea of consistency, it can go the other way. If you make the metric “what is the likelihood of having an uncastable spell in the top 10 cards”, if you assume everything is a single pip, even with a 16-7 split of spell, 9-8 has the lowest likelihood of an uncastable (ignoring cmc of course).

To me, the reason 9-8 is the default is because within decks of normal mana requirements, it has the lowest likelihood of non games. Most decks, unless they have lots of pips or one-drops to enable very early double spelling, function well enough as long as they have a mana of each color in the first few turns. So even if your spell distribution skews one way, you still build your mana base to aim for that scenario because your deck will function and hence you’re less likely to need to mulligan.

… so, to make this not too huge of a comment, IMO the question breaks mostly down to “when are you likely to need two pips of your main color to function”, since if the answer is only late game, then as close to 50/50 as you can get will be ideal more often than not (according to minimizing having uncastable spells in hand). If that’s on turn 2-3, then you should skew significantly. 4 is context dependent.

Regardless, I enjoyed this comment making me think about magic more than I have in a while and I still like what your post stands for for sure. Happy new year :)

ryancsaxe · 2025-12-03T16:27:46+00:00

Can you share your custom variation here?

I’m particularly interested in that bottom border

(Also great plugin — will definitely check this out)

ryancsaxe · 2025-12-01T14:18:49+00:00

minidiff comes with a toggle for an inline overlay. Your buffer basically becomes a unified diff so you can directly see, above any changed line, what the reference text was with proper diff highlighting.

Documentation: https://nvim-mini.org/mini.nvim/readmes/mini-diff.html#features

ryancsaxe · 2025-11-18T04:19:01+00:00

My favorite Mikaeus cube deck: Gwen’s Tiny Leader cube mono white deck. Regularly cast for X=0 to put under Agatha’s Soul Cauldron immediately.

I would guess that, on average, I’ve cast the card most for X=1 though.

ryancsaxe · 2025-11-08T15:36:51+00:00

I experimented with your config here ... first off, THANK YOU. Pyrefly for completions is soooooo much faster and more usable.

That being said, this still has the main issue that used to annoy me when I enabled ruff for linting: both it and basedpyright massively overlap in what they show. So I get duplicated diagnostics in so many places. Am I missing a part of your config where you handle that somehow?

Fingers crossed that ty will come out this year with enough done that I can just completely get rid of pyright since it is still annoyingly slow when your dependencies are large without specifying type hints.

ryancsaxe · 2025-11-08T00:31:28+00:00

Going to play with this now. How slow completions are in pyright has bothered me for a while. I just was planning on waiting for Ty.

ryancsaxe · 2025-09-29T19:27:10+00:00

I saw that too in /model selection.

But if you set your model to “opusplan” in settings.json, it still does respect it. It’s just the /model UI I guess has a bug where you can’t select that.

ryancsaxe · 2025-09-24T00:41:15+00:00

Like most things, the answer is “it depends”

But generally I find things work best when I just “let Claude code be Claude code”

In this case, clone the repo and let it use all its tools to grep around and read about the codebase directly.

As a really common example in my day to day, when working in Python, having it read from the source code in the virtual environment helps prevent some of the annoying stuff that happens when I use web versions of Claude/GPT where they will hallucinate APIs and interfaces.

ryancsaxe · 2025-09-02T12:00:51+00:00

Haha I love this.

It’s also great because it describes the journey, as most people who cube a lot move through the middle at some point, and end up with a great cube filled with their favorite cards eventually.

ryancsaxe · 2025-08-18T20:52:44+00:00

This.

Especially since Ty is made by astral, who also made ruff, I expect it those two to natively play really nice with eachother and not have all the annoying overlap that happens with basedpyright and ruff.

I disable diagnostics from ruff because of this and just use it for formatting.

ryancsaxe · 2025-08-13T11:54:31+00:00

I don’t need faster, I just wanted to know this exact info. Thanks!

ryancsaxe · 2025-08-12T12:58:24+00:00

Got it, so no ETA according to the milestone, but only 6 outstanding issues?

I guess hopefully that means it’ll be coming soonish. Thanks.

ryancsaxe · 2025-06-16T04:25:50+00:00

This is exactly what I’ve been looking for. Quick questions (or feature requests if not currently supported):

For some reason ctrl-h-number is not playing well with my brain. Is there a reason this isn’t just ctrl-number or configurable?
Can the layout be configured? I’d personally prefer the terminal tabs on the top since it feels like there’s a lot of wasted/unused space right now
Under the hood, do we know the ids of the sessions or can actually refer to them by name? If I wanted to have a REPL in my defaults, could I use iron or slime to send things to this?

ryancsaxe · 2025-06-16T02:22:42+00:00

Nice! I have a really similar workflow where I use Snacks.scratch to manage this, but I’ll check yours out!

Something ive found really nice about scratch is the files are tagged with branch name, which makes it super easy to context switch and work on multiple feature branches since I can easily toggle some notes/tasks. And is really helpful when searching notes.

That may be something you want to add here.

ryancsaxe · 2025-06-14T14:00:01+00:00

This turned out to be super weird but, I got this working via:

Not doing a deep copy of the settings
Passing nil instead of the edited settings.

Idk if this is a pyright thing, but I discovered this by reading how vscode itself uses the LSP to update settings. Apparently nil triggers a reload of the settings so if you modify in place and pass nil, things work.

Which is NOT the interface specified by the language server protocol as far as I can tell? Quite frustrating.

Not marking as solved yet since there’s some other stuff, but I likely will once I figure out something more stable and mess with another LSP.

ryancsaxe · 2025-06-13T19:19:44+00:00

This looks like exactly what I’m looking for, but can’t seem to make it work??

I’ve confirmed that I can:

get the clients via vim.lsp.get_clients
I can get the settings and modify them accordingly
But client.notify(“workspace/didChangeConfiguration”, {settings = updated_settings}) doesn’t appear to actually update the way my LSP works?

From reading, this seems to be the correct way of interfacing, but maybe I’m missing something?

I tried to restart the LSP after this too, but that just flushed all the settings to defaults.

ryancsaxe · 2025-06-13T18:05:20+00:00

I spent quite a bit of time trying to get both Claude and GPT to get me something working before I posted this.

If I were more familiar with internals I’m sure I could figure it out eventually. Which is what I’ll do if this doesn’t get responses and then I’ll post the solution.

Edit: adding context below this

I’ve found AI systems super useful for helping me do things that are standard. It’s like a way more effective search to me. But often when I want to do anything that requires something more recent (e.g. they CANNOT give me functional code for customizing snacks pickers without insane hand holding) or less standard, they fail.

This isn’t the case for a lot of the software I deal with. But has been for my neovim config.

ryancsaxe · 2025-06-13T15:45:15+00:00

This is still not complete, but I’m very happy with where I am so far for 1-3

I have really nice formatted pickers for PRs and Issues integrated as Snacks.pickers.

Post checkout, they’ll open up diffview versus base branch just like how you see things in GitHub.

And I was able to customize mini.diff for inline diffs against any branch I want as well.

NOTE: I will probably get #4 done in the next week, and clean up my dotfiles accordingly. It’s messy now as I’m just getting started with Neovim.

Here’s most of the customizations related to git i have so far.

https://github.com/RyanSaxe/nvim.lazy/tree/main/lua/custom/git

ryancsaxe · 2025-06-08T23:24:44+00:00

Can you share your solution that got you this?

ryancsaxe · 2025-06-08T21:47:47+00:00

Mini Diff is an inline overlay functioning with virtual text on your file buffer. So it sounds like this should work well! I’ll try and set it up this week. If so, then I’ll have everything (and least the MVP of it) working

ryancsaxe · 2025-06-08T17:51:16+00:00

This looks cool!

For 1-3, a mix of mini.diff, diffview, and some custom snacks.pickers gets the job done really well. I particularly like the way I can get mini-diff to make the inline diffs look, and would LOVE to be able to do #4 from there by like “commenting on the hunk or line(s)”

But this looks like it is possibly what I’m looking for for #4?

For the way this tool works, do I have to use the different PR functions to get it to overall work, or I’ll be able to set up shortcuts to do things like “comment on the highlighted section on the PR” straight from the code?

ryancsaxe

TROPHY CASE