Jump to content

Flutieflakes

Members
  • Posts

    7
  • Joined

Reputation

10 Good

3 Followers

Personal Information

  • Location
    Upstate New York
  1. Have you tried keybinding? They have a way to set "target nearest enemy" and other ones to the tab key. That doesn't always focus on the enemy that's center on your screen, but I found it helps a lot to use the "target nearest enemy" binding.
  2. I think most people don't understand the process of geting just ONE bug fixed, how involved that can be. 1. They have to decide which of the most complained/reported bugs need to be worked on. This requires multiple meetings and delegating of the work load. 2. Let's take it to just one programmer/developer now. They have to go back into the game's logs to find reported incidents to see what might be triggering the problems. 3. Then they have to start "running" lines of code (as my husband says). This involves reviewing code, sometimes line by line, to find where the error might have occurred when the original coding was done. 4. Once they find the said error/s they correct it. 5. Then it's sent off to a tester (QA) so that the tester can apply the "fix" to the game and see if it works and/or causes any conflicts or other breaks to the game. This happens a LOT where one fix can break a dozen or more other things. 6. IF that happens and somethign else is broken or the fix doesn't work, it gets sent back to the dev/programmer for them to go over the code again and try and figure out what happened. This can take, literally, weeks and sometimes months. 7. Then, once they think they have it fixed (again) it's sent back to the tester. 8. Tester retests and looks for new problems. If none appear, it goes to Public Server to be deployed before being released to live servers. IF more problems come up that weren't found in testing, the whole process can start over. During all this procedure, there is ongoing meetings and status updates, etc. This is NOT a process that takes only a day or two (reference Trion). This can take weeks or months sometimes, depending on the problem and it's severity. This is how it works for ALL software, not just games. Your reports of Trion World's dealing with Rift say to me that they were majorly on the ball with their beta testing and were working on major patches from beta that were put out early. Bioware, perhaps, should've been more so than they have, but they ARE trying. What seems like a simple fix to us can be something major in the programming, even though we don't see it. I understand the frustation as I've had more than one problem pop up, but they weren't game breaking, just very irritating. But from learning how this whole process works from being married to a senior developer and a company, I'd say if you're willing, patience would be a good thing to have. Oh, and if you really want a peek at what's coming down the pike early or want to help the game get better, spend some time on the Public Test Server. It helps the game, not just the company, a lot.
  3. WAY off point here. That's the problem with skimming something over reading the full content. He was using WOW as an example and the whole context of the post was a pithy, sarcastic note to the elitests and rush to 50 crowd that are currently complaining and/or quitting. Before posting on a subject maybe next time you should make sure you know what the guts of the post are instead of assuming so much.
  4. You keep saying you read this fan rating of 6.1/10 but I'd like a link please to where you read this. If I can't read it for myself, I won't believe it. This is especially true due to the overwhelmingly positive reviews I've seen for the game on many different sites.
×
×
  • Create New...