The game will be ready for release late 2014 or early 2015. Most MMO's release in this state. If your trion you are fast fix things quick have an open book, acknowledge your games shortcoming s immediately and keep a break neck content pace while holding monthly Live events Albiet shallow but still new dynamic content.Thunderchief wrote: »The players have known what the problems are for 2 months now. Finally you have acknowledged that you agree and that something will need to be done.
The devs have outlined some very minor changes to stamina builds that maybe perhaps possibly might be implemented in some distant indefinite patch at some time. Sounds very wishy-washy.
These minor changes are what you should have hot-fixed immediately weeks ago. These should have been something temporary to keep us happy while you researched the core problem and came up with a more permanent solution. Slight damage increases to underused skills and slight stamina reduction passives on medium armor (but nothing for heavy).
Did it really take 2 months to come up with this? Will it take another 2 months or more to implement it? When your boss heard about these changes did he pat you on the back and say "good job, it's obvious you've been working hard on this?" If I came back to my boss after 2 months and showed him 5 lines of text I'd get the sack.
Are the devs leaning back in their chairs pondering solutions all day. Do they really need to spend weeks and weeks play testing on PTS? This time right now is the most crucial time sensitive period in regards to the longevity of your game. If something isn't done soon this game that you have worked hard to create will just become a bad memory in the gaming community. Most times when people unsub from a game they don't go back. The best chance to retain players is while they still feel invested in their characters.
Do you need to test it? Get a couple of devs and a few of your friends from tamriel foundry and get on PTS and test it out over the course of an hour or two then go back and tweak any necessary changes. Then put it in the game! What are you really waiting for? A sign from heaven? Just do it already. I would rather have seen you implement these changes and make minor tweaks to the game every week or so rather than this seeming inactivity and apathy.
Your devs work at least 8 hours a day right? What do they do? Are they working on new content? If they are please tell them to stop and fix the core issues first.
Back to my original question. Why does it take so long. Do you need to find the specific line of code that you need to change? You can't seriously still be considering what exactly it is you need to change. Are you dithering and procrastinating while you bleed subs?
Every day on the forums there are dozens of new posts complaining about the same specific problems and every time a variety of suggestions are thrown up that are exactly the same as the suggestions the day before. Your options for solutions are limited. Rule out the options you don't like and find a good compromise between the options you do like.
I am quite sure that if you brought the servers down right now but said "we are doing this to reduce VR mob hit points and damage by 10%" there will be smiles all around and few VR players would complain. We would at least know that you are doing something and that it won't take months for change to happen.
Here's another idea you bring down the servers and when they come up again staff skills require stamina instead of magicka. Some people will complain, but it would solve many problems. The only reason they use magicka right now is a roleplay reason. "Hey, staves are magic so they must use magicka right?" No, it completely breaks all balance. Class skills should be magicka and weapon skills should be stamina. In this way all classes will have greater balance. You don't really need to reduce the cost of the skills to counter for utility use of stamina either. Staves are ranged weapons and staff users should not be on the frontlines dodgerolling/blocking/interrupting anyway.This is something that really should have been changed long ago before everyone jumped on to this build. Now when/if you change it everyone will be unhappy and ask for points refunds from staff and light armor trees.
I could be wrong about my suggestions above, but I don't go to work at your company and spend all day thinking about it. You do.
What would happen if you sent out an email today to all unsubbed players stating that you have made VR easier but still challenging, that you have improved stamina/magicka balance and that there is now a greater demand for healers and traditional tanks?
I bet you would see a serious increase to your sub base. $$$$ That's what.
I had high hopes for this game. My sub has been renewed today for 1 more month and I and many others will be watching for changes. Money is coming out of my pocket and going in to yours in return for a service. Please remember this.
The clock is ticking.
Thunderchief wrote: »I'd rather they did something now that makes people "snarky" but interested in the game rather than some airy-fairy contemplations to a problem that has already existed for months. When they behave with such a lack of urgency it makes people feel like things might not ever be fixed, they lose hope and unsub.
If they gave stamina users 14% regen on medium armor today it would put a smile on their faces and they might put down their staff and light armor to play with bows and swords but eventually they will go back to the magicka builds. This is because what they are proposing should be a temporary stop-gap measure rather than the solution we are looking for to fix class balance.
Wifeaggro13 wrote: »I've been hard on ZOS for the games shortcomings but they truly did create a beautiful game with a lot of potential.
What would be the point of spending a week making a temp fix, in stead of actually working on the real fix, to then throw it in the bin a week down the line when you have the real fix ready.
kirnmalidus wrote: »Yes things need work. Yes I wish my Nightblade was more competitive. But I'm willing to be patient.
Do we already forget Cragfail?
Please give them time to do proper diagnoses, QA, regression testing, etc.
Wifeaggro13 wrote: »The game will be ready for release late 2014 or early 2015. Most MMO's release in this state. If your trion you are fast fix things quick have an open book, acknowledge your games shortcoming s immediately and keep a break neck content pace while holding monthly Live events Albiet shallow but still new dynamic content.
If your ESO you have a beautiful engine one server and a very unfriendly toolset that wont allow live fixes or changes. a very very poorly tested end game and a video game press that lead you to the Guilottine way before launch.
I've been hard on ZOS for the games shortcomings but they truly did create a beautiful game with a lot of potential.
Unfortunately i dont think much of the player base has patience for the imbalance issue or phasing problems. Combine that with the poor itemization in the duck taped end game retention at the 90 day mark will be very poor. Worse then AOC that lost 40% in the first 60. a Rift scenario would have been desirable with a 70 percent Retention at 90 and hovered at it for about a year.
Zos reminds me of my 10 yr old nephew at times. He has some fears of failing so he works very hard to come up with these elaborate master plans that he is sure will keep him from failing. He'll contemplate and work on them for days/weeks at time until he's sure they are fail proof.
Then he goes to implement them and they crash and burn. He gets so disappointed because he worked so hard on them. The problem is he just doesn't have the experience or knowledge to pull off such elaborate master plans. He can be pretty stubborn and won't listen to anybody. So you can see his failure coming but there's nothing you can do about it.
It appears to me that they just comment out their bugged code and use layers of code versus modules which can create conflict of course that lie dormant until a specific process is flagged/triggered. Of course this is speculation on my part. The initial code appears to be bugged and loaded with errors which obviously is not an easy fix, especially if you are not using modules. But I confess to knowing very little in what processes it takes to code a video game.
stefan.gustavsonb16_ESO wrote: »
... each using their own favorite coding style and never writing any comments or documentation...
That's called job security XD Make yourself difficult to replace cuz no one else can read or manage your work.
Honestly, I only read the first paragraph since it seemed to be a rant. I then proceeded to skim over your post but never could locate the specific issue(s) you are referring to.