Bort -- hoping you are still watching this thread.
Your comment on the first page about poorly built CBs and their whiny agents struck me as odd.
When you implement a code fix do you "release it to the wild" and have us test it for you as the first check to see how well your tweak worked, or do you have a few "test teams" built that you use to see if the game mechanics are working as you intended?
If you use us, that's obviously fine since this is a beta test community. But, I would argue that you'd get much better results from having two teams built that only exist as a test case for your code changes. You could build a prototype player for each position (not one that's a monster, but one that generally fits the way you think an 'average' player would look like at that position) and run a sim game between the two test teams each time you implement a fix.
As an extra layer of transparency you could open the builds of these players and post the game results of your tweaked settings to the change log. This would let you very publicly show what you are doing and why and simultaneously give all the whiny-assed agents out there who are looking for every possible exploit a reason to shut up and build a more balanced player instead of min/maxing everything.
I am sure there are people who will not like this idea because it will be providing a defacto build standard for players...so another way to handle this might be to give all the players the exact same number in every attribute..say 50. That way you could also very clearly see which attributes are too powerful in relation to others.
You've obviously done a great job putting all this game together so far, so maybe I wasted my time putting this recommendation together, but I figure it is worth it on the off chance that some of this is helpful to you.
-- John
Your comment on the first page about poorly built CBs and their whiny agents struck me as odd.
When you implement a code fix do you "release it to the wild" and have us test it for you as the first check to see how well your tweak worked, or do you have a few "test teams" built that you use to see if the game mechanics are working as you intended?
If you use us, that's obviously fine since this is a beta test community. But, I would argue that you'd get much better results from having two teams built that only exist as a test case for your code changes. You could build a prototype player for each position (not one that's a monster, but one that generally fits the way you think an 'average' player would look like at that position) and run a sim game between the two test teams each time you implement a fix.
As an extra layer of transparency you could open the builds of these players and post the game results of your tweaked settings to the change log. This would let you very publicly show what you are doing and why and simultaneously give all the whiny-assed agents out there who are looking for every possible exploit a reason to shut up and build a more balanced player instead of min/maxing everything.
I am sure there are people who will not like this idea because it will be providing a defacto build standard for players...so another way to handle this might be to give all the players the exact same number in every attribute..say 50. That way you could also very clearly see which attributes are too powerful in relation to others.
You've obviously done a great job putting all this game together so far, so maybe I wasted my time putting this recommendation together, but I figure it is worth it on the off chance that some of this is helpful to you.
-- John






























