David
I have possibly some unpopular suggestions, and maybe it’s more of a ‘what should have happened’ as it’s a bit late to do this now:
1. Postpone races for the festive period (until January 1st).
Right now, the servers have been overloaded, bottlenecks, race-conditions ... whatever the cause may be ... and having a solid block of time to resolve the issues would really help.
2. Get help. And allow them to help. By this I mean, find someone willing to go through the code and maybe perform some of the quick fixes that you're not getting round to because you're focusing on W2W. Yes I'd love to do this and help out - it's just my experience is in Javascript only and I'm not sure you'd want someone inexperienced looking through things.
3. I kind of disagree with the focus in fact. The races, messed up as they are, still 'perform'. But people are losing real-world money, and years of time, because of faults in the frontend. These are criticial/urgent matters. Even simple things like salaries of young/trained drivers/staff going up to normal stats means that people have invested tokens into these supposedly cheaper options but are now losing out on them. League's messing up as they tick over to the new structure, races not starting.
I would seriously consider putting races on hold, fixing all of the frontend issues first, and then going to W2W.
Hi David, you've been really helpful throughout this week, I truly appreciate it.
These are simply not tasks I could drop someone else in to take over on short notice. My aim is to wrap up tonight with the service stable, if all goes to plan, then tomorrow address many of the other issues, IAPs etc. I do not plan to devote any more time to refining w2w right now. The physics update was enough to address 80% of the concerns, the remaining 20% can wait.
CEO & CTO
