That’s right kids, if you take a photo in step 4 of the weekly forzathon BEFORE completing steps 2 & 3 it will now show as completed.
However, you can now not complete steps 2 or 3 or have the 5 point \ 160 f’ap attributed to your score.
Let me preface this by saying I’m a developer and have been for a number of years (decades).
This reeks of poor architecture within the FH codebase. It shows there is a distinct lack of isolation within the codebase. We’re talking basic of basic checks here. Have the 4 tasks within a specified group been completed as opposed to hey looky, last task done, previous must have been so let’s mark as complete. But the mark complete must look at the overall task state and says no.
I’ve ripped \ refactored through way too many codebases with crappola like this and it is either lazy coding, poor architecture or pressure from mngt to just… ship.
My view is this a poorly constructed software architecture that allows this sort of error to propagate.
Either way, I’d be embarrassed to have my name associated with this (think LinkedIn).
edit: sanitised expletives to make me sound like a character from Happy Days.
That explains why both this and the treasure are messed up for me after using said battle for a race not only have I no treasure appearing but this whole chapter is not advancing.
It’s enough with all the other problems to make stop playing till the next dlc comes out.
I get the feeling they actually code for each forzathon weekly completion as opposed to an event driven framework which allows you to drop in any number of tasks and have them pop on completion and check the overall result.
We’re talking minimal lines of code here if correctly architected.
Yeah hopeless. Having been caught out in the past with stuff like this I make sure when I do the weekly Forzathon tasks I do them in order and don’t do anything else until all are completed.
I do wonder at times whether any of the developers play their own game or how much testing is done? There’s no way the missing car thumbnails of the new cars in the latest month should have got through testing.
There was a… some kind of reveal media event escapes me atm… and iirc a dev fired up the game, on an obviously tricked out dev rig, and still managed to look bad.
IF they play, it’s on said tricked out isolated dev rigs, not the usual bog standard machines and connections/servers so they have no real idea what the real game play is.
IF they test, it’s also on said tricked out isolated dev rigs and they simply don’t get the same game play experience we do.
All imo of course. I tend to think it much more likely they simply don’t play and don’t test, even on said tricked out dev rigs.
Sometimes I feel like the folks working on the game now are little more than glorified modders, trying to drop in new content here and there without actually having fundamental understanding of the majority of the coding for the full game. They just know enough to be able to add in and tweak things, but lack overall fundamental understanding of how everything works and interacts.
But somebody (finally) fixed the nonsense of the car sort order to (radical concept…) alphabetical (in English anyway… see below). So, somebody knows some fundamentals at least. I think.
…hmm, now I’m wondering, how that came out for all the other language editions ? Anybody ?
Let me answer as a player playing in Japanese. As in other languages, the listings are sorted alphabetically.
However, at least in Japanese, it is not confusing and easier to read than before.
This is because in Japanese, the words used for categorization are basically the same as in English, only the English words are replaced by katakana.
Therefore, the convenience is the same as for players playing in English.
I’m unsure if it’s a coding issue, or just a if/then mentality run amok. If socks then shoes. Pants independent.
The treasure hunt completes (for some) doing other events, as do accolades. So Forzathon only instance?
Yep, not a coder but honestly with the quality control this game has been lacking recently I knew there was some basic stuff they just weren’t going to bother doing properly.
Like it’s been YEARS and the game’s FPS still nosedives when you scroll through the rims options rapidly. Why not just load the LOD model for each rim at first? NFS has been doing that forever, I’m not even a gamedev and that’s just such an easy fix
