RIP to my control, c, and v keys ):

they still keep the cool sickass cloaks right those things rock

FUCK NO.

Current issues:

• Private abilities are available to minors
• Corporations not forced to own trains

Writing

failIfNoFirstInvocation: unknown = true

I still need to make CI happy.

To my surprise, PIE isn't the default everywhere yet.

• 418 Teapot

Not overdue. Still QA on prod

Yes I had to restore a backup. 5385 slots hit the ground at once. The work around is to break the cable going to the SAP before breaking the SAP itself.

Should we do

large = 6

extra_large = 8

Changes look good to me, but I cannot verify that @doronbehar is true a human, so I will not merge this :smiling_imp:

Why would you make a test specifically to ensure that a flag is only one character on some shuttle text. Im so fucking scared rn. Let me see if I can find an 18+ icon thats like...one character.

Do you expect the combine to set cruise control and drive itself?

We use -Werror. Warnings are errors.

src/sirthreadpool.c(189): error C2220: the following warning is treated as an error

Claude said we should just

#pragma warning

Works for me when you don't stuff the corpse into the pit, which is definitely not what's intended, but it's a workaround for now.

Can I add a TODO instead of fixing it right here and now? In the next PR I'm going to operate on SLM anyway.

Fixed this, and also fixed the logic because I was originally returning the opposite of what the function name said. 🙃

Can you make this a config option please? i have a 100% invisible gameskin that i use for things like screenshots

however, of course this config must be enabled by default

Done, I'll release it ASAP (I was fast, just 3 years to do it!)

    ##Kill the target dramatically

Expected results

Scrolls through time.

hey so um these are prundles.. not… time machines… we’ll see what we can do.

I Was Elected To Lead, Not To Read ... Number twooo :-D

Did I read your restrictions on arguments? Yes

Did I ignore them coz they were dumb? Yes

I'll use

fatalError

@mohamed-rekiba Let me clarify... I'm waiting on YOU to provide ME with those scenarios. :D

This is similar to #424, and I'm facing issues today, after 13 years!! it is really hard to add simple

implements Serializable

When I removed those asserts just to test, the move failed like it should, but the battle never progressed past the "but it failed" dialogue

Period removal did not crash my dev environment so I think we’re good to merge

Oh okay I'll check back in January 2027

Maybe we should just .Lock() at the top and call it a day?

This can be resolved on April 1st