Main Site | Forum | Rules | Downloads | Wiki | Features | Podcast

NLSC Forum

Talk about NBA Live 06 here.
Post a reply

custom trades with NBA live 2006 Editor or .dbf commander

Sun Dec 12, 2010 4:09 am

Hi,

i made the experience that some trades just don't work. The Dynasty crashes after some days /weeks mostly end of a month.

Some trades work fine , i play with them some seasons without a problem.

Is this maybe a salary or contract thing? or maybe something else... i think i have to live with that

Maybe to much players in the roster..

I make backups and simulate the whole season after a trade to be kind of sure ... :?

Re: custom trades with NBA live 2006 Editor or .dbf commande

Sun Dec 12, 2010 11:06 am

Most likely there's an incorrect or conflicting value somewhere.

Re: custom trades with NBA live 2006 Editor or .dbf commande

Mon Dec 13, 2010 1:04 am

I noticed that to the beginning of the season some teams had to much players. Now that a few weeks are gone the remaining were automatically released by their teams.
I tested some trades again and now they work.

Re: custom trades with NBA live 2006 Editor or .dbf commande

Mon Dec 13, 2010 8:45 am

Ah, so there were a few teams with more than 15 players?

Re: custom trades with NBA live 2006 Editor or .dbf commande

Mon Dec 13, 2010 7:38 pm

Yes some had 16, i noticed that when i tried to trade in game and there was a -1 number for available slots.

After some days / weeks the 16th player was automatically released by the CPU.

I also made another fault, i think i traded someone from my own team, i read in another topic that this action will crash a dynasty too, because the players of the custom team have two IDs or something like that.


Now that i am aware of theese problems it works.

I simulated about 10 times and nothing happened , so i hope for the best . :bowdown: :bowdown2:

Re: custom trades with NBA live 2006 Editor or .dbf commande

Mon Dec 13, 2010 9:04 pm

That's right, trading players on your own team is usually problematic. Glad to hear it appears to have been resolved though. (Y)
Post a reply