a few people have mentioned the glitch about not being able to access the different trainings but it's one thing that I am unable to replicate and I'm not sure if it's a settings thing or specific chain of events.
To be honest I'm confused how the browser version doesn't have the issue but the download version does. My best guess is maybe the save mechanic is screwing up the training but that is the only difference between the two versions that would explain it????
=3=
I'm also kind of wondering if I should have hard coded the different track types, since the methods I try to implement to prevent an impossible track seems to fail when compiled =3=
If I went back to the idea I would probably rework the training and race physics completely so that way it is at least more consistent.
The biggest issue with how I coded it is the training mechanics function differently than the race mechanics from a physics standpoint, and for how the tracks generate. The main thought for the race was excluding jumping in theory any gobo can finish any race, however this ends up failing with strength challenges where they're unable to get up the first slope at times.
In the case of training, the physics mechanics are different and admittedly that's because I coded it poorly. I should have planned ahead because currently it's two separate instances doing a similar thing rather than using the same line of code to keep consistency.
Overall as it stands I feel like the script is kind of too messy to try to fix, I'd be better off starting new using what I learned as a whole to rework it all.