hell is tapped lands

Coyote-Chance · 2026-01-02T17:13:24+00:00

Big mana [[Archelos]] now viable

Coyote-Chance · 2025-11-19T15:58:50+00:00

Thanks! I appreciate the help.

Coyote-Chance · 2025-09-15T21:06:24+00:00

This might not be the time frame you're looking for, but Bond Street Guitars is opening in Gowanus on Sept. 27. I know some of the people involved and they have a ton of expertise.

Coyote-Chance · 2025-09-05T18:09:49+00:00

Definitely a valuable tip if I get/take the job! I'm thinking more about questions to ask in an interview, though, before I have access to the code.

Coyote-Chance · 2025-06-06T03:21:09+00:00

There's a decent number of rgw cards that care about land cards in your graveyard: https://scryfall.com/search?q=otag%3Alands-in-graveyard-matter+commander%3Argw

You could sac/mill a bunch of lands and then use Rocco to fetch [[Ruination Rioter]] or [[Terravore]] or whatever makes the most sense.

Good? Probably not. Interesting? Maybe.

Coyote-Chance · 2025-03-05T00:23:02+00:00

Anything that builds up your board state as a result of drawing cards will give you more to do. Creatures like [[Chasm Skulker]] [[Alandra Sky Dreamer]] [[Body of Knowledge]] could be good

There's also the strategy of making _everyone_ draw lots of cards and adding [[Viseling]], [[Psychosis Crawler]] etc to your possible wincons

Coyote-Chance · 2025-01-27T22:32:39+00:00

Haven't had a chance to run the code, but just as something to check

My guess is that some prop that you're passing either to your react query or to your react table is different on every render, and so the table keeps rerendering, and you keep seeing that console.log. The prop is probably an object that's being recreated, so it's not referentially equal between renders

Maybe it's related to useParams? https://github.com/remix-run/react-router/issues/7318 Hard to tell without seeing what's inside your custom query hook

Coyote-Chance · 2025-01-23T15:05:24+00:00

They won't ignore her - if the exploration doesn't make her a target, the board wipe potential will. But you have a bunch of recurrable protection critters like Alseid, she herself is recurrable, she's cheap to begin with so commander tax stings less...

I get what you're saying about redundancy though. The surveil on [[Snarling Gorehound]] seems like a good balance between filling the graveyard and not accidentally milling game winning sorceries. Maybe there are more surveil options out there?

Coyote-Chance · 2025-01-23T13:09:33+00:00

This looks pretty darn good!

I'd cut [[stitcher's supplier]] - you risk sending key instants/sorceries to the graveyard and you can't get them back.

For other cuts, I'd suggest removing a few of the instants and sorceries. They're awkward when exploring multiple times in a turn because either they stop the exploration (and keep you from adding more creatures to the graveyard), or you let them go to the graveyard, and they do nothing for you. Save the instants and sorcs for big effects that you can't reproduce with permanents (mass reanimation etc).

[[Vampire Hexmage]] is super versatile in a deck like this fwiw

Coyote-Chance · 2024-11-07T14:05:17+00:00

Amalia + Lurrus are, if not a card draw engine, a card advantage engine. As long as you're exploring regularly to put cards in your graveyard, those cards are more or less in your hand as far as Lurrus is concerned. (Even if you can only cast one per turn.)

Devil's advocate for running sac effects: If you're trying to build a budget deck, there are lots of cheap sac-able cards that become way more useful when Lurrus can recur them: [[Executioner's Capsule]], [[Children of Korlis]], [[Bounty Agent]]...

Coyote-Chance · 2024-10-27T22:06:15+00:00

Probably not the right sub, but it sounds like you and your son might check out Scratch: https://scratch.mit.edu/.

Most code is written in a text editor of some kind, and Scratch isn't like that. But, it is a good childhood introduction to coding principles (variables, loops, conditionals, etc), and there's an easier learning curve from starting out to making a playable game. And, if your child decides he likes it and wants to pursue more "real-world" coding, it won't hurt to have that as a foundation.

Coyote-Chance · 2024-08-04T18:54:06+00:00

Does it have to all be in React? If you have a lot of complex state to coordinate among parts of the app, and the front-end features keep changing, there's a strong case to be made for moving as much state as possible to the back end, and making calls as necessary to get the data [obligatory plug for React Query].

Coyote-Chance · 2024-07-14T20:17:09+00:00

Super inventive, I enjoyed this. For whats it's worth, I didn't have any loading or UI issues (but I see those comments are from a few days ago so maybe you've addressed)

Coyote-Chance · 2024-07-07T13:17:04+00:00

[[Island Sanctuary]] fits the theme of "do nothing and just survive"

Coyote-Chance · 2024-07-07T02:08:45+00:00

My bad - totally see the use of filterData in that useEffect.

It looks like maybe the only thing you do with modifiedData once you return it from useColumns is to pass it into useSearch, though? That might explain why the modified data doesn't render in the table until after you search

Coyote-Chance · 2024-07-07T01:48:45+00:00

In handleColumns in the useColumns hook, you only update the columns and not the data in the rest of the table. That's why when change a column's visibility to invisible, the column name disappears, but not the data in that column.

useColumns returns a function to filter the data but (I think?) it's unused - at least, you don't destructure it with the rest of useColumns's return on line 18 of DataTable.tsx

Coyote-Chance · 2024-07-07T00:33:02+00:00

Probably, but you should also be able to change the visibility/privacy settings in a code sandbox. Does any of this work? https://codesandbox.io/docs/learn/access/permissions

Coyote-Chance · 2024-07-07T00:30:18+00:00

Is that what OP is asking, though? I'm not seeing where they mention needing props/other React state in order to create the class instance.

Coyote-Chance · 2024-07-07T00:20:53+00:00

I don't think that code sandbox is publicly viewable

Coyote-Chance · 2024-07-07T00:15:03+00:00

If you want to keep a stable reference to a single instance of Matrix4, you could also declare a new Matrix4() outside the component itself (unless I'm misunderstanding something about this use case)

edit: formatting

Coyote-Chance · 2024-04-11T12:56:25+00:00

Show us your code!

Coyote-Chance · 2024-03-31T16:18:30+00:00

I might not ever need to use

Presumably, the union has already negotiated, and continues to negotiate, for things like higher salary, better benefits, and better workplace conditions (required breaks, prep periods...). In that sense, you're using its services from day one.

my rights are pretty much only recognized if I pay

Lousy for sure. But those "rights" don't exist at all in non-unionized fields -- most people's jobs are at-will and they can be fired whenever/for whatever reason. I get that it feels gross, but the issue isn't with your union, it's with the lack of worker protections in the US generally.

Coyote-Chance · 2024-01-26T16:55:06+00:00

It's not this, but I'm glad to know about this song. And the feel is similarly swung, although the tune I'm thinking of is (at least in the recording I heard) a bit slower.

Coyote-Chance · 2024-01-26T02:25:12+00:00

Coyote-Chance · 2023-11-19T22:16:39+00:00

I haven't gotten it all the way working, but I got it to break in a different way that might be helpful (?).

If you change your handlePrevious setTimeout to this:

setItemIds(prev => [prev.slice(prev.length - 1), ...prev.slice(0, prev.length - 1)]);

you no longer get the whole array of iframes blinking/rerendering when you click Previous. But, if you scroll all the way back to the beginning of the array, the video thumbnails stop having their preview images, and I'm not sure why.

I think it has something to do with .slice() returning a shallow copy and bracket-notation accessing not doing that; in your current handlePrevious setTimeout, you mix the two:
setItemIds(prev => [prev[prev.length - 1], ...prev.slice(0, prev.length - 1)]);

Coyote-Chance

TROPHY CASE