For those not familiar with software developmentDepending on how many resources were working on epics… 1 week delay can easily blow out to a few months.A. As previously said the 1 week delay was on everything. So if 25% of the staff were working on epics, then dropping that content would still leave a shortfall of 50% to catch up on… which would mean the ‘epic staff’ would require 3 weeks to catch the rest of the development up.B. Let’s assume that SOE actually have work planed after the release and are not all going on holidays. (Skeletal revamp, Guild housing etc) So the resources are probably already allocated to other stuff.C. After any release you have to hold developers and QA staff back for warranty purposes. To fix all those problems that you find (that were missed).D. Implementing something as large as epics into the game probably requires QA to run substantial regression cycle which in itself could be weeks. (Instead of testing it with everything else during ROK regression)So a smart project manager would probably delay the Epics and roll it out with something else so as to piggy back it onto another testing regression cycle (perhaps for the skeletal revamp?). Thus saving time and money for more cool content for us.Just ask yourself… if you were the Test manager and were asked to make sure 24 quest lines (maybe 500 quests), 500 quest reward and 48 weapons (fabled and legendary) all worked as designed. And to make sure that none of the present content was affected (mobs used for updates, quest givers, clickable, collectables, carftables, specific zone instances, drops etc) that the quest lines touched.Easy to do if you were testing everything for ROK to start with plus Beta looking at them. Not so easy to do on its own and without Beta.
|