These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE General Discussion

 
  • Topic is locked indefinitely.
 

6 week dev cycles

Author
Flay Nardieu
#61 - 2014-09-03 03:53:44 UTC
DaReaper wrote:
Flay Nardieu wrote:


... redacted to save space ...

Quote:

Crius: Overhaul of industry with a bulky less than intuitive UI and a complete lack of common sense with decentralization of BP placement on POS side removing remote from office they at least should have had the foresight to make BPs usable from an online corp hangar at the POS but we did get compression arrays and a somewhat more intuitive reprocessing of modules.



So you are whining because your bp's are no longer 100% safe from attack? Where as one fo the biggest reasons you needed a pos anyway (slot limits) has been removed so you can go to any station and setup shop with no problems. Yea, i'm an industrialist carebear and even I thought the idea of remote copy and manufacture was stupid and needed to die in a fire years ago.

[quote]
In the first example it improved the acquisition of sites which determining what something was of interest quicker but made looting data and relic sites annoying as hell.

The second example makes S&I more of a chore especially at a POS this is a much greater nuisance value in the expansion for those who would do S&I at a POS in addition to ore compression.

I have stated in many posts related to Crius how dumb that approach is even though I am irked with basically the bulk of the changes with Crius and definitely would prefer changed for personal preference I know I won't get them but damn how hard is it for CCP to admit that they dropped the ball with decentralizing where we store BPs and the UI is a lot less then advertised. Correcting obvious flaws should be high on the priority in a rapid release system. Radical changes should really be fully ran through their paces on SISI before every even being considered to be deployed on Tranquility. I know one thing I tested on Sisi had only 2 weeks prior to release to test then went live with the update and it wasn't resolved.

Can anyone honestly say they like moving BP around in a POS?


They decentralized nothing. They made it harder for you to have safe bp's. I so can't wait for the reactions when they announce all stations in null can be destroyed and you will lose your crap in it. The tears will be epic... and what the hell have you forum people done to me?!?1


Point if fact running remote from an office did offer centralization of blue prints, even if people buy into the BS line of removing it to give a "Risk vs Reward" mantra the same risk would exist if you had your BPs in a Corporate Office Array (Hell why not add the Personal Hangar Array as well) but no; actual improvements didn't happen. I have not seen one intelligent post how the POS is offering more rewards and the risks are frankly negligible. All Cirus really did was make a push for a nomadic industrial culture IF a player wants to move around to shave costs to improve their margin.

Diverting from the more direct response to quoted post. I chose Oddessy and Crius specifically because they where the old and new release cycle in addition to having very specific and clear examples.

I've lost count of how many 'blah blah tears blah' and 'oh stop whining' posts in response to constructive critique of releases and ****** behavior by myself and others. The over inflated egos in Eve must be unparalleled in gaming history, tears really? butthurt? (love that lame nugget) Lol, only 3 people ever offered me a legitimate debate in the forums.

After the 4th this account goes idle, but until then I refuse to consent by remaining silent. I offer legitimate debate and critique for a game I honestly do like but refuse to support while they put out assinine expansions.
Moloney
University of Caille
Gallente Federation
#62 - 2014-09-03 15:54:44 UTC
Please note that the industry changes in crius are not the point of this thread.

They were done fairly well imo.

However, the majority of that work and associated communication took place in the 6 month dev cycle for KRONOS