Can you code better than the greatest developer alive Zig Forums?

What you should do here is make some kind of list instead right?

There's more to it than that.
>completely meaningless class/method names
>ifelsescript class (what's that even supposed to mean) has method ifelse (dafug) that assigns a string day name based on an int????????
>public class properties break encapsulation
>methods don't take parameters and don't return a value
>instead they set properties for no reason
>modifying state this way is immediate death for multithreading

No

Still too complicated

well for the day example, you could simply store an array of strings since you seem like you're going to be using them a lot, which desires persistent data storage, so in something like c, you could be like const char* const days[] = {"sunday, "monday", ...}; (or something like that)
and you can simply use days[index number] to refer to the string you need and that bypasses the need to run through control flow
a lot more needs to be done in the second post

I'm don't code either, but I think you could make an array for that.

You would make an array/list with all the days and then assign the "Day" to whatever the ID is in the array. Something like
Day = dayArray[ ID ]
But I'm a retarded fag so bleh

...

So basically he doesn't know what arrays are? Isn't that like chapter 3 of whatever language you're learning?

huh?

Or just use a fucking dictionary.

huh?

Pointless in this case

p much
for some reason that seems like a big problem with java and c# beginners who are so used to things that are the equivalent of the template libraries
do you like to use a sledgehammer to pound a 2 inch nail into a 2x4

In something as simple as days of the week? The index numbers are your keys

I can't tell how any of the uniforms would be different

How hard is it to get into Unity if I have backend web experience in C#?

By starting small, and not committing. When an inexperienced programmer designs a big piece of software, they inevitably create a mess that becomes unmaintainable. When this happens, start over. Each time you'll do it better and better. Software design is a skill that needs to be honed. You can't skip it.
The problem with Yanderedev is that he bit off more than he could chew, and his success forced him to keep moving forward past the point where his codebase is impossible to work with. The larger the scope and scale of the project, the more important it is that responsibilities be separated.
The more separated responsibilities are, the more you can allow yourself to forget how parts of your design actually work. Without this, you end up in a situation like yanderedev where to add a new type of witness behaviour to an NPC you need to remember how your hair color generation works so they don't end up breaking each other. This could be fixed with refactoring, but refactoring is admitting that you aren't perfect, and I'm not sure yanderdev's ego would allow him to do that.

When you're right, you're right. I just assumed he must know what arrays are and avoided them for whatever reason.

the only difference I can tell is that he's assigning those textures in different orders to each of the 4 materials

CultureInfo.CurrentCulture.DateTimeFormat.DayNames[dayNum];

Wait a fucking second. Did he make If Else a fucking function?

I dunno. What's her name?

looking at it in the context of two functions that seem to do the exact same thing, named ifelse and switch, it looked like this was originally something that was used to profile if switch statements were faster than if statements, and he just didn’t delete the ifelse one.