Development Cycle Archive
Thread: FINAL RESOLUTION ON DECAY: 1% Decay will be gone with the Imperial Crackdown
Greets ...
I wonder how many folks picked up on the simply statement:
Back in November
That's right .. November ... which was followed by December which was followed by January ...
Development takes time ... it's not a quick fix here or there ... it's not decide today and do tommorrow, or next week, or even next MONTH.
I hope folks that read this thread read this message and start to appreciate what a *long* road the Dev's have and learn just a bit of patience.
BigSteve03 wrote:
I'm happy about the change, but I feel bad for the programmer who had to work (probably) most nights and all weekend long to get this change into this publish just because some people couldn't accept a simple mistake and wait a little longer for the change.
It must've been a lot easier to code up than that "day pass" thing would have been. One of the reasons I was so against that idea was that it seemed like a waste of dev resources when simpler solutions existed.
Yay for the simple solution! I was hoping the 1% decay on insured items would go away entirely (leaving them to the mercies of use-based decay alone as long as we kept paying our 5k each death), but having insurance work "correctly" for factioned death at least means I can go do faction missions without leaving all my survey tools at home. ![]()
It looks like I will have to start moaning and whining an awful lot more and being rude and demanding to get the backpack sort order to save and the "Fade Objects" setting to stay set between log ins and the column width saved for the bazaar. It seems to be the only thing that gets any attention. You can post plenty of contructive posts requesting positive changes to the game, but in the end the negative ranting posts seem to get the changes pushed through.
Don't get me wrong, I am 100% for this change, but it's almost like you are encouraging the horrible behavior of all the forum trolls who treat everyone like dirt and piss and moan non stop. What a disappointment.
Pretty soon, we'll see wookiees in full composite, Combat Medics will be nerfed beyond recognition and there will be swarms of Jedi all over the place.
This is great news but it sounds likea griefer hole exists here. Some poeple will incapitate you three times instead of DB'n you which will fustrate many. Still nice to see that SOE tries to listen to its player base /cheer.
TH - I have a wish ... any chance you could ask the devs to fix our HAM bars whenwe have buffs on. In PvP situations it is kinda of important to know the status of your HAMs. It is kinda silly to have to tell someone in your group to heal because they are almost dead and they don't even know it.
SirKnightTerry wrote:Well you got it half right. This should be lifted for PVE as well. I mean if its bad for PVP why is it not bad for PVE. We who do not want to participate in PVP are gradually being pushed out. I mean look at the Crack Down now even though we dont want to participate we will be scanned and penalized. I have gone from playing 6 hours or more a night at first to playing maybe an hour a week or less. The game was fun at first now because of constant changes what was fun you can no longer do. I loved logging on and if I could not find a group quick to hunt I would go by myself solo. That is getting to be more and more difficult. You are completely in my opinion trying to minimize solo play. Why?
Oona
The primary difference being, Attacking or defending a base, you can die several times in several minutes. How often do you die against mobs? If it's that frequent, might want to rethink your tactics.
PvP should become much more exciting now, and I will get into PvP myself. With the Imperial Crackdown, there is lot to look forward in this publish.
I must also say, it is a relief to see the developers really listening to the community for once. Despite my growing frustrations with this game, there may be light in the tunnel after all.
Thank you Thunderheart
Thunderheart wrote:
BigSteve03 wrote:
I'm happy about the change, but I feel bad for the programmer who had to work (probably) most nights and all weekend long to get this change into this publish just because some people couldn't accept a simple mistake and wait a little longer for the change.
Thanks for saying so BigSteve
I'll pass along your kind words. They are much appreciated.
We are job security and overtime creators