Jump to content

TemporalVileTerror

Members
  • Content Count

    191
  • Joined

  • Last visited

Community Reputation

168 Excellent

About TemporalVileTerror

  • Birthday 10/31/1977
  1. Yup. We're keeping our Netflix, but spouse cancelled AmazonPrime to make room for the new Disney Star. Eventually we'll cancel Disney when we've watched what we want to and possibly switch back to Prime for a while longer. Still really skeezy business practices, though.
  2. X-Ray Beam has an Activation time of 1.67s, so it's animation is roughly that long. Cutting Beam has a 1.9s Activation. While I'd personally be okay with padding out the extra time with a bit of animation hang, I expect the Dev Team might not be (based on some of the other statements they've made about graphic quality over the past two years). So, sadly, there is a little bit of an extra hurdle in the way here. Hopefully one which can be overcome, though. The changes to Total Focus suggest the Devs now have the tools necessary to make adjustments like this feasible.
  3. Another point of these being volunteer devs means that even if no one on the team currently has the time for this suggestion, that doesn't preclude the possibility of a new dev joining the team who focuses on this as their personal pet project. Suggestions are good. End of story. No one here is making demands. Stating that something may not be feasible due to scope is fair, but even then an expert opinion is more valuable than a guess made by one of us. Stating an idea sounds personally worthwhile or not is subjective, but fair. Stating if something is or isn't worth the devs' time is up to the devs.
  4. A Level Boost for Sidekicks/Lackeys could be treated as a PBAoE Buff, originating from the Team Leader. How many complaints do we have about the Range on the Leadership Buffs? Err on the side of caution and make the Level Boost Buff radius a bit larger than Leadership. Hell. Maybe even introduce the Level Boost Buff in to the existing Leadership Buffs.
  5. Also, another small note: Sorry @GM Tahquitz and everyone. I meant @Telephone when I had said "Lighthouse" in https://forums.homecomingservers.com/topic/22631-hey-devs-can-you-please-some-or-all-of-this-to-hc/page/3/?tab=comments#comment-327004. I had forgot to do my fact-check there.
  6. It actually does scratch the surface, and I really appreciate you taking the time to post it, @Number Six. Thank you.
  7. Neirsa (sorry if I misspelt that) was terrifyingly resilient during that time she was thrown in to the cage. I'm going to have to invest in some lower level characters to Malefactor the volunteers down far enough next time.
  8. Lots, and lots, and lots to reply to (and I'll try to find some time this week) . . . but, specifically to that last message: It doesn't hurt to try. Let's try.
  9. Thank you again for your insight, @Naomi. I suppose my point is: Do you -ever- hear the end of it, even now? I've personally never worked on a project quite like this. No commercial obligations, but also not entirely an original, personal hobby project. There's a LOT about Homecoming which is uncharted territory, and I have personally hoped from the beginning that it would afford this community the opportunity to move away from old, harmful development models. The hope that not only would Homecoming be a second chance for City of Heroes, but a chance to explore methods of de-industrialization of game development. If the sentiment is that the gamer metaculture is still much too toxic to permit for a safe space to fail, I can't fault that. There have definitely been years upon years of that attitude being intentionally cultivated as part of marketing ploys. I suppose part of me wants to believe that this game's community would step up and try to combat that. It's one of those things that I wanted to see from Homecoming's development back when we were asked about it in 2019. My hope has been for the Devs to extend the initial olive branches, and then reinforce them through community efforts. I don't want to assume anyone's lived experiences. I hope that no one on the Homecoming Dev Team has had to suffer in their professional career, but with how far reaching things have been and continue to be, I suspect that you each at least know someone who has suffered or had their passion exploited. Abuse thrives in hidden places. And I'm not saying the Homecoming Team are being abusive by keeping things hidden. But it is something we've been groomed to do by abusers. The culture of "keep it secret, keep it safe" is one which has allowed for so many problems to take such deep roots, especially in the games industry. So . . . magical imaginary theoretical situation: If the community could self-reflect enough to maintain an emotionally safe space for the Devs to share their failures without the passionate players being bent out of shape, do you (or anyone) have any additional insights on how to move toward that? What would you like to see from the community to improve communication on our end? (and not to totally subvert my own efforts here, but I would like to circle back to clarifying the core philosophies some day too. But I figure we should focus on this other stuff for now.)
  10. In the context of a for-profit venture, I could see someone in management making that argument (and have, numerous times). Operating in that paradigm, there's this belief that "angry gamers won't buy our product, so don't do anything to make them angry." But given that we're operating in a situation where there isn't anyone's continued employment hinging on a certain subscriber base value and other Servers with divergent development branches exist, can you elaborate on any specific impact in your example which wouldn't be addressed by broadening the pool of available testers and input, and providing clear design goals in that scenario? If some unreasonable people are hindering testing and feedback efforts due to their personal beliefs and expectations, having a larger pool of potential testers would help overcome that issue by default. Additionally, even before that, having clearly defined philosophies and goals provide leadership something to point to and say "this is what we're looking for here." I'm unsure of what this nebulous scenario you're describing is exactly @Galaxy Brain, so I can't provide you with a more meaningful potential solution . . . which just circles back to exactly what the problem I've been describing is. Keeping things "in the dark" just hinders the overall development cycle. Educating everyone creates a massive resource to tap in to for better results.
  11. Yeah, but having to sign away a part of your soul to get a membership card is kind of annoying.
  12. Given this games' ludonarrative? I rather think one -could- just pick up those Incarnate abilities at CostCo these days.
  13. Wholeheartedly agree, @RunoKnows. There are a lot of existing animations which could be utilized. About the only thing that would need to be addressed are animation times and activation times. Not an insignificant amount of work, but clearly one that would be well worth the investment.
  14. Absolutely. And as breath/spit attack animations. And similarly using the death ray to fire off Fire Blasts, Ice Blasts, Radiation Blasts, et cetera. In other words: ALL the customization!
  15. Thank you very much for taking the time to compose that thoughtful message, @Naomi. It's hits upon a lot of what I've been striving to see expressed by members of the Homecoming Team. Hopefully it's a message we can use to address concerns as they come up by other community members. Also, hopefully, it's the sort of thing which other Devs can find a little time to expand upon with their own personal points of view. I do have to question the part which says: "... avoid disappointing anyone if things take a different turn and we can't deliver." It's a sentiment I've seen expressed a number of times, but I just don't get it. My perspective may be narrow here, but it seems a little misguided to me to think that a lack of information prevents disappointment. The disappointment exists whether something was expressly considered and unobtained, or if it is quietly unobtained the whole time. At most, the disappointment is merely not expressed if there isn't the prompt. In fact, for me, knowing that something is on the Devs' radar gives me hope, even when its not implemented. It gives perspective and context; important clues as to what the future has in store. More information allows for better decision-making. For example, a Dev had once spoken about allowing for RGB Hex code to be used for costume colourization. Even if that never comes to pass, it's heartening to know that someone on the team cares about an improvement like that. To know that it's not considered undesirable. I do want to emphasize that I'm not asking for things on deadlines, as there seems to be regular misinterpretation in that regard by several community members. I am more than happy to have the team take their time. I'm asking for foundational work in communication. And I appreciate the efforts you have made here today. Thank you.
×
×
  • Create New...