That's the purpose of the penalty SA tree - give people the option to use it, but at a known cost. It's not meant for power backs to be using elusive abilities or elusive backs to be using power back abilities. It's the main purpose of the penalty SA's. It makes the archetypes have unique value in that they are the one position that can fully utilize a specific tree.
reedric
offline
offline
Originally posted by Catch22
That's the purpose of the penalty SA tree - give people the option to use it, but at a known cost. It's not meant for power backs to be using elusive abilities or elusive backs to be using power back abilities. It's the main purpose of the penalty SA's. It makes the archetypes have unique value in that they are the one position that can fully utilize a specific tree.
Then the whole tree should be penalized, not just 2 branches of it. If the goal is to discourage a powerback from using elusive abilities make the cost higher, IMO.
Don't take me the wrong way here, I like all the proposed changes except this one. The game has needed a way to open up build plans for a long time, but I think this will limit the builds a little because a vet of the game is not going to be wasting SP in an SA that will not give them what their paying for.
That's the purpose of the penalty SA tree - give people the option to use it, but at a known cost. It's not meant for power backs to be using elusive abilities or elusive backs to be using power back abilities. It's the main purpose of the penalty SA's. It makes the archetypes have unique value in that they are the one position that can fully utilize a specific tree.
Then the whole tree should be penalized, not just 2 branches of it. If the goal is to discourage a powerback from using elusive abilities make the cost higher, IMO.
Don't take me the wrong way here, I like all the proposed changes except this one. The game has needed a way to open up build plans for a long time, but I think this will limit the builds a little because a vet of the game is not going to be wasting SP in an SA that will not give them what their paying for.
Originally posted by reedric
Then the whole tree should be penalized, not just 2 branches of it. If the goal is to discourage a powerback from using elusive abilities make the cost higher, IMO.
Don't take me the wrong way here, I like all the proposed changes except this one. The game has needed a way to open up build plans for a long time, but I think this will limit the builds a little because a vet of the game is not going to be wasting SP in an SA that will not give them what their paying for.
That's pretty much what it does, it gives you .8 in stead of 1 for your SP, but it still shows up as a 1 (rough example). If you're just putting points into it to get to the next one on the tree it wont hold you back like increased cost would. If it cost more like the 5th spot does, it would hinder pumping the SAs above it.
Then the whole tree should be penalized, not just 2 branches of it. If the goal is to discourage a powerback from using elusive abilities make the cost higher, IMO.
Don't take me the wrong way here, I like all the proposed changes except this one. The game has needed a way to open up build plans for a long time, but I think this will limit the builds a little because a vet of the game is not going to be wasting SP in an SA that will not give them what their paying for.
That's pretty much what it does, it gives you .8 in stead of 1 for your SP, but it still shows up as a 1 (rough example). If you're just putting points into it to get to the next one on the tree it wont hold you back like increased cost would. If it cost more like the 5th spot does, it would hinder pumping the SAs above it.
PDO
offline
offline
I don't understand why the archetypes were beaten down as much as they were.... doesn't it defeat the whole purpose if the difference between builds are so minimal?
I liked having some .67's and such... created a lot more variety.
Just randomly subbing one major for one minor all over the place is pretty... meh.
I liked having some .67's and such... created a lot more variety.
Just randomly subbing one major for one minor all over the place is pretty... meh.
reedric
offline
offline
Originally posted by Fumanchuchu
That's pretty much what it does, it gives you .8 in stead of 1 for your SP, but it still shows up as a 1 (rough example). If you're just putting points into it to get to the next one on the tree it wont hold you back like increased cost would. If it cost more like the 5th spot does, it would hinder pumping the SAs above it.
But I'm saying if thats the goal, then penalize the whole tree.
And it will hinder pumping the SAs above it, if i want to get the one above it to 10, I will have to put 9 SP into the penalty SA, thats 2 levels on something giving me less bang for my buck.
I'm not even sure this will be an issue, but I'm sure some of the builds will be able to utilize both trees effectively. I would even be okay if the cost of an SA went up if I could skip around if I want to, at least I would know I'm getting full value for my SP.
That's pretty much what it does, it gives you .8 in stead of 1 for your SP, but it still shows up as a 1 (rough example). If you're just putting points into it to get to the next one on the tree it wont hold you back like increased cost would. If it cost more like the 5th spot does, it would hinder pumping the SAs above it.
But I'm saying if thats the goal, then penalize the whole tree.
And it will hinder pumping the SAs above it, if i want to get the one above it to 10, I will have to put 9 SP into the penalty SA, thats 2 levels on something giving me less bang for my buck.
I'm not even sure this will be an issue, but I'm sure some of the builds will be able to utilize both trees effectively. I would even be okay if the cost of an SA went up if I could skip around if I want to, at least I would know I'm getting full value for my SP.
chazno
offline
offline
Originally posted by Catch22
Yes you will.
Since there is such a craze to make things equal are the SAs going to be reordered so that the bonuses and penalties are at the same level across all archetypes?
Since we are forced to move up the tree, we will be forced to take penalty SAs if we want to invest in later non-penalized ones.
Example:
A hard hitting LB penalty SAs are at positions 4 and 5 in the Pass Rusher Tree. He can take Shed Block to 10 at position #3 without any penalty.
A Blitzing LB has Penalty SAs at positions 2 and 3 in the Hard Hitter Tree. If he too wanted to pump position #3 to 10, he would have to raise a penalized SA (that he may not even want) to 5 (9 SPs) just to achieve the same thing.
Yes you will.
Since there is such a craze to make things equal are the SAs going to be reordered so that the bonuses and penalties are at the same level across all archetypes?
Since we are forced to move up the tree, we will be forced to take penalty SAs if we want to invest in later non-penalized ones.
Example:
A hard hitting LB penalty SAs are at positions 4 and 5 in the Pass Rusher Tree. He can take Shed Block to 10 at position #3 without any penalty.
A Blitzing LB has Penalty SAs at positions 2 and 3 in the Hard Hitter Tree. If he too wanted to pump position #3 to 10, he would have to raise a penalized SA (that he may not even want) to 5 (9 SPs) just to achieve the same thing.
Edited by chazno on Feb 12, 2010 21:05:03
chazno
offline
offline
Originally posted by Catch22
That's the purpose of the penalty SA tree - give people the option to use it, but at a known cost. It's not meant for power backs to be using elusive abilities or elusive backs to be using power back abilities. It's the main purpose of the penalty SA's. It makes the archetypes have unique value in that they are the one position that can fully utilize a specific tree.
For all the talk about this opening up new possibilities for build, doesn't this just sound restrictive.
The only thing about archetypes that is opening up new possibilities is the choose a new SA (something we had with AEQ).
The new ALGs allow new (not necesarily better) levels of base attributes, but that doesn't open new possibilities.
The the penalty SAs are just a preemptive nerf. Say you chose power back, and in season 16 'Power thru' is nerfed into inneffectiveness. No problem just move some equipment and become a Combo, but wait, your elusive SAs are already nerfed with penalties.
That's the purpose of the penalty SA tree - give people the option to use it, but at a known cost. It's not meant for power backs to be using elusive abilities or elusive backs to be using power back abilities. It's the main purpose of the penalty SA's. It makes the archetypes have unique value in that they are the one position that can fully utilize a specific tree.
For all the talk about this opening up new possibilities for build, doesn't this just sound restrictive.
The only thing about archetypes that is opening up new possibilities is the choose a new SA (something we had with AEQ).
The new ALGs allow new (not necesarily better) levels of base attributes, but that doesn't open new possibilities.
The the penalty SAs are just a preemptive nerf. Say you chose power back, and in season 16 'Power thru' is nerfed into inneffectiveness. No problem just move some equipment and become a Combo, but wait, your elusive SAs are already nerfed with penalties.
Edited by chazno on Feb 12, 2010 21:17:27
ijg
offline
offline
curious, what was the logic between forcing players up to 80 days old (i.e. s13 and 14 builds) to have to choose an AT vs prior guidance that it would be optional?
Is there some exploit you're concerned about catch?
For those of us who created farm teams in s13 that we need to replace other farm teams in the future, this is a real conundrum. I'm sure it will be fine for some players but for others where we capped supporting attributes because they were majors and now they're going to minors and skipped minors that now become majors, it kind of bamboozles the build.
For example, today when you build a power WR, you still start with speed/agility and carry and wait on strength because there is no point in training strength for a long time. Well, now if I choose power WR, my str is leveling but I haven't trained it for two seasons and I've lost out on gains I expected on carry and speed. Totally gimps the build or I have to morph into a possession WR (too slow to be a speed WR, so not an option).
I'm sure I can come up with more examples with more time to think about it. Not to mention I've crafted build plans that assume caps are hit in a certain order that now have to be torn up because they will be hitting the decimal for the next cap either much sooner or later and I may not have the SP to hit a cap at the optimal level now.
Again, I'm not saying it's a terrible decision and I'm sure there are cases where it's helpful, but there are definitely cases where it hurts. And just saying "oh, go retire your players then" doesn't really help if you planned out to need those players available down the road at a certain time to take over from other retiring players.
Is there some exploit you're concerned about catch?
For those of us who created farm teams in s13 that we need to replace other farm teams in the future, this is a real conundrum. I'm sure it will be fine for some players but for others where we capped supporting attributes because they were majors and now they're going to minors and skipped minors that now become majors, it kind of bamboozles the build.
For example, today when you build a power WR, you still start with speed/agility and carry and wait on strength because there is no point in training strength for a long time. Well, now if I choose power WR, my str is leveling but I haven't trained it for two seasons and I've lost out on gains I expected on carry and speed. Totally gimps the build or I have to morph into a possession WR (too slow to be a speed WR, so not an option).
I'm sure I can come up with more examples with more time to think about it. Not to mention I've crafted build plans that assume caps are hit in a certain order that now have to be torn up because they will be hitting the decimal for the next cap either much sooner or later and I may not have the SP to hit a cap at the optimal level now.
Again, I'm not saying it's a terrible decision and I'm sure there are cases where it's helpful, but there are definitely cases where it hurts. And just saying "oh, go retire your players then" doesn't really help if you planned out to need those players available down the road at a certain time to take over from other retiring players.
Edited by ijg on Feb 13, 2010 12:18:42
Finnude
offline
offline
My first question is, will we have option to get refund on flexpoints we have bought as you are probably making huge change in this game and thats not what we have paid for to play. I have spent lot of time building my players and a lot of flex has been burnt too and I am not sure at this point the newer version is something I want to play of pay for playing it. Yeah I know that your terms of use says sales are final, but that doesnt mean that if you wanted to provide refunf you wouldnt be ablo to provide such option. The reason I am asking this is that are you so confident that this little "improvement" you are about to introduce is so needed and brings so much more enjoyment to your customers that they will love the change and they would not opt on refund. In my opinion if you dont have the guts to offer such option, you should consider twhether this "improvement" actually is this needed at this point.
My second question is that why are you not giving us 100% return on flex when retiring players due to the fact that YOU are bringing these changes quit unexpectedly and many of us have just created players within few seasons. This game is about longterm planning and YOU are now ruining them. So again I am asking is this improvement so important that it is needed with rather short time warnign and making people lose flexpoints due to the fact that they have palnned longterm players and now you are changing the rules. I now I would like to know why this info is given right after new season has started and many players have already spent flex on boosting for this season, I am sure this idea didnīt born on day -6 of this season. So if you had this idea before this season, why not start discussion before that -> again i consider time of this announcement as cheating agents to spend flex on boosting for this season and only afterwards telling them that your player will probably be retired early but thanks for spending extra flex.
And as you are making these "improvements" would it be time to move from beta to final version, where every second season some major changes are not introduced. It annoying to start longterm projects on players and jst to find out that I have done useless players and still lose flex as rules change. So what is this hurry to make chages but DO YOU HAVE DATE SET UP FOR RELEASING FINAL VERSION? I am sure I am not the only one who see bigger problems withing the machine running games that in the builds of players. So have you spent 90% of your development time on fixing game instead of making cahnges on stuff that at least work on some level compared to you engine running the games. So why not announce that final version of this game will be on 1.1.2011 and rest of this season you will be running this and two other seasons and after that you will have new and better game - and reset for everything...
And while we are at this introducing stuff all the time, it gives me bad impression of you testing this stuff. How come new VAīs and VA+s are tweaked on every season - cannot you test and plan the stuff you make. All these minor changes give me very bad impression of your skills on planning, testing and implementig stuff. Please dont plan stuff just for a week or season ahead but do bigger plans for final version and DO TEST WELL BEFORE INTRODUCING ANYTHING NEW so that after introduction you dont have to fix it all the time. Every fix that you make after releasing stuff to this game gives you a mark of shame for BAD SOFTWARE DEVELOPMENT.
Argh this post is already too long so iīll stop writing more stuff here and see if any official comments are given development of this game by this company or am I just wasting my time.
My second question is that why are you not giving us 100% return on flex when retiring players due to the fact that YOU are bringing these changes quit unexpectedly and many of us have just created players within few seasons. This game is about longterm planning and YOU are now ruining them. So again I am asking is this improvement so important that it is needed with rather short time warnign and making people lose flexpoints due to the fact that they have palnned longterm players and now you are changing the rules. I now I would like to know why this info is given right after new season has started and many players have already spent flex on boosting for this season, I am sure this idea didnīt born on day -6 of this season. So if you had this idea before this season, why not start discussion before that -> again i consider time of this announcement as cheating agents to spend flex on boosting for this season and only afterwards telling them that your player will probably be retired early but thanks for spending extra flex.
And as you are making these "improvements" would it be time to move from beta to final version, where every second season some major changes are not introduced. It annoying to start longterm projects on players and jst to find out that I have done useless players and still lose flex as rules change. So what is this hurry to make chages but DO YOU HAVE DATE SET UP FOR RELEASING FINAL VERSION? I am sure I am not the only one who see bigger problems withing the machine running games that in the builds of players. So have you spent 90% of your development time on fixing game instead of making cahnges on stuff that at least work on some level compared to you engine running the games. So why not announce that final version of this game will be on 1.1.2011 and rest of this season you will be running this and two other seasons and after that you will have new and better game - and reset for everything...
And while we are at this introducing stuff all the time, it gives me bad impression of you testing this stuff. How come new VAīs and VA+s are tweaked on every season - cannot you test and plan the stuff you make. All these minor changes give me very bad impression of your skills on planning, testing and implementig stuff. Please dont plan stuff just for a week or season ahead but do bigger plans for final version and DO TEST WELL BEFORE INTRODUCING ANYTHING NEW so that after introduction you dont have to fix it all the time. Every fix that you make after releasing stuff to this game gives you a mark of shame for BAD SOFTWARE DEVELOPMENT.
Argh this post is already too long so iīll stop writing more stuff here and see if any official comments are given development of this game by this company or am I just wasting my time.
Nice wall of text.
Do you actually expect a response when you do that?
But because I am lame enough to read some of that, I gotta ask, are YOU a businessman?
Cuz offering people hundreds of dollars to quit buying your product is pure business genius. I think Bort should hire you as his marketing adviser.
Do you actually expect a response when you do that?
But because I am lame enough to read some of that, I gotta ask, are YOU a businessman?
Cuz offering people hundreds of dollars to quit buying your product is pure business genius. I think Bort should hire you as his marketing adviser.
Edited by Fumanchuchu on Feb 12, 2010 23:24:47
MadMike52
offline
offline
I can't understand why a combo TE would have jumping as a minor but a receiving TE wouldn't.
Originally posted by reedric
But I'm saying if thats the goal, then penalize the whole tree.
And it will hinder pumping the SAs above it, if i want to get the one above it to 10, I will have to put 9 SP into the penalty SA, thats 2 levels on something giving me less bang for my buck.
I'm not even sure this will be an issue, but I'm sure some of the builds will be able to utilize both trees effectively. I would even be okay if the cost of an SA went up if I could skip around if I want to, at least I would know I'm getting full value for my SP.
That's why they didn't penalize the whole tree. Using LB as example, Currently, if you want to use the hard hitter tree, you have to put points into snarl no matter what, that SA doesn't do anything, yet people still put points in it to get to Aura. The whole point of the tree is to make the good ones hard to get to. You've always had to put points into something you don't want, and it's not like they'll be rendered useless, they'll just become something you don't want to build your dot around. If you are building an HB that Jukes and Breaks tackles, use combo and take the hit in ALGS, or use elusive and take the hit in SAs.
But I'm saying if thats the goal, then penalize the whole tree.
And it will hinder pumping the SAs above it, if i want to get the one above it to 10, I will have to put 9 SP into the penalty SA, thats 2 levels on something giving me less bang for my buck.
I'm not even sure this will be an issue, but I'm sure some of the builds will be able to utilize both trees effectively. I would even be okay if the cost of an SA went up if I could skip around if I want to, at least I would know I'm getting full value for my SP.
That's why they didn't penalize the whole tree. Using LB as example, Currently, if you want to use the hard hitter tree, you have to put points into snarl no matter what, that SA doesn't do anything, yet people still put points in it to get to Aura. The whole point of the tree is to make the good ones hard to get to. You've always had to put points into something you don't want, and it's not like they'll be rendered useless, they'll just become something you don't want to build your dot around. If you are building an HB that Jukes and Breaks tackles, use combo and take the hit in ALGS, or use elusive and take the hit in SAs.
Edited by Fumanchuchu on Feb 12, 2010 23:35:26
Maddoc
offline
offline
Using LB SAs as anything other than a cautionary tale of how bad your position could have it is probably a bad idea tbh
Originally posted by Maddoc
Using LB SAs as anything other than a cautionary tale of how bad your position could have it is probably a bad idea tbh
Yeah, my point does ride on Aura being worth a damn. Not a great foothold for argument
Change that example to Glare and Shed Blocks on a DT then.
Using LB SAs as anything other than a cautionary tale of how bad your position could have it is probably a bad idea tbh
Yeah, my point does ride on Aura being worth a damn. Not a great foothold for argument
Change that example to Glare and Shed Blocks on a DT then.
You are not logged in. Please log in if you want to post a reply.






























