You can't what if everything. In the bad old days games just used to stay knackered, release and hotfix is huge improvement.
Well I would think the central payment system is a core issue, one of the things where you must "what if" everything.
You can't what if everything. In the bad old days games just used to stay knackered, release and hotfix is huge improvement.
We have a similar situation at the place I work where a particular "internal currency" can either be bought or free (though think stuff like "canteen vouchers" rather than anything exciting). Our policy is that the ones someone bought are spent last - which matters for us because the bought ones can be returned for a full refund, but you can't cash in the free ones - and I think the same should probably apply in any ARX-related situation where it mattered.If someone buys say 5000 ARX with cash but also earns 5000 ARX ingame, then purchases a paintjob for 5000 ARX.....which part of their 10000 ARX total is used to buy the paintjob first, the paid for ARX or the earned ARX.
Doesn't matter. As long as the free arx get removed things would still be hunky dory. If it is only the free arx that are remove that is. Op also refers to purchased once:There's another problem with this losing ARX's on a reset issue.
If someone buys say 5000 ARX with cash but also earns 5000 ARX ingame, then purchases a paintjob for 5000 ARX.....which part of their 10000 ARX total is used to buy the paintjob first, the paid for ARX or the earned ARX.
Probably best for Frontier to not delete any ARX upon reset, but they do what they want.
Even if you never spent any of it, but only just purchased it.
I would find it incredible if this didn't cross someone's mind while this was being made. it's not exactly some obscure, hard to define edge issue. But then again, I've seen some doozies from FD recently.You can't what if everything. In the bad old days games just used to stay knackered, release and hotfix is huge improvement.
Well I would think the central payment system is a core issue, one of the things where you must "what if" everything.
I would find it incredible if this didn't cross someone's mind while this was being made. it's not exactly some obscure, hard to define edge issue. But then again, I've seen some doozies from FD recently.
Lmao, thats like blaming the hammer for missing the nailWelcome to agile programming: making things up as you go! Analysis is a waste of time!
Granted it's been a while since I got my qualifications but I can't believe not avoiding obvious problems is now standard programming practice.That's not how release and hotfix works.
Granted it's been a while since I got my qualifications but I can't believe not avoiding obvious problems is now standard programming practice.
It's true knackered games stayed that way in ye olde days, but the press would've covered them accordingly and put a big 'avoid' on their reviews and only mugs who judged games by their packaging cover would get stung with a dud.You can't what if everything. In the bad old days games just used to stay knackered, release and hotfix is huge improvement.
It's true knackered games stayed that way in ye olde days, but the press would've covered them accordingly and put a big 'avoid' on their reviews and only mugs who judged games by their packaging cover would get stung with a dud.
I still go back to early 90s games from the 16bit era and the level of polish on display there (of the good games obviously) is something I sorely miss with many current titles - which admittedly are more complex in nature, but how some really glaring issues continue to make it to the live version is hard to grasp. Would love to be a fly on the wall at FDev to understand better how this keeps happening.
Maybe computer games (and there's plenty that are not broken) - consoles though were a noticeable step up in terms of playability and overall quality; as someone who switched from C64 to Mega Drive it was a real eye opener.All games were knackered back then even the ones considered classics, then you had to hope for a patch disk with the right stuff on it with a magazine, now stuff just gets fixed via the internet.
I've got a massive 30+year game collection and the old disks are better left on the shelf. If you want a stable working version of for example X-com enemy unknown steam has a working patched version compatible with modern systems and the alien base bug has been fixed. Back in the day you just lived with it being broken even though its one of the best games ever in any countdown.
Release and hotfix is much better.
Considering they were already doing it right for Frontier Points, they didn't even need anyone to think about or analyse it. They just needed someone to go over the old code with their brain functioning, so yeah, I qualify that as obvious."Obvious" is entirely subjective.
Right after getting a load of free ARX is probably one of the least obvious times for a save-game reset and most players never reset at all based on what people say here.
So I'd say this is definitely an edge case or the forum would be flooded with identical threads and threads about those threads.
No drama=not widespread.
Maybe computer games (and there's plenty that are not broken) - consoles though were a noticeable step up in terms of playability and overall quality; as someone who switched from C64 to Mega Drive it was a real eye opener.
Considering they were already doing it right for Frontier Points, they didn't even need anyone to think about or analyse it. They just needed someone to go over the old code with their brain functioning, so yeah, I qualify that as obvious.
You can imagine a scenario where the in game hooks are only aware of the CMDR and attach there, and so Arx had to be built as a combination of CMDR + account owned Arx.I am likely grossly simplifying things but it wouldn't surprise me if Xmas Arx were tracked separately in the code and FDev just forgot to ensure the relevant variables carry over in the event of a CMDR reset.
I think "obvious" is a bit of a stretch, it's been months and there's been countless ARX threads where people have worked their very hardest to find ways to complain about ARX and this hasn't come up before.Granted it's been a while since I got my qualifications but I can't believe not avoiding obvious problems is now standard programming practice.
I think "obvious" is a bit of a stretch, it's been months and there's been countless ARX threads where people have worked their very hardest to find ways to complain about ARX and this hasn't come up before.
I find this very iffy, as there should have been at least some instance of this happening before now if this was the result when the system worked as it should.
Nothing's really confirmed yet, though people certainly have already gotten a head start on making a big deal about it.Not sure anyone has confirmed anything yet.