Hi, i'm editing my own db with the advanced editor, and for some of the changes to work I think I need to edit the local.cdb as well. There's a ticker in the editor called 'local.cdb patch' and I was wondering if this could be used in this situation, or if I need to open the local.cdb and edit the tables one by one to reflect the changes I made in my db?
Many changes require that you also change the Local.cdb. For most of them, you can simply copy over the data from your main DB (e.g. STA_race and STA_stage - copy the .xml's from main DB to Local.cdb).
So yes, tick the Local.cdb patch button, import it, make your changes and export it again.
Edited by CrueTrue on 10-04-2009 11:38
But here's the problem: I altered the chances of the different potentials occuring in the STA_newrider_area in my own db. Problem is, when i'm playing a career the scouts find no new riders. I see that the STA_newrider_area isn't part of the local.cdb, so i'm not sure how to tackle this problem.
Try having a look at gene_i_min_new_riders and gene_i_max_new_riders (in STA_new_rider_area) - try setting them extremely high.
Edited by CrueTrue on 10-04-2009 11:53
I think I know what's causing the problem now, and I'm writing this post as a 'heads up' to the guys with the PCMDaily09 db.
I've found that riders do appear when scouting, but only after a couple of years, and they all seem a little older than usual.
Therefore I believe that editing the STA_potential only defines when young riders become "scoutable" and not their level.
When I increased values in the STA_potential, I postponed the moment at which I could see the young riders. They appeared a couple of years later, having grown into better riders, albeit older riders.
So if the PCMDaily09 guys are altering the STA_potential table, they might want to look into this.
