In-Testing: Task / Strike Force and Trial Missions
By
1_800_Spines,
Posted on: 2008-02-26 15:44 in CoH and CoV General Discussions
Huzzah! now I can solo Positron's TF like I wanted to.
This is a much more rational method of handling soft loading. I still feel some pain that there will be fewer Pool C recipes on the market, but at least this doesn't punish the wrong people. Perhaps the drop rates can be examined now that a source of artificial inflation will be removed.
One question, is there a method for the team leader to remove a player that DC'ed or logged off? If not, that might be nice QoL addition.
Thorizdin
Lords of the Dead
Old School Legends
I do like this change, Lighthouse. On paper, it's logical and if someone griefs by just logging out after helping you start then you can quit that TF and reform that TF again.
This still stops solo spawning and is fair to small teams.
EDIT: For Thor, maybe the team window never removes the name of the player if they're offline. So the color behind the name is black and to the right it says OFFLINE. Thus, the team leader still has he ability to kick. Here's the evil thing: Do not let a Pickup player get the star by being the 2nd or 3rd add.
Thank you, City of Heroes, for giving me a superhero social network combined with amazingly smooth game play. Petitions signed with realistic expectations.
This change and the previous one is bad because it still allows for some teammates to grief your team should they choose to log off and not quit. I have had it to happen twice since the first change on a few tfs I have done. Once on Katie hannon and once Sara Moore TFs. We need a way to be able to kick people from the team that are not currently logged in. Secondly neither of these changes have done anything to address the reason why this softloading of tf/sfs happens in the first place. If the recipes that people can actually use were more readily accessable we would not be going thru this now in the first place. Either address the issue with the drop pools or you are doing all this for nothing and all it is doing is punishing the rest of the playerbase instead of farmers.
Bump and Grind Bane/SoA
Kenja No Ishi Earth/Empathy Controller
Legendary Sannin Ninja/Pain Mastermind
Entoxicated Ninja/PSN Mastermind
Ninja Ryukenden Kat/WP Scrapper
Hellish Thoughts Fire/PSI Dominator
Thank You Devs for Merits!!!!
I really like that. I think it's more feasible.
How about allowing a Task Force to stay together with only one member? That way people can still solo Positron.
Doom.
Yep.
This is really doom.
Much better.
@Mental Maden @Maden Mental
"....you are now tackle free for life."-ShoNuff
[ QUOTE ]
This change and the previous one is bad because it still allows for some teammates to grief your team should they choose to log off and not quit. I have had it to happen twice since the first change on a few tfs I have done. Once on Katie hannon and once Sara Moore TFs. We need a way to be able to kick people from the team that are not currently logged in. Secondly neither of these changes have done anything to address the reason why this softloading of tf/sfs happens in the first place. If the recipes that people can actually use were more readily accessable we would not be going thru this now in the first place. Either address the issue with the drop pools or you are doing all this for nothing and all it is doing is punishing the rest of the playerbase instead of farmers.
[/ QUOTE ]
Understandable and thanks for the feedback. However, I would have to advise you to better get to know the people you are grouping with. Simply put, if someone has a reputation for such, don't engage in a task / strike force or trial with them. You would be well advised to only take your most trusted allies with you to tackle such challenging and dangerous missions!
Lighthouse
Community Relations Manager
If you have a specific in game, account, tech or billing problem please contact our Customer Support team via The Knowledge Base "Ask A Question" page.
This sounds like an improvement. So... a team won't be able to softload missions then get together for the reward at the end. Meanwhile, team attrition won't be punished.
I'd still like the minimum sizes of the TFs to be adjusted to the actual difficulty of the TF rather than level range on the hero side. But I suppose that issue has dropped to low or zero priority now.
This is a much better system than the force to minimum team size.
Thanks for listening.
@Catwhoorg "Rule of Three - Finale" Arc# 1984
@Mr Falkland Islands"A Nation Goes Rogue" Arc# 2369 "Toasters and Pop Tarts" Arc#116617
[ QUOTE ]
Understandable and thanks for the feedback. However, I would have to advise you to better get to know the people you are grouping with. Simply put, if someone has a reputation for such, don't engage in a task / strike force or trial with them. You would be well advised to only take your most trusted allies with you to tackle such challenging and dangerous missions!
[/ QUOTE ]
Blacklist, *chuckle*
I agree, though. Besides -- it'd take a concerted effort from multiple individuals to cause a significant strain on any well built team.
Doom.
Yep.
This is really doom.
Yeah, this is a better change and will still allow for the "Soloing" of many Task Forces.
Now, when will you guys address the anemic Villain Market?
How about a comment on the potential of a Merged Market environment?
Sign It : http://www.change.org/petitions/ncso...city-of-heroes
Thumbs up
[ QUOTE ]
[ QUOTE ]
This change and the previous one is bad because it still allows for some teammates to grief your team should they choose to log off and not quit. I have had it to happen twice since the first change on a few tfs I have done. Once on Katie hannon and once Sara Moore TFs. We need a way to be able to kick people from the team that are not currently logged in. Secondly neither of these changes have done anything to address the reason why this softloading of tf/sfs happens in the first place. If the recipes that people can actually use were more readily accessable we would not be going thru this now in the first place. Either address the issue with the drop pools or you are doing all this for nothing and all it is doing is punishing the rest of the playerbase instead of farmers.
[/ QUOTE ]
Understandable and thanks for the feedback. However, I would have to advise you to better get to know the people you are grouping with. Simply put, if someone has a reputation for such, don't engage in a task / strike force or trial with them. You would be well advised to only take your most trusted allies with you to tackle such challenging and dangerous missions!
[/ QUOTE ]
Not to be rude but thats crazy man. This game was designed not just teaming around friends but to also encourage making new ones. Otherwise you should limit teaming to only people in your sg or coalition. How can one detect a griefer if he/she is allowed to make a new toon? Should we make a blacklist for every server to keep an eye out for such people?
PuGs are very common in the CoX game and to use such restricted measures just to allow you to complete a tf/sf should be nulled and voided.
[ QUOTE ]
[ QUOTE ]
This change and the previous one is bad because it still allows for some teammates to grief your team should they choose to log off and not quit. I have had it to happen twice since the first change on a few tfs I have done. Once on Katie hannon and once Sara Moore TFs. We need a way to be able to kick people from the team that are not currently logged in. Secondly neither of these changes have done anything to address the reason why this softloading of tf/sfs happens in the first place. If the recipes that people can actually use were more readily accessable we would not be going thru this now in the first place. Either address the issue with the drop pools or you are doing all this for nothing and all it is doing is punishing the rest of the playerbase instead of farmers.
[/ QUOTE ]
Understandable and thanks for the feedback. However, I would have to advise you to better get to know the people you are grouping with. Simply put, if someone has a reputation for such, don't engage in a task / strike force or trial with them. You would be well advised to only take your most trusted allies with you to tackle such challenging and dangerous missions!
[/ QUOTE ]
On several TF's its already hard enough to get a big enough team together to run it(esp for the FP and Shard TF's) and many times you dont have the luxury of picking and choosing who is to use.
This also stops people who might drop out suddenly due to internet problems and such.
IMO all this change does it stop a few people from softloading, while punishes the rest of the player base becasue no matter how much you "prepare" there are going to be times where someone is going to drop out suddenly.
This is a much more equitable change than the previous implementation. Thanks for listening to us.
Tech Support Rule #1 - They will lie to you. Usually intentionally.
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
This change and the previous one is bad because it still allows for some teammates to grief your team should they choose to log off and not quit. I have had it to happen twice since the first change on a few tfs I have done. Once on Katie hannon and once Sara Moore TFs. We need a way to be able to kick people from the team that are not currently logged in. Secondly neither of these changes have done anything to address the reason why this softloading of tf/sfs happens in the first place. If the recipes that people can actually use were more readily accessable we would not be going thru this now in the first place. Either address the issue with the drop pools or you are doing all this for nothing and all it is doing is punishing the rest of the playerbase instead of farmers.
[/ QUOTE ]
Understandable and thanks for the feedback. However, I would have to advise you to better get to know the people you are grouping with. Simply put, if someone has a reputation for such, don't engage in a task / strike force or trial with them. You would be well advised to only take your most trusted allies with you to tackle such challenging and dangerous missions!
[/ QUOTE ]
On several TF's its already hard enough to get a big enough team together to run it(esp for the FP and Shard TF's) and many times you dont have the luxury of picking and choosing who is to use.
This also stops people who might drop out suddenly due to internet problems and such.
IMO all this change does it stop a few people from softloading, while punishes the rest of the player base becasue no matter how much you "prepare" there are going to be times where someone is going to drop out suddenly.
[/ QUOTE ]
It does put the control back in the players hands in all cases but a hard, irreconcilable loss of internet connectivity. Some examples:
Wife/Husband agro or a bad storm moving into your area that will likely cause you to have a power outage: Simply let the team know you need to go and quit the team and the spawns will scale down to the new team size.
Cat steps on your power strip, turning off your system: Well, the team will have to deal with you going Link Dead, but hopefully they can manage till you log back in.
Someone on your team is acting like a complete dork, agroing ahead, or otherwise placing the teams integrity in jeopardy: Have the team leader talk with them and if they can't settle down, remove them from the team and allow the spawn size to scale down to the new team size.
If you want to "solo" a Task Force (for example Positron)? Invite two others (since it is a min. 3 person to start) to start the Task Force and then have one quit. You need to have 2 people minimum in a Task Force / Strike Force or Trial for the mission chain to stay solvent. But hey, you can solo spawns for 2 with your settings on heroic, can't you? Or - duo it with a friend.
I hope those examples help.
Lighthouse
Community Relations Manager
If you have a specific in game, account, tech or billing problem please contact our Customer Support team via The Knowledge Base "Ask A Question" page.
Great move, Devs. Well done.
Story Arcs I created:
Every Rose: (#17702) Villainous vs Legacy Chain. Forget Arachnos, join the CoT!
Cosplay Madness!: (#3643) Neutral vs Custom Foes. Heroes at a pop culture convention!
Kiss Hello Goodbye: (#156389) Heroic vs Custom Foes. Film Noir/Hardboiled detective adventure!
Sounds good!
Solves the exploit without punishing people who have teammates drop or quit for whatever reason.
The Nethergoat Archive: all my memories, all my characters, all my thoughts on CoH...eventually.
My City Was Gone
you may all now shower your devotion upon me
linky 
Liberty
My 50s:
Hero: Armor Assassin (scrapper), Cross Dresser (scrapper), Surly Seaman (blaster), Defensive End (Tank), Rad Rhino (Cont)
Villain: Beast Infection (Corr), Sweet Zombie Jesus (MM), Milk Weasel (Stalker), Orgullo (MM), Agent Eris (Crab)
It's better but I would still like a feature to kick logged teammates.
This is a much better solution, thank you.
Please try my custom mission arcs!
Legacy of a Rogue (ID 459586, Entry for Dr. Aeon's Third Challenge)
Death for Dollars! (ID 1050)
Dr. Duplicate's Dastardly Dare (ID 1218)
Win the Past, Own the Future (ID 1429)
[ QUOTE ]
We need a way to be able to kick people from the team that are not currently logged in.
[/ QUOTE ]
This bears repeating.
Kudos to the devs for implementing this much more equitable fix.
[ QUOTE ]
[ QUOTE ]
This change and the previous one is bad because it still allows for some teammates to grief your team should they choose to log off and not quit. I have had it to happen twice since the first change on a few tfs I have done. Once on Katie hannon and once Sara Moore TFs. We need a way to be able to kick people from the team that are not currently logged in. Secondly neither of these changes have done anything to address the reason why this softloading of tf/sfs happens in the first place. If the recipes that people can actually use were more readily accessable we would not be going thru this now in the first place. Either address the issue with the drop pools or you are doing all this for nothing and all it is doing is punishing the rest of the playerbase instead of farmers.
[/ QUOTE ]
Understandable and thanks for the feedback. However, I would have to advise you to better get to know the people you are grouping with. Simply put, if someone has a reputation for such, don't engage in a task / strike force or trial with them. You would be well advised to only take your most trusted allies with you to tackle such challenging and dangerous missions!
[/ QUOTE ]
Sometimes there are not enough trusted allies online to tackle such challenging and dangerous missions. It's the ridiculous minimum team size that causes you to pickup whoever you can find to start the TF's that require 7-8 team members. Please reduce the initial team sizes to something reasonable, like 4 members except for the STF and LRSF.
On February 12th, we introduced a change to Task / Strike Force and Trial Missions whereby the monster spawns would not scale down below the required number of players needed to start the mission. To further refine this change we are currently testing a revision to this functionality on the Training Room Test Server. From the Patch Notes
[ QUOTE ]
Task Force/Strike Force and Trial Missions
The size of spawns in Task Force/Strike Force missions will always be based on the number of players in a Strike Force/Task Force, regardless of whether they are logged on or not.
Spawns for Task Forces/Strike Forces no longer have a minimum size that they will not scale below.
8 Person Task Force Example:
8 players begin an 8 player Task Force and then 7 people LOG OFF. The spawns in the Task Force will still scale to the 8 players attached to the Task Force (regardless of whether they are logged on or not).
If instead of logging off, 6 of the players QUIT the 8 person Task Force, then the Spawns will scale down to the remaining 2 players on the Task Force.
[/ QUOTE ]
Please use this thread to discuss the above proposed change currently under testing. For actual discussion based on your play experience, please visit the Training Room Test Server Forums.
Lighthouse
Community Relations Manager
If you have a specific in game, account, tech or billing problem please contact our Customer Support team via The Knowledge Base "Ask A Question" page.