According to an industry website on coding challenges, here are the top five hardest things known to man to code:
1. Aanderaa-Karp-Rosenberg evasiveness conjecture
2. Cryptocurrency algorithm replication
3. Space vehicle intercept trajectories
4. Integer factorization in polynomial time
5. Video game player grouping
So cut ZOS some slack, they've only been working on it for 5 and a half years!
Zos did nothing about the issue for a year and OP wants us to cut them some slack. For a year the forums were filled with threads informing Zos their fix 2 years ago did not resolve the issue then Zos follows up trying to tell us they thought that previous fix worked.
They either outright ignored our flood of feedback or chose to lie about the issue. I do not know which is worse.
Additionally, Rich stated they would not have another event that required the GF until they were 100% certain it was fixed. Considering they did not do due diligence and stress test the "fixed" GF on the servers before the event they could not be 100% certain. Again, their words fell short of what they actually did.
This is not about the GF not working properly. This is about management ignoring us. It is about poor management and possibly incompetence at that level. OP wants us to give Zos a break because they do not live up to their words.
VaranisArano wrote: »Zos did nothing about the issue for a year and OP wants us to cut them some slack. For a year the forums were filled with threads informing Zos their fix 2 years ago did not resolve the issue then Zos follows up trying to tell us they thought that previous fix worked.
They either outright ignored our flood of feedback or chose to lie about the issue. I do not know which is worse.
Additionally, Rich stated they would not have another event that required the GF until they were 100% certain it was fixed. Considering they did not do due diligence and stress test the "fixed" GF on the servers before the event they could not be 100% certain. Again, their words fell short of what they actually did.
This is not about the GF not working properly. This is about management ignoring us. It is about poor management and possibly incompetence at that level. OP wants us to give Zos a break because they do not live up to their words.
I find it sad and funny that the Groupfinder improvements actually appear to be the thing that was working correctly, only for other things to start breaking under heavy load.
It's also funny and sad that ZOS' workaround for "we won't run events that require Groupfinder" has just been to rewrite the dungeon events so they don't "require" Groupfinder. With the result that the only canceled event was Midyear Mayhem because of Battlegrounds.
What's just sad is that everything else seems to have broken for more or less the same cause as earlier this year - that PC/EU has a high number of concurrent players during events. Whatever improvements ZOS made to handle that earlier don't seem to have held up for very long.
Actually, on top of that list should be "Hello World" using the Brain[Snip] programming language.According to an industry website on coding challenges, here are the top five hardest things known to man to code:
1. Aanderaa-Karp-Rosenberg evasiveness conjecture
2. Cryptocurrency algorithm replication
3. Space vehicle intercept trajectories
4. Integer factorization in polynomial time
5. Video game player grouping
So cut ZOS some slack, they've only been working on it for 5 and a half years!
[Edit to remove profanity]
nafensoriel wrote: »Space vehicle intercept trajectories can easily surge to petabytes of data to be calculated if you include annoying things like accurate gravity models.
Group finders are just one of those absurd logic equations. To anyone who thinks group finders are easy to do.. write a flowchart for how they should work. When you get to your 40th page and still havent reached an optimal solution youll understand why it's hard. If you never reach the 40th step congradulations youve conclusively proven you cant code and shouldn't code.
nafensoriel wrote: »Space vehicle intercept trajectories can easily surge to petabytes of data to be calculated if you include annoying things like accurate gravity models.
Group finders are just one of those absurd logic equations. To anyone who thinks group finders are easy to do.. write a flowchart for how they should work. When you get to your 40th page and still havent reached an optimal solution youll understand why it's hard. If you never reach the 40th step congradulations youve conclusively proven you cant code and shouldn't code.
That is so last century ...
- Establish a decent amount of ground truth (Shouldn't be any problem for ZOS since they should have plenty of historical data)
- Train a neural network (AWS has cheap GPU instances just for this purpose, they even have them wrapped around a dedicated service now)
- Use the NN output model and implement it in your server app to make quick and accurate predictions about who should be grouped
This isn't rocket science, i've done just that and used NN models on anything from large high traffic client/server systems down to embedded ARM devices (Even some without floating point FPU)
nafensoriel wrote: »Space
Group finders are just one of those absurd logic equations.
Luckylancer wrote: »nafensoriel wrote: »Space
Group finders are just one of those absurd logic equations.
You select longest waiting 2 DDs, 1 healer and 1 tank. I cant imagine how hard it is!
If you dont want to put 810cp and 15 level guy, group people to "810-300 cp, 300-160cp, 160cp-10 level. If you have a lot of cp but sub-50, you are down by 1 group." parties can be formed from 2 adjent group types max, waiting 5 min means you can be in party with 2 upper or lower groups aswell.
This cant be rocket science.
nafensoriel wrote: »nafensoriel wrote: »Space vehicle intercept trajectories can easily surge to petabytes of data to be calculated if you include annoying things like accurate gravity models.
Group finders are just one of those absurd logic equations. To anyone who thinks group finders are easy to do.. write a flowchart for how they should work. When you get to your 40th page and still havent reached an optimal solution youll understand why it's hard. If you never reach the 40th step congradulations youve conclusively proven you cant code and shouldn't code.
That is so last century ...
- Establish a decent amount of ground truth (Shouldn't be any problem for ZOS since they should have plenty of historical data)
- Train a neural network (AWS has cheap GPU instances just for this purpose, they even have them wrapped around a dedicated service now)
- Use the NN output model and implement it in your server app to make quick and accurate predictions about who should be grouped
This isn't rocket science, i've done just that and used NN models on anything from large high traffic client/server systems down to embedded ARM devices (Even some without floating point FPU)
So your solution is just "make a neural network and bam it works" ?
Are you daft?
Sorry, that's baiting.
Yes, you can make machine learning do this. It most likely would also require considerably more work. If you find it easy.. go make a group finder with an NN. Youll be a millionaire overnight selling the code to EA, UBI, and EPIC.
I do love when new blood comes along and pretends they've found the holy grail to replace all the old farts.. and then in every single case fall on their face when they hit reality. NNs are great. They are awesome tools. They are not magic and they don't replace all the tedious BS. Some yes. Never all.
nafensoriel wrote: »nafensoriel wrote: »Space vehicle intercept trajectories can easily surge to petabytes of data to be calculated if you include annoying things like accurate gravity models.
Group finders are just one of those absurd logic equations. To anyone who thinks group finders are easy to do.. write a flowchart for how they should work. When you get to your 40th page and still havent reached an optimal solution youll understand why it's hard. If you never reach the 40th step congradulations youve conclusively proven you cant code and shouldn't code.
That is so last century ...
- Establish a decent amount of ground truth (Shouldn't be any problem for ZOS since they should have plenty of historical data)
- Train a neural network (AWS has cheap GPU instances just for this purpose, they even have them wrapped around a dedicated service now)
- Use the NN output model and implement it in your server app to make quick and accurate predictions about who should be grouped
This isn't rocket science, i've done just that and used NN models on anything from large high traffic client/server systems down to embedded ARM devices (Even some without floating point FPU)
So your solution is just "make a neural network and bam it works" ?
Are you daft?
Sorry, that's baiting.
Yes, you can make machine learning do this. It most likely would also require considerably more work. If you find it easy.. go make a group finder with an NN. Youll be a millionaire overnight selling the code to EA, UBI, and EPIC.
I do love when new blood comes along and pretends they've found the holy grail to replace all the old farts.. and then in every single case fall on their face when they hit reality. NNs are great. They are awesome tools. They are not magic and they don't replace all the tedious BS. Some yes. Never all.
Yes, i'm so daft that i do this kind of stuff on a daily basis for a living and have yet to fail to deliver on a project.
As for "new blood", i've been programming since 1978, with many years spent in the gaming industry.
Here's one thing i have learned in all those years, if you don't keep up with current technology, you will become obsolete very quickly.
PS: And yes, setting up a NN and training a model is not difficult at all anymore. With decent ground truth data, they will almost always outperform conventional algorithm based solutions, especially for complex problems like a smart group finder.
Actually, on top of that list should be "Hello World" using the Brain[Snip] programming language.According to an industry website on coding challenges, here are the top five hardest things known to man to code:
1. Aanderaa-Karp-Rosenberg evasiveness conjecture
2. Cryptocurrency algorithm replication
3. Space vehicle intercept trajectories
4. Integer factorization in polynomial time
5. Video game player grouping
So cut ZOS some slack, they've only been working on it for 5 and a half years!
[Edit to remove profanity]
Sigh, that is the name of an actual programming language ...
https://en.wikipedia.org/wiki/Brainfuck
nafensoriel wrote: »Group finders also have to be lean. NN doesn't define that.
According to an industry website on coding challenges, here are the top five hardest things known to man to code:
1. Aanderaa-Karp-Rosenberg evasiveness conjecture
2. Cryptocurrency algorithm replication
3. Space vehicle intercept trajectories
4. Integer factorization in polynomial time
5. Video game player grouping
So cut ZOS some slack, they've only been working on it for 5 and a half years!
I don’t know about this thread. It starts off as a joke. Then people reply seriously. Then someone adds to the joke. And now there’s a discussion of who can call themselves a real coder. Now people are offering solutions... listen: it’s fake.
I despair for gamer kind.