This is a silly mistake I always make with #dotnet and static members. Static members are initialized in the order they are declared, which means, in this case, I’ll get two entries of nulls in my collection because they’re not initialized yet.

#JetBrainsRider warns me that I have an issue.

@khalidabuhakmeh holy crap. That's why I was having an issue with a static method a while back I bet... what an idiot. My solution was to just make the static method not static and force an object...

I'm notorious to some in my habit of declaring variables when I need one and moving them to the top later (if I remember which I'm notorious because I don't remember a lot)