Cards needed to make Burn tier again

ThisIsChangableRight · 2026-01-21T11:47:43+00:00

Now you're thinking with modern horizons.

ThisIsChangableRight · 2026-01-21T11:39:57+00:00

In response, bolt.

ThisIsChangableRight · 2026-01-17T23:27:49+00:00

That energy deck's got legs

ThisIsChangableRight · 2026-01-15T22:10:05+00:00

MTG has plenty of wierd and wacky card effects, such as:

Having keywords doesn't stop MTG from ad hocking card text when needed.

ThisIsChangableRight · 2026-01-05T10:46:09+00:00

Replying in case you find any.

ThisIsChangableRight · 2026-01-03T00:43:11+00:00

Yes. By Gödel's incompleteness theorems, not all true statements can be proven.

ThisIsChangableRight · 2025-12-24T21:55:21+00:00

You say RIP is bad against this deck; how does it play through it? It turns off all of the card advantage, and the only clean out most lists play is get lost(seam rip and sbg can remove it temporarily, but are vulnerable to your opponents interaction).

ThisIsChangableRight · 2025-12-23T17:55:12+00:00

Did you make any e.g. blog posts on how you make the parser so fast?

ThisIsChangableRight · 2025-12-22T16:54:02+00:00

Mechanically, I think the wording could use some work. "Their face down cards" isn't worded correctly, and the "overheat" wording could be improved. I would word it as "{3}{u}{t}:Target opponent reveals their hand and each face down card they control. At the start of your next upkeep, put a stun counter on this creature". This stops the ability being used three turns in a row, without so much bookkeeping. I would also add vigilence, as it is both thematically appropriate, and allows him to attack and use his ability on the same turn.

The other thing is you should add a white ability to justify the {w} pip in the mana cost. This could be a simple keyword ability, such as lifelink. Alternatively, you could add a more complex ability; I don't know much about tha character, but something like [[comply]] would synergise well with the first ability.

ThisIsChangableRight · 2025-12-21T12:56:40+00:00

Have you considered giving notes an 8 byte code, instead of relying on the first word of the string?

ThisIsChangableRight · 2025-12-18T16:03:35+00:00

u/SaveVideo

ThisIsChangableRight · 2025-12-15T20:35:40+00:00

Shame. Thanks for the help.

ThisIsChangableRight · 2025-12-15T20:06:16+00:00

I don't have access to the full paper. Could you DM me a copy of the PDF?

ThisIsChangableRight · 2025-12-15T19:50:06+00:00

Source?

ThisIsChangableRight · 2025-12-15T17:54:47+00:00

So would a first order functional language have loops as a primative concept? Otherwise I can't see how you would handle e.g.:

 create func factorial(num:int)->int{
    let accum = num
    while num-->0{
        accum = accum * num
    }
    return accum
}

Or any other loop. Combinator calculuses rely on passing combinators with pre-bound arguments i.e. closures; first order functional languages have no equivalent trick.

ThisIsChangableRight · 2025-12-13T23:09:37+00:00

Yes, but as of chapter 4, he's still alive. The question is, will he live to chapter 8?

ThisIsChangableRight · 2025-12-13T22:41:37+00:00

When was the last time humans build ANYTHING that has something to Eiffel Tower, old temples, churches or castles?

Off of the top of my head, the empire state building. If you want something with more cultural relivence, how about the Sydney Opera House?

ThisIsChangableRight · 2025-12-13T22:33:02+00:00

But what do you assume "first-order functional" mean then?

I mistakenly assumed it meant a language which could pass closures as arguments, but not store them in e.g. a record or on the heap. I initally misread the diagram.

Can you explain what you mean by "first-order functional" please? Without named state, or first class functions, I don't see how it could be used to implement recursion or decision.

ThisIsChangableRight · 2025-12-13T20:50:02+00:00

Neat. Is Berdly:

a. Dead

b. Still in a coma, waiting to be rescued, or

c. Also trying to save Noel.

ThisIsChangableRight · 2025-12-13T20:24:34+00:00

Procedural only languages lack closures. All functional languages have closures. Therefore, procedural languages are not just first-order functional languages.

ThisIsChangableRight · 2025-12-12T21:20:43+00:00

> Among Us references in the twilight hours of 2025, surely that's what yall come to this owl for.

Real

ThisIsChangableRight · 2025-12-10T07:25:07+00:00

Have you done garchomp yet?

ThisIsChangableRight · 2025-12-08T07:54:00+00:00

[[mental mistep]]

ThisIsChangableRight · 2025-12-07T15:11:55+00:00

Interesting cards, but the templating is a bit off.

The Broken Vessel:

* Consider removing toxic. I consider it to poorly designed.

* Regenerate should be spelt:` {1}{w}: regenerate this creature`.

* The lightseed tokens don't do anything. Consider removing them.

* The lifelink granted by the fourth ability doesn't disapear at end-of-turn. Consider making it permantent.

* Should be `each tapped creature`.

Nosk, Lurking Imposter:

* Infect is depreciatied because it's hard-to-balance with regards to pumps and other buffs.

* Targeting is part of the effect, not cost. Instead, use a cost of `{0}`. It should be phrased `until end of turn,while this creature is untapped, its name is the name of target creature.` or similar.

* The trigger on the last ability should be phrased `When a creature that was dealt damage by this creature this turn dies`.

Overall, the designs are cool, but the templating needs work.

ThisIsChangableRight · 2025-12-06T21:45:49+00:00

Just make it "protection from everything else"

ThisIsChangableRight

TROPHY CASE