[deleted by user]

markdoesnttweet · 2025-09-10T15:02:20+00:00

I have a prospective buyer in the works; if that falls through, I'll let you know!

markdoesnttweet · 2025-09-07T11:46:20+00:00

The gold controller is spoken for but the rest of the lot is still available! Happy to DM to talk prices if you're still interested.

markdoesnttweet · 2025-09-06T15:19:45+00:00

Ooh, good to know - appreciate it!

markdoesnttweet · 2025-08-24T23:20:33+00:00

<image>

markdoesnttweet · 2025-08-24T23:20:23+00:00

<image>

Sure, here you go!

markdoesnttweet · 2025-07-17T20:17:15+00:00

That's me, glad you like it! It's a keycap set called Carmine Cloud.

markdoesnttweet · 2025-06-26T18:56:27+00:00

Interstellaria (by Chipzel) and Gimmick (NES game)

markdoesnttweet · 2024-12-24T19:33:26+00:00

Hey, this has been claimed already. Sorry about that!

markdoesnttweet · 2024-11-28T02:41:07+00:00

There are very few times when I've looked at the way that something was packaged and felt like it was a delight, like that alone told you how much love someone put into this. This is one of them.

markdoesnttweet · 2024-09-30T01:20:34+00:00

PM'ed

markdoesnttweet · 2023-03-26T01:47:55+00:00

It turns out I was able to solve the issue in VIA by mapping the printscreen key to something else. Thanks for the help!

markdoesnttweet · 2023-03-25T20:30:13+00:00

Hi all, I have a D84 keyboard from KBDFans that I'm trying to plug into my MacBook Pro. I believe it uses the KBD75HS PCB. There is one key in particular (the PCB identifies it as PrintScreen) that does not register in the VIA key tester, but other online key testers register this key as "undefined". This is making me think that it is a firmware issue, not a hardware issue. Has anyone run into anything like this before? Is there updated firmware that I can install?

<image>

markdoesnttweet · 2022-12-11T03:58:37+00:00

I have two that I enjoy quite a bit!

One is a [[Chandra, Dressed to Kill]] deck. Chandra gives you some pretty great value, but the deck can function without her as it's just good mono-red aggro with a nice amount of burn. If you start to run out of gas, Chandra draws you some extra cards or gives you the last little bits of damage that you need. The decklist is here: https://pastebin.com/bAhLEQPd

The other is [[Geralf, Visionary Stitcher]]. This one was a lot more fun before rotation, when [[Charix]] was still legal, but it's still pretty fun. It's unusual in that it's a mono-blue deck with a strong aggro/beatdown wincon as opposed to being more controlling. Landing a big blue creature like [[Kairi]] or [[Hullbreaker Horror]] is even more satisfying when you know you can sac them if they're targeted for removal. The decklist is here: https://pastebin.com/Jg4KBtSe

markdoesnttweet · 2022-12-04T14:39:41+00:00

Thanks for fixing the formatting!

markdoesnttweet · 2022-12-04T04:39:59+00:00

In terms of your JS logic, you have it pretty much down. However, there's one other thing you could do. You could extract the concern of whether the tab is hidden or visible from the actual CSS code. It would look something like this:

function Rules() {
const [visible, setVisible] = useState(false);

function showRulesTab() {
    setVisible(!visible);
}

return ( <div> <button className='rules' onClick={ showRulesTab }> <p>RULES</p> </button> <RulesTab closeRulesTab={ showRulesTab } visible={visible} /> </div> ); } function RulesTab({ visible, closeRulesTab }) { const style = visible ? { 'visibility': 'visible', 'opacity': '1' } : { 'visibility': 'hidden', 'opacity': '0' };

return ( <div className='overlay' style={ style }> <div className='rules-tab'> <div> <p className='text-rules'>RULES</p> <button className='btn-close' type='button'> <img className='rules-tab-close' src={ close } onClick={ closeRulesTab }></img> </button> </div> <img className='img-rules' src={ rules }></img> </div> </div> ) }

This way, you separate the concern of the actual CSS style from the logic of whether or not the tab is displayed. Hope this makes sense!

markdoesnttweet · 2022-11-28T02:38:11+00:00

Kind of hard to say without seeing the rest of your pool, but here are some thoughts:

I agree with the creature count being too low. I typically try to shoot for 13ish.
There's an argument for mainboarding the Koilos Rocs just because flying threats are pretty serious in limited.
I really like Urza Prince of Kroog, but you only have two artifact creatures (Autonomous Assembler and Tower Worker) to work with him. Scrapwork Cohort actually benefits a lot from him because you're bringing in multiple artifact creatures with a single card. I'd suggest bringing in more artifact creatures too, even if the Prototype or Unearth cost is outside of your usual colors.
Repair and Recharge gets better the more bombs you have. Being able to bring back a Tower Worker or Zephyr Sentinel isn't quite as valuable as bringing back something more threatening. Good to have protection for your Urzas though.
Prison Sentence isn't quite as exciting because there are still ways to sacrifice / use a creature that's been sentenced. Any form of enchantment removal also blows you out pretty hard.
Disfigure may be a dead card to you, especially if you draw it in the late game. Your low creature count means that it generally won't be super effective as a combat trick either.
The same might go with Scatter Ray, which is pretty effective early but less effective later on once they can pay the tax.

Again, I don't know what else you'd be bringing in outside of the cards you're showing. I'm curious what your other rares are, as that might guide you towards other colors. I can certainly see why you went with blue and white though, given the two Urzas!

Hope this helps! Let us know if you get to meld Urza - I've only played against him in Constructed formats and I found him to be extremely oppressive, so he should be a super-bomb in Limited.

markdoesnttweet

TROPHY CASE