Xiphias, thank you. I thought the game against the Bobcats would be tougher, but I managed to shut them down pretty well.
Clutch, Q-Ross will play! I promise! Right now, though, I'm trying to find the right starting 5 more so than anything else, and Ross certainly doesn't enter into that equation. But he will play a lot more once I get that settled. I love his perimeter D. As for a Raps/Rockets finals, I'm gonna go out on a limb and say it's unlikely that I make it to the finals this year. I'll be happy with a 1st round win.
Marquis, thanks a fucking lot, man!

Just kidding. I really appreciate your comments, but unfortunately I think you might be disappointed in Daniels performance. The Pacers still have Jackson and Granger ahead of him, so significant PT will be hard to come by. I actually wish I could trade for him, cause I really dig Daniels in real life, but his contract is too big and too lengthy for me to be able to afford it and still stick to my building strategy.
Lamrock, thanks to you, as well. Yeah, we're struggling slightly, but it's still early, and like I said, I'm trying to find the best starting 5 right now, so some ups and downs are to be expected. We rip it up in games I play, though (which is only the "NBA TV Game of the Week"), but I guess that's to be expected.
SpaceFlare, as usual the bulk of the moves ar done by the CPU, but a few were done by me. So far this year, the only ones I forced were the Magic signing Walton (they needed help in the worst way, and with Walton coming off a MIP award, it seemed like he'd be the guy Orlando would target), the Heat signing George (also needed help badly, and I figured it made sense with George having played with O'Neal in LA, and the fact that he's a vet and Miami is still in "win now" mode), and Stevenson to New York (they really needed big man help, but the quality big men left were few, so I went with the proud Knick tradition of signing the best available guy, regardless of how well he fits the team). All other roster moves were done by CPU, though I did edit a lot of guys desired contracts so that teams would actually sign them.
But this raises a good question, I think. Do you guys think I should somehow indicate the moves I've forced versus the CPU moves? Maybe with an asterix or something. Is that something you guys feel would improve the dynasty, or does it not really matter either way? Bear in mind I don't make rash decisions for other teams. It's all carefully thought out, weighing things like team record, team needs, and where the team is in terms of rebuilding, or "win now", or what have you. I guess indicating the forced moves could open up more interaction, with people then being able to question why I've made specific moves, which would be a good thing. On the other hand, I'm not really too interested in hearing things like "you shouldn't have signed that guy, he sucks", or "this team ripped off this team in this trade", without any thought to what a team's particular needs might be. It's not that I'm not open to criticism, I just don't want to get bombarded with baseless criticism. Everyone has preconceived notions of a player's worth, but I've been trying really hard to throw that out the window when evaluating potential roster changes and work only with team needs.
So after all that rambling, what do you guys think? Indicate forced moves, or no?
Week 4 up soon, and then after week 5, some monthly recap action, stats leaders, MVP and ROY race updates, and some manner of article or something about the Raps (haven't decided the specifics of the last part).