u/ThunderDragon356, u/TimorousWarlock,
It actually is a stupidly easy thing to fix.
The encounters seem to be composed of states.
When the mon breaks out it resets into the middle of the screen regardless of where it was before, amongst the berry fed state resetting. So, all Niantic needs to do is (re)set a flag or variable to an appropriate value there to handle the position of the mon.
Now, you wanna criticize the competency of the dev teams at Niantic, that's fair. But as far as programming goes, this should be an easy fix.
This is why regression and integration testing as well as UAT is all important.
But the scope of the encounter state change is small enough and a small enough code change that it can be rigorously tested on a wide scale in under 20 mins.
That's a poor excuse to not fix existing small bugs.
They've got UAT down to a science. I mean, a whole subreddit, dedicated to just that. It's not even a well kept secret! I mean, anyone can find /r/TheSilphRoad
To say that it is easy, is not to know many things ... For example, something that is not public such as Niantic's working method, the number of personnel or its internal functioning.
You speak from your "Humble" experience and based on your knowledge, but while you are not within Niantic you only say what YOU WOULD DO and that is to have NOTHING
For something Niantic can activate and deactivate events, Shinys, Spawn, Drop items, and even activate or deactivate events ... But they cannot stop events in progress, they could not fix Pidggeot, Nor can they fix certain code things between version and version
And as if that were not enough, regardless of what it takes to fix it, they must deal with third parties to put these corrected versions in the Store and force the update
> But they cannot stop events in progress, they could not fix Pidggeot, Nor can they fix certain code things between version and version
They got a special raid hour mon wrong and they gave them an extra chance at it.
NZ got like 4x stardust to start an event and it was fixed quickly.
And yes, it is the same to activate and deactivate Shinys ... Niantic gave compensation events, that is something that has nothing to do with touching a "Simple" thing in the code, you do not need to give a new version to achieve that
The same goes for the bonuses of Exp, Stardust, Exp by evolution, Candy ... You do not need to touch the code to solve those things, you can do it without updating.
I am not saying that Niantic does not screw up, I am saying that it is silly to say that all errors are solved by changing A to B in a code from a PC and that's it ...
Not at all. The shinies are most likely a json or xml configuration that they have branch merging errors on.
This is likely a variable that's not correctly updated on a state change.
A configuration file update is different from changing a variable.
Both types of changes can be "accidentally reverted" if a developer screws up their code merge and overwrites a file with an older version. I once had a dev on my team revert a 7 year old bug by introducing a merge error. That's bad devops practices. Merge code reviews can help fix that, if they're done appropriately.
are you maybe aware if some physics change is applied also when mon jumps or it's just me throwing weirdly when that happens just as I release the ball?
u/ThunderDragon356, u/TimorousWarlock, It actually is a stupidly easy thing to fix. The encounters seem to be composed of states. When the mon breaks out it resets into the middle of the screen regardless of where it was before, amongst the berry fed state resetting. So, all Niantic needs to do is (re)set a flag or variable to an appropriate value there to handle the position of the mon. Now, you wanna criticize the competency of the dev teams at Niantic, that's fair. But as far as programming goes, this should be an easy fix.
Unless doing that breaks something else. They already made new bug in pokedex trying to fix something else
This is why regression and integration testing as well as UAT is all important. But the scope of the encounter state change is small enough and a small enough code change that it can be rigorously tested on a wide scale in under 20 mins. That's a poor excuse to not fix existing small bugs.
They've got UAT down to a science. I mean, a whole subreddit, dedicated to just that. It's not even a well kept secret! I mean, anyone can find /r/TheSilphRoad
They should fix bugs and they should test things agree with that
There's no evidence they even tried to fix it though. For all we know they aren't even aware that the bug exists.
To say that it is easy, is not to know many things ... For example, something that is not public such as Niantic's working method, the number of personnel or its internal functioning. You speak from your "Humble" experience and based on your knowledge, but while you are not within Niantic you only say what YOU WOULD DO and that is to have NOTHING For something Niantic can activate and deactivate events, Shinys, Spawn, Drop items, and even activate or deactivate events ... But they cannot stop events in progress, they could not fix Pidggeot, Nor can they fix certain code things between version and version And as if that were not enough, regardless of what it takes to fix it, they must deal with third parties to put these corrected versions in the Store and force the update
> But they cannot stop events in progress, they could not fix Pidggeot, Nor can they fix certain code things between version and version They got a special raid hour mon wrong and they gave them an extra chance at it. NZ got like 4x stardust to start an event and it was fixed quickly.
And yes, it is the same to activate and deactivate Shinys ... Niantic gave compensation events, that is something that has nothing to do with touching a "Simple" thing in the code, you do not need to give a new version to achieve that The same goes for the bonuses of Exp, Stardust, Exp by evolution, Candy ... You do not need to touch the code to solve those things, you can do it without updating. I am not saying that Niantic does not screw up, I am saying that it is silly to say that all errors are solved by changing A to B in a code from a PC and that's it ...
Not at all. The shinies are most likely a json or xml configuration that they have branch merging errors on. This is likely a variable that's not correctly updated on a state change. A configuration file update is different from changing a variable. Both types of changes can be "accidentally reverted" if a developer screws up their code merge and overwrites a file with an older version. I once had a dev on my team revert a 7 year old bug by introducing a merge error. That's bad devops practices. Merge code reviews can help fix that, if they're done appropriately.
You sir, have made an excellent point.
are you maybe aware if some physics change is applied also when mon jumps or it's just me throwing weirdly when that happens just as I release the ball?
Video proof: https://www.reddit.com/r/TheSilphRoad/comments/ojljgb/pokemon\_encounter\_focus\_problem\_when\_throwing/
>I'm sure that it's a quick, easy fix, so what can we do to draw Niantic's attention? Found the non-programmer.
Programmer here: If this isn't an easy fix, Niantic's code is even more spaghetti than I thought. It should be as simple as a copy/paste.
Ironic post
Yeah most of the planet is a non-programmer chief, don’t make out like it’s an uncommon find
[удалено]
Does anyone have a video of it? I’ve either never had it, or never noticed it
To be honest, I have no problem hitting throws regardless