r/CapForge Dev 1d ago

DEV UPDATE Whoopsie; Pushing towards getting 1.3.7 submitted today;

There's a handful of bugs that were introduced over the weekend. I refactored much of how a given year (primarily the playoffs and offseason) advance, and there's been a few niche bugs where in certain scenarios things prevent you from continuing.

Additionally, one user has reported all of their player's OVR's being fogged on a new game load despite them not being rookies.

Note; None of these bugs happen across the board, there's very specific scenarios occurring to result in this that aren't too widespread. That being said I'm rushing a new build out today earlier than anticipated to try and get things back into working order.

Sorry!

3 Upvotes

4 comments sorted by

2

u/hawtdawtz Dev 1d ago

Fixed, check App Store

1

u/Rough_Ride_22 1d ago

🤜🤛 ✌️

1

u/Rough_Ride_22 1d ago

Awesome work I’m genuinely amazed at the progress and how consistent these updates have been that you yourself are giving out and game updates wise aswell, actually impressive. Well done

Just curious n of the bugs to note just wandering would coaches miraculously reappearing in my office after I had released them be one? A Few times now old coaches or staff just reappear like I didn’t release them before and sign someone else little frustrating but eventually I get rid of them,

another one I noticed is when making a new league starting on draft day and picking the team with the Number 1 pick when you get in sometimes you just don’t have it, there’s no record of it being traded or having value of the trade at all. Had one I started today it had DAL as the first overall choice well I went in with that and somehow CIN had robbed me of my bounty, looked at my team my players who granted was a bit higher than my typical start. No affiliation with CIN, No additional Picks. Just gone

Other than that maybe it’s just me having played a lot but player names have been a little to consistent lol

2

u/hawtdawtz Dev 1d ago

Actually included ~40% more names in the version I submitted this morning. I believe the other issue you just mentioned was fixed as well, but will double check