Richard Meredith

A fluffy white Angora cat lies curled up, nearly asleep. A six month old tabby kitten is snuggle up to her

Rare scenes of my girls tolerating each other this #caturday

A fluffy white Angora cat lies curled up, nearly asleep. A six month old tabby kitten is snuggle up to her

Rare scenes of my girls tolerating each other this #caturday

When Unity started collapsing I made a quick "how do I get going in Unreal" website many folks found helpful. that website has now MOVED and is a DIFFERENT COLOUR. If you want Unreal demystification, tips and scoops, this is a place

www.ughiguessiwanttomovefromunitytounreal.com

Update to the update: we got up this morning I got everyone fed and then Beez found the dress, sat on it and stared at me until I put it back on her

I have never seen a cat act like this

She's very happy now

I'm reacting to a statement in the form "X is disproved by Y", by saying
1. You misunderstand X
2. Y is irrelevant to X

I'm rejecting the premises, so there's no rearrangement of those premises that is salient here

Also nothing in the blog post moves the needle on either point

Asking for access to a complete, known product, is utterly different to asking for modifications to a existing product

Yeah, as I suspected, you're completely misconstruing the meaning behind that phrase

And even if you weren't, the WOW Classic example is so completely different to typical user/player feedback as to be irrelevant

We're in agreement here in a practical sense, I just think you've misunderstood the intent behind a particular phrasing?

But that's what "players/users don't know what they want" or "users think they know what they want, but they don't" means:

Users are right in their feelings but come with solutions/suggestions/demands (what they say they "want") and generally you've gotta look past what they say they want

Yes, there's a need to reinterpret player's feedback, to "find the need and address it properly" as you say downthread, which means that "players don't know what they want" hasn't been disproven at all! Quite the opposite is true, in fact

Then maybe vibe coders could hold off on the grandiose claims until *after* they can show results? The point is not to declare anything with certainty, it's to point out the gap between what the techbros are saying and what they're shipping.

a collage of these three tweets https://bsky.app/profile/why.bsky.team/post/3lzrkcsk3xc24 https://bsky.app/profile/why.bsky.team/post/3lzsgnvof4c2n https://bsky.app/profile/why.bsky.team/post/3lzubxv6q722o

i for one am shocked that the "i go in the pool to cool down, why can't my phone?" guy is bad at programming and offloading his job to the anthropic api

"I want to play this thing I have nostalgia for that it's literally impossible to play now"

Is very different to

"I want this existing game that I am playing to be changed in these specific ways because I think that will improve the overall experience and not cause side effects I don't like"

Oh this gap, during the Years of the Omnicrisis? Yeeeeaah...

*eyes glaze over*

You probably don't need corporate saboteurs when you're at "I don't know or care how to remove the red squigglies from under my game name on my official communications" levels of slack-jawwed incompetancy

Like, I know it's not the most egregious thing about this at all, but Jesus fucking Christ

An unreal blueprint function, something like ReturnEvenOnly(value): if(value % 2) return value else (unhandled)

Event graph using that function Event BeginPlay: for(int i=0; i<=10; i++) Print(ReturnEvenOnly(i)

The output from the code, showing that for unhandled odd numbers, the function outputs the previous output (as opposed to a default value of 0) 0, 0, 2, 2, 4, 4, 6, 6, 8, 8, 10

Just got reminded of an absolutely cursed piece of unreal blueprint lore

If you don't add a return node on some paths in a function, and call it from the event graph, the callsite will just return whatever the previously returned value was, instead of say, a default value like zero

If you’re part of any creative groups, unions or other organisations in the uk you should be passing news like this along and spreading the world. News like this gets has the chance to be overlooked but if enough organisations kick up a fuss things can change.

You've got macros and K2 Nodes that can expand into their own nested node graphs inside the node, so you'd need to reason about those as well

No, but I do know *why* it happens:
bsky.app/profile/rtm2...

You can write blueprint linters, and I've considered writing one for this case, but determining all flow paths is a pretty gnarly problem space

I hit this a few years ago and thought I was losing my mind - sent me spiralling for hours

Just saw someone on a discord say that the behaviour was to "return default value" and it brought up flashbacks so I had to check :D

Impure nodes retain their outputs as anonymous class variables (in event graph), or anonymous locals (in functions). By not returning a value you are not updating that value.

It really should either be implicitly reset on call or just fail to compile

An unreal blueprint function, something like ReturnEvenOnly(value): if(value % 2) return value else (unhandled)

Event graph using that function Event BeginPlay: for(int i=0; i<=10; i++) Print(ReturnEvenOnly(i)

The output from the code, showing that for unhandled odd numbers, the function outputs the previous output (as opposed to a default value of 0) 0, 0, 2, 2, 4, 4, 6, 6, 8, 8, 10

Just got reminded of an absolutely cursed piece of unreal blueprint lore

If you don't add a return node on some paths in a function, and call it from the event graph, the callsite will just return whatever the previously returned value was, instead of say, a default value like zero

My games urbanism course is starting tomorrow. You can still enroll.

FYI for fellow narrative designers/game writers: the studio in question is Sentona Games and it’s my understanding they are currently interviewing to replace me. Be very careful with them. They were very nice to me and easy to work with right up until I needed the money I was promised.

If they come in early (as they should), when you don't have traction and still have a lot of development costs to cover, etc. that 30% - 50% can be much more justified

I crunched some numbers a while back and came to the conclusion that a publisher coming in late would need to boost expected sales by 2.5x to justify a 30% cut with no recoup.

If you have enough traction for a publisher to come in late, it's vanishingly rare that they're worth it

The publisher being involved *shouldn't* matter as
- They should be paying for the bulk of costs
- They should be adding more revenues than they take in recoup / cuts

A lot of shoulds there as publishers are coming in much later than they should be now, so paying for less dev and adding less revs

He blocked me.

The guy doing "debate me" shit blocked me. That's gotta be an achievement, right?

Yuuuuup!

Just saw him responding to someone else complaining about "vitriol towards white men" so you know this guy is a fucking loser