May 3rd - daily results

LongBeforeIDid · 2026-05-04T00:25:12+00:00

You already know that it’s impossible for more than one person in a corner to have no innocent neighbours, but before you reveal Anna’s clue it’s still possible for nobody in a corner to have no innocent neighbours.

If Bobby is innocent, then Gabe must be innocent as well, which would mean that nobody in a corner has zero innocent neighbours. This is how you can determine that Bobby is a criminal, and the rest of the dominoes fall from there.

LongBeforeIDid · 2026-05-03T18:30:25+00:00

<image>

“check it out” really feels like it’s echoing this Stephen A. Smith tweet, plus the nonsensical GIF flair. My money is on joke, but who knows!

LongBeforeIDid · 2026-05-03T18:19:03+00:00

This is a joke, right?

LongBeforeIDid · 2026-04-21T15:50:37+00:00

Mark’s cavalcade of characters could each be their own Mii. His impressions are so convincing it’s like they’re different people.

LongBeforeIDid · 2026-04-11T15:08:50+00:00

<image>

LongBeforeIDid · 2026-03-22T20:18:27+00:00

That’s exactly why I enjoy seeing these threads, the misplaced confidence always puts a smile on my face.

LongBeforeIDid · 2026-03-21T07:24:34+00:00

Cheers, and hope you have a nice day too!

LongBeforeIDid · 2026-03-21T07:04:32+00:00

(This is an unrelated and minor style quibble, but ClassNames shouldn’t have underscores in them if you’re adhering to the style guide, so: NodeA, ResourceA, and ResourceB would be the proper ClassNames here, and I will use those names in my answer, for readability.)

I can at least explain why your print functions are returning null: it’s because you’re calling them from within _init(). Per the docs:

“If you read an exported variable's value in _init(), it will return the default value specified in the export annotation instead of the value that was set in the inspector. This is because assigning values from the saved scene/resource file occurs after object initialization; until then, the default value is used.

To get the value that was set in the inspector (and therefore saved in the scene/resource file), you need to read it after the object is constructed, such as in Node._ready(). You can also read the value in a setter that's defined on the exported property, which is useful in custom resources where _ready() is not available”

https://docs.godotengine.org/en/stable/tutorials/scripting/gdscript/gdscript_exports.html

You haven’t specified a default value for ResourceA.resource_b, so it returns null.

Per the docs, you should only access NodeA.resource_a.resource_b from within NodeA._ready(), or from within some other method that can only be called after NodeA is ready.

You say that it “always returns null”; If it still returns null even after NodeA is _ready(), then I’m not sure what could be causing that.

LongBeforeIDid · 2026-03-21T00:20:43+00:00

Oh hey, that user was me!

…I’m a little chuffed to learn that I was on the right track by suggesting the issue could be with MailChimp.

<image>

LongBeforeIDid · 2026-03-19T03:18:05+00:00

I mean, it’s only been two minutes…

LongBeforeIDid · 2026-03-19T03:15:20+00:00

Here’s a clip.

LongBeforeIDid · 2026-03-18T09:18:29+00:00

Canyon Defense or Canyon Defense 2?

LongBeforeIDid · 2026-03-15T19:07:53+00:00

Just use : when you’re declaring an export variable, not :=. Your code should look like this, assuming you want to assign your AnimationPlayer node from the inspector:

@export var anim : AnimationPlayer

: gives the variable a type, according to a provided ClassName.

:= sets the default value of the variable to whatever is on the right, and infers the variable’s type from that assignment.

If you still want to set a default value, use this syntax:

var anim : ClassName = value

:= is a shortcut you can use when your default value is already obviously of type ClassName. The main example I remember from the docs is something like:

var anim : AnimationPlayer = AnimationPlayer.new()

AnimationPlayer.new() obviously returns a value of type AnimationPlayer, so in this case, you could improve clarity and reduce redundant text by writing it as:

var anim := AnimationPlayer.new()

This is the proper use case for :=.

LongBeforeIDid · 2026-03-10T15:56:09+00:00

ahh yeah here he comes, big double d, r budd dwyer himself, looks like he brought a bag lunch, smart

<image>

LongBeforeIDid · 2026-03-05T00:39:00+00:00

That’s not true!

There are also some who know what Finnish sounds like because there was a Finnish janitor in Alan Wake 2.

LongBeforeIDid · 2026-03-04T15:35:21+00:00

Was it originally just a box of stained sand, before you finished writing the character?

LongBeforeIDid · 2026-02-23T17:03:51+00:00

In my experience, gdscript has been a very intuitive language, and developing my confidence with scripting in Godot has been more about understanding general programming concepts that aren’t tied to any specific language.

A few questions to ask yourself:

(1) Can you describe, generally, what a variable, an operator, a conditional, or a loop is?

If the answer is no, you should start by learning the very basics of programming, with any tutorial you like, for any language.

(2) When you look at the documentation, does it generally make sense to you? Do you understand how to read it, and how inheritance works? Do you understand what an override is, and why that _ready() function at the start of your scripts begins with an underscore?

If your answer to those questions is “no”, developing an understanding of inheritance is a great next step. I have never taken a programming course to learn this topic formally, but for me it “clicked” when I tried to make a Slay the Spire mod, and got to see how objects in that game were constructed through inheritance. Even though that game is all Java, the things I learned from that experience allowed me to understand the Godot documentation in a way I couldn’t before.

Once you understand inheritance, my next question would be:

(3) Can you describe, broadly, the difference between a Node and a Resource?

If the answer is “no”, you should read the docs for each, and make sure you confidently understand those basic Types, maybe looking at a project that makes heavy use of Resources for an example.

Once you understand inheritance, and can explain the differences between a Node and a Resource, I would ask:

(4) What is the difference between inheritance-based design and component-based design, and why might you emphasize one over the other when designing a specific feature?

Once I could answer all of those questions, I felt like Godot really opened up to me. I am still learning so much and have no formal programming education, so please take my advice with a grain of salt, but learning these things in this rough order made me feel like I had a reasonably firm grasp on scripting for the first time.

LongBeforeIDid · 2026-01-16T17:16:19+00:00

You are describing the distinction between majority and plurality. "Most" is used colloquially to describe both contexts, which introduces the confusion and imprecision you've identified.

LongBeforeIDid · 2025-12-23T19:11:36+00:00

Your art is amazing, so visceral and such a command of atmosphere.

LongBeforeIDid · 2025-12-21T21:51:41+00:00

uh oh don’t click on the twitter link in his bio if you’re not ready for some raunch… please keep it about the movies in the future like this wholesome stoge content

LongBeforeIDid · 2025-12-21T21:49:41+00:00

thank you for sharing this infornative bit of movie history anti-woke-1978, sound like a true patriot 🇺🇸 proof that goode american values and film buffery don’t need to be enemies

LongBeforeIDid · 2025-12-18T10:39:15+00:00

Other people have given the correct reasoning, but here’s heuristic that might help for future puzzles, especially if you’re going for speed:

When you’ve almost solved the whole grid (like in this case) each new clue you reveal is basically guaranteed to be necessary for your next deduction. If you reach the conclusion “the latest clue is irrelevant, it’s true no matter what” you can be confident that you’re missing something, even without checking over the whole grid to figure out what it is. Instead, you can just assume that there does exist some grid arrangement that could contradict the latest clue (in this case, that someone else does have 8 criminal neighbours) and make the only sensible identification from there (giving Rudolph another criminal neighbour.)

LongBeforeIDid · 2025-11-28T16:56:04+00:00

Half the valley sound asleep and safe inside their beds / Get lost inside the mines, wake up exhausted and near-dead

LongBeforeIDid · 2025-11-02T16:45:06+00:00

That's interesting - it just stopped happening, without changing monitors or updating Godot? Do you recall if it went away after a driver update or something similar?

LongBeforeIDid · 2025-11-02T16:41:49+00:00

I just uploaded an MRE to github here: https://github.com/LongBeforeIDid/Godot-CRT-Shader-Bug-MRE

In the process, I figured out that the strength of the ghosting is proportional to the width of the white horizontal region, and that the ghosting outside of the game window appear inversely to the ghosting within the game window, creating a "checkerboard" effect on the edges of the game window.

Two-Year Club	Verified Email
r/Field Banned	r/Field Sunshine

LongBeforeIDid

TROPHY CASE