Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


About Sethos-DN

  1. NO GP FOR FORT!!!!

    You guys should relax. I'm sure they have guys working around the clock in Korea to find a solution to this problem. In the meantime, you can always go to the fully functional BCM and grind your way up the rankings using instances. The NC NA guys can't afford a proper QA/tester team, so your continued support is very important in their time of need. I'm sure the whole staff is feeling terrible about this bug right now.
  2. NO GP FOR FORT!!!!

    What in the past few months of 6.x makes you or anyone else think there's still a QA for this game? There's no kind of patch management here, they just get something from Korea, toss it on live servers, have Cyan trot something out about fixes and discussions, then tell Korea about all the bugs you found for the next update. I'm pretty sure you and the rest of the playerbase are the only people testing and catching bugs in the NA version of the game.
  3. Ereshkigal Server Consolidation FAQ

    Remember what we said when EK launched? Whoever has the final say on server decisions isn't learning, but we just learned tossing an alt on the next doomed server could be profitable.
  4. Glory Points Reset & Seasons

    1. Is this a late April Fool's joke?
  5. Start Petition

    I think you're on to something: If this is for Aion, then it would explain all the recent patches and events. Think about it, NCWest requests changes from the Korean version and assumes we'd find them acceptable. The decision makers don't understand the customers, so they have to react to negative feedback instead of requesting favorable changes before the patches. They obviously need someone to explain the "game’s design, feature set and mechanics, art, economy, audience (and more)." We're going to need someone to take one for the team and fill this position fast.
  6. Something like this would be helpful @Cyan. Could we get someone like @Gideon to admit you guys also handled 6.2 poorly and reiterate the solutions with an ETA so we can move on (minus the people who will complain no matter what)? Korea has been sending patches to NA since 2009. One process repeated over and over, for events, patches, hotfixes for the better part of a decade. You might not know the timeline, but I find it hard to believe no one in your office has an ETA on the changes you mentioned. I can't imagine you guys asked NC devs for a patch without any idea of a timeline while your customers are raging and leaving. That doesn't sound reasonable to me. If there's a legitimate reason why "nobody knows", then I'm open to hearing it. You're asking devs to change enchantment rates and loot tables to the current build not reinvent the wheel. Korea is way past 6.5 development, so how much effort does it require combine two things that already exist? If you don't know the ETA, then someone in NCWest management should probably ask. Even if you really don't know the timeline would it be asking too much to get an idea of how long the process normally takes? I know that answer exists.
  7. Reason why enchanting rates is so bad +

    I'm going to be optimistic and plan for this to happen in April, with 6.5 dropping a week after so Cyan gets to keep his word. Whoever approved of the current event will probably have a say in this next patch. So, I'm expecting marginal improvements at best and a plot twist related to the accessibility of the stones. Shard prices will still get overlooked because the BCM guy either doesn't play Aion, doesn't get our feedback, doesn't care, or a combination of these things. If you expect nothing from somebody you are never disappointed, right? I'll just shake these shugolings out of the trees and be happy with my one stone a week events until the patch drops.
  8. Weekly Server Maintenance - December 12, 2018

    Do we need Korea to help fix shard prices on NA?
  9. Reason why enchanting rates is so bad +

    I got excited until I realized this means...
  10. Are mobs suppose to have insane dot damage?

    Were you wearing armor when this happened? If so, was your armor from this patch?
  11. The power of Ereshkigal

    Ereshkigal wanted all the new characters to grind for shards forever or pay a heavy price.
  12. Nc Will Kill Aion

    #1, #4, #5, and #10 touch on enchantment rates/stones and I wanted to add to it. Someone already said we have the same enchantment rates as Korea. Those rates will go up in 6.5 to match the changes from that patch.The problem is the rates were set with higher enchantment stone availability in mind. Korea makes up the difference by putting the stones in the cash shop. In 7.0, Korea added an NPC to upgrade enchantment stones at a 3 to 1 ratio but 7.0 is a long time for NA to wait. We need this now. I'm assuming NCWest has more control over their own cash shop than the content in the game to include enchantment rates. If they don't have the power or influence to change the rates, then they should address the availability of stones in the game. I'd suggest either including those stones on the shop like the NCSoft intended or creating events to increase their availability. I know Cyan said there would be less events, but I don't see another good way to handle this issue. They will either make adjustments for this playerbase or bleed off everyone but the whales. I know the game is carried by P2W players but you need to consider the cannon fodder too. They had an opportunity with the current event to put something better than one stone for 1350 gems. How about a pvp event where we spend two weeks grinding for something like: People enchanting pvp gear could just do extra pvp instances and ignore the current event because the rewards aren't worth the effort. I'd like to know how events like this get past the planning phase with terrible rewards. It's like the people who make the decisions don't play the game.
  13. Weekly Server Maintenance - November 28, 2018

    This is the single most important issue in Aion at the moment. I hope this is the #1 topic in your talks with the development team.