AionSource's Interview with Lani Blazier about 1st Part of 1.5.1 Patch Notes
-
Date: 11-11-2009 Views:
KeyWords: Aion, AionSource.com, interview, Lani Blazier, NCsoft, 1.5.1 patch notes
- Summary: AionSource.com recently took a interview with Lani Blazier (aka Liv) about the first part of the 1.5.1 patch notes of Aion, talking about measures for goldselling, bugs in recent versions and some other problems that players are very concerned about.
-
|
This Article is Originally from AionSource.comIf You Want to Know More Details about it, please check out the link below:http://www.aionsource.com/forum/news-announcements/ 86334-aionsource-interviews-lani-liv-blazier-about- upcoming-1-5-1-patch.html |
AionSource.com recently took a interview with Lani Blazier (aka Liv) about the first part of the 1.5.1 patch notes of Aion, talking about measures for goldselling, bugs in recent versions and some other problems that players are very concerned about.
1) We've been told that 24/7 customer support is on the way and the new filter has really cut down spam in chat channels, but we are still seeing goldsellers sitting for days and days in personal shops in major cities (where they cannot be autoreported) with nothing being done to them. Can you elaborate if/when we will see in-game GMs on all servers taking care of these advertisements and, hopefully, bots as well?
- Our CS team is always hard at work providing a lot of support to different areas of the game. Because of their increased efforts, many players have already seen the results you're talking about from RMT spamming in chat. We are also fighting other forms of exploitation (hacks, bots, etc) and while they aren't visible, GMs are actively fighting against bots, and gold sellers.
2) The community has been working to help NCsoft find a fix for the memory leaks and crashing during fortress raids. Have there been any advancements with this issue? Is there a fix on the way in the near future?
- We have been actively communicating with the development team on fixes for this memory leak and are especially grateful to the community for the data they've been able to submit. The dev team is working on solutions and we hope to have something to announce soon.

















