Page 1 of 1
3 questions for those who have played 10-20 seasons or more
Posted: Fri Feb 04, 2011 5:29 pm
by s3nn3n
I wanted to start a game to play for 20+ seasons, but wanted some help deciding on a db and some settings
1. How big do the save files get after 10-20+ seasons? (ex. if you use nhl and ahl on enhanced with prefs database normal, games stored 2500)
2. Are there any issues with salary cap after this many seasons? I though I read somewhere that you might need to edit the save game to increase cap after many seasons due to higher creeping salaries. Is this true? I also read somewhere that editing the same games could cause some corrupt issues.
3. The original db is a little thin on personnel. Lidas, for example, has added a lot and also changed some things like reducing the number of players with highly randomized potential. BUT it seems to me there are too many superstars, too much talent in some of these newer dbs. So, what db would you recommend?
thnks
Posted: Fri Feb 04, 2011 5:43 pm
by helmespc
1: I've seen them get to like 300 megs compressed if I recall correctly.... much bigger uncompressed...
2: There are issues with the salary cap eventually.... you'll find that some superstars will not be signed by teams because nobody has cap room. Not a big deal, just increase your cap at some point before this starts happening... I usually keep mine at about 62 mil.
3: I've had fun w/ both the original and the current Lidas dbs..... I also have enjoyed the 79-80 db.... it all depends on what you're going for.
Make sure you don't have anything stupid like bad color schemes for teams or certain leagues not enabled before you start... sucks to get into a game and realize there's something stupid you can't change... it can potentially drain your interest in playing.
Posted: Fri Feb 04, 2011 6:53 pm
by shooter_80
We are using EHM 2005 in the DMHNL with everything enhanced. We are in the year 2029 and the saves range from 500Mb to 600Mb. Havent been any issues with salary cap.
Posted: Fri Feb 04, 2011 8:38 pm
by philou21
shooter_80 wrote:Havent been any issues with salary cap.
Probably because you don't have some AI to destroy it.

It helps alot. The farthest season I got was 2018 and I think there was some cap issues starting to appear because alot of good players were on the trade block 1 week after 1st July.
Posted: Fri Feb 04, 2011 8:44 pm
by Tasku
My game's in 2018 and no cap issues. No stars on the trading block or without contract either.
Posted: Fri Feb 04, 2011 10:12 pm
by CeeBee
I'm in 2025 with a Lidas 2 DB and I don't see cap issues yet. The AI signs the occasional player to a 10m/pa contract but thats about the only glitch and thats a normal glitch in the game with any db.
Posted: Fri Feb 04, 2011 11:34 pm
by s3nn3n
ok. i'm gonna use lidas 3. tnks for the info.
Posted: Sat Feb 05, 2011 3:12 am
by Richie Daggers Crime
I'm in 2049 starting from the standard database with the $44 mil cap. There's been no cap issues in my game. My save file is 480 megs compressed.
Re: 3 questions for those who have played 10-20 seasons or m
Posted: Mon Aug 15, 2011 9:35 pm
by tmratlif
My Boston save is in the year 2079 and I have had no issues with salary cap except for the one I did to myself (in a different save year 2044). I would like to have a higher than 44 mil salary cap but don't know enough about the editors to mess with them.
Re: 3 questions for those who have played 10-20 seasons or m
Posted: Wed Aug 17, 2011 3:56 pm
by pens66
There shouldn't be any major problems with the cap. At some points a couple of veterans may remain unsigned a couple of weeks into the season. But that's rare. Most problems actually occure by increasing the salary cap. The financial models of the game are made for the standard cap.
If you really intend to play a long game I can't see why you would choose a user db with tons of changes over the standard db. It only increases the risk of any glitches or corrupt savegames, but after only a couple of years there will be so many trades, signings, regens etc. that teams won't have a "recognizable face" anyway.