Smite Dev Tracker

This sh*t makes me so furious it's insane.

Imagine being such a talented, dedicated, and positive employee and getting laid off with no warning or heads up like you're nothing to the company.

And not just Lermy, everyone else affected by the second round too, kinda like everyone on the first round of layoffs as well.

Utterly disgusting to the max level. Stew and every single higherup in HiRez deserve to be completely financially ruined for how many people they have affected with their sh*tty ass decisions.

Awful awful awful

This was actually added a few updates ago! In settings under Usability you can find a Photosensitivity option that you can toggle.

Under Video settings we also have opacity sliders for self, ally, and enemy VFX that you can use to tone down effects.

Hope this helps!

Literally didn't read my post, I didn't suggest a single "solution"

Just wanted to start a discussion about Hecate 3 as it's been irking me for a while now.

The idea that it only shields magical damage is cool on paper, and was cool on her release, but in practicality, especially with gods being entirely magical or physical, it's extremely unreliable as a shielding effect.

The fact that an ability does next to nothing depending on the composition of the enemy team is a really messy mechanic. Applying the shield only to see that the ally is chased by two physical gods feels very bad as someone who plays Hecate a lot, as it's not a matter of skill, but rather just pure luck of who's engaging in the chase.

Additionally, the shield itself is very confusing to apply and receive. The health bar shield is slightly more purple than the regular shield variety. In a massive team fight I don't really have time to colour pick the shield colour in paint to determine whether or not I'll live and whether or not I need to use an active item...

Why wouldn't they get any good data? That's just silly - they have shown that they can track god's based on the build they do, something like an aspect is not a problem for them lol.

If anything, it gives them direct info on how to buff/NERF a god or their aspect immediately next patch

The crew is investigating this now! Appreciate the report.

Did find the issue that was causing this this morning and submitted a fix. May take a bit for a hotfix to pop up that can take this fix but should be fixed in live soon.

That's also another awful idea in a MOBA - again, that works for other games but there's a reason why you don't see it here, in LoL, or other examples.

By doing that they would:

a) mitigate the consequences of allies leaving therefore implying that leaving is not as bad

b) Increase player frustration of joining a match in progress on a losing side, or on a winning side where the game is like 1 minute from being over

c) Decrease team synergy if people picking end up picking bad or trolling themselves.

All of this to avoid a simple solution - if you aren't gonna be there to pick a god, you shouldn't be in the queue.

Random choice if the player is not there is a terrible idea in a moba - it's not a FPS like Paladins where it doesn't matter as much.

You're rewarding players for not being there on time. What if you had to leave for a longer time and the match loaded you in, and now your team has to play as 4 instead of 5 players. Would you want to be in a team like that, or a game that encourages such behavior?

No offense but that is partially a problem - you weren't ready to play the game therefore you shouldn't have been in the queue.

You can always leave and rejoin, no?

Patch Notes

Because MOBAs depends on each member of the team being there, anything less is wasting other people's time in matches that can go up to 40 minutes long.

Queueing is the same, wasting 5 minutes of people's time.

Even the dedicated Assault map isn't confirmed - as they've said they feel fine with the current one.

Edit: I stand corrected lmao - I remember a comment going into detail how it's very resource intensive to create a new map for little to no benefit and how the conquest map serves its purpose for assault too, but I wasn't aware of newer plans to change the map.

Everyone's focusing on how you shouldn't reward allies for dying but I think the bigger problem is that you should never be punished for playing well and getting a kill. It's the same problem devs had with Perse upon her release - why should the enemy team be punished for successfully outplaying her by risking dying to a ghost of her?

we released a hotfix this morning that fixed an issue with Vulcan's Turret/Thumper not working with various Items!

Patch Notes here

You say you expected more "resistance" as if something bad has happened, when in reality most players saw the S2 announcement and went "oh neat i get to play smite but better"

Several things here that are obvious even without access to smite code:

• Rebuilt from the ground up does not mean every line of code is written from point 0. Old code often times is used at least as a reference point. Some things are different, as S2 most likely uses GAS, which would require most of the gameplay logic to be done in a completely different way, but the general point still stands - references are important unless you wanna spend a week trying to think of a way to do something that has already been done.

• The Susano issue sounds more like it relates to the logic of the networking code itself, rather than it being connected to Susano. Networking is DIFFICULT, and rubberbanding like that is extremely common of an issue, especially in an early phase of the game.

• Also, keep in mind, just because a bug looks the same and has the same repro, doesn't mean the root cause of it remains the same.

Tldr game dev is ...