Teaching blizzard basic programming

Here’s a basic programming tip:
Stop trying to do the work of another programmer. They will let you.

1 Like

I’d suggest 30-60 seconds instead.
2 minutes is plenty of time to make a comeback with the right team.
Below a minute? Not usually, 'less you’re lucky.

That is why no one likes commenting code.

If you actually mean “if the game has lasted more than two minutes” then this seems odd that you wouldn’t want backfill, considering matches can easily last 10 minutes.

If you meant “if there is only 2 minutes remaining” then I urge you to consider what two minutes remaining means. Firstly, capturing an object can extend the timer, so that needs to be considered. But you’re likely also forgetting that the remaining time can still be considerably high when a victory occurs for the attacking team. Imagine you’ve pushed the payload 90% of the way with 5 minutes left and you get backfilled, and during the time it takes you to load in, they take the remaining 10%. You will be backfilling directly into defeat despite more than 2 minutes remaining (and in rare steamroll cases maybe it hasn’t even been 2 minutes yet :smiley:).

You also haven’t actually considered the actual experience impact of the players in the match and how they’d feel about fighting 5v6 for upwards of 2 more minutes.

BTW if you’re not a programmer I would refrain from using a thread title like that. It sounds like you’re trying to be a smart aleck like you’ve solved some super obvious problem despite having zero experience. I can assure you the issue is not as dead simple as you seem to think it is, or they would’ve just done that.

I dont think I’ve every seen anyone use “=>” for ‘greater than or equal to’ before. Is this how you actually think about it, or is this syntax from a real language that you write in?

It is a real syntax in my preferred language. I mostly use C++ and C#, but is it also how I think about it.

Truly you can make due without the “=>” and use just “>” instead. However I use it because I wanna check when it reaches the two minute mark as oppose to just check if it passes it.

Also if we set to 0 instead of two minutes then I feel this would be better. Since it will check when it reaches 0 instead of it checking past negative numbers.

1 Like

Interesting. I’ve never known anyone who thought about it that way (to me at least, that’s backwards :slight_smile: ).

I havent used C# in a while but I use C++ on a daily basis and ‘=>’ is not valid syntax, though. Is it valid in C# (and that’s your preferred language) or do you have yet another that is your preferred?

1 Like

i’m losing my mind @ this phrase

1 Like

The issue with that is the in game timer does not reflect how much time is left in the match with multiple checkpoints, overtime, etc.

Honestly, now that you get priority queue for backfilling I don’t think it’s really that frustrating anymore.

Yea in C++ I think it is >= actually.

Not really but I do know other languages such as Lua, Typescript, Javascript and shell scripting.

1 Like

But why would they do that is the question

You can win a game in 60 seconds, nevermind 2 minutes

Also, backfill is just extra XP.

Why spend an extra 60 seconds in queue when you can spend 60 seconds in a game & get rewarded for it? Doesn’t make sense

Because in many cases backfill leads to a loss, so people do not like having to load into a loss, followed by getting put back into the queue.

Like imagine you went to go play laser tag and you were waiting in line and then got told you could cut to the front for 30 seconds, lose the game, then get put in the back of the line.

Then why did you try to teach Blizzard programming…?

3 Likes

Because people who dont know how to do something generally have a very simplified model of how that something works. For example, Doomfist still has bugs because the devs are lazy, and certainly not because basic computing using variables and conditional statements to represent a real 3D world in a simulated physics system over a network is prone to corner cases. Oh and new code never has side effects or unintended consequences.

1 Like

Luckily for you, I am a professional programmer. And I’m happy to report that the people at Blizzard are better than me. They’ve programmed everything that is currently in the game as they have been instructed.

You are blaming the wrong people for this one, chief. Programmers have no say in what they code.

I mean we know Blizzard doesn’t always use variables because they hardcoded Sombra’s hack-time.

If
{
Match time < 120
}

Then
{
Pls no backfill

}

1 Like

99% of gamers couldn’t create a 2D Pong replica using Unity, let alone create a 3D first person shooter from the ground up using a custom engine.

Don’t insult them, you have no idea the amount of expertise and work that goes into making games.

3 Likes

Then people will just leave before two minutes… :man_shrugging:

i think its like if the match has lasted more than 2 min then backfill is disabled.