Hi GMs, Current Issue: Insufficient Quickslots and Quickslot bars With so many skills and pots, all quickslots are fully used up, and players experience repetitive downtime re-organising skills/pots for different scenarios. This is especially so for healers who have many buffs, formation skills and traps, leech party skills, on top of the usual combat skills. There are just not enough quickslots spaces to house all support and combat skills for effective and efficient gameplay. Suggested Improvements: Increase the number of quickslot bars players can cycle through (currently only 3 quickslot bars) Increase the number of quickslot rows each quickslot bar can expand upwards (currently only 2 rows per quickslot bar) Reduce the size icons so it doesn't take up so much of the screen Allow players to toggle and fix the placement of their quickslot bars, and have the clientside remember the position of the placement (if they prefer having the skills horizontal at the bottom, or vertical on the side) Alternative Suggested Improvement: Allow players to create and save customisable skill chains that allow them to make a buff or skill combo, then place the saved custom skill icons into quickslots (this will reduce the number of quickslot/quickslot bars required)
Alternative Suggested Improvement: Allow us to create and save customisable skill chains so we can make a buff or skill combo, then place the saved custom skill icons into our quickslots (this will reduce the number of quickslot/quickslot bars required) (Edit: This suggestion has now been added to the original post for consolidation)
Most of the skills and buffs are not needed in game and are worthless. I've been playing this game since 2007 and found that many are a waste to even lvl or use in pve or PvP. I just came back to game the last week and still setting up my bars but 1 buff bar for training and.my main bar for pve and PvP all in 1.
Interesting suggestions! Unfortunately, as we've mentioned before, we're unable to make any changes to the system that aren't already in Korea's service.
Thanks CM NineArts, Completely understand your point. When I made the suggestion, I was hoping you could escalate it to the Korean side / developer team when you have meeting with them, so they can consider adding it to Korean service first then, and perhaps in time to come, we can get it too. That's how improvements are made after all right? Instead of waiting reactively for Korean/Developer to have the ideas, and then we just see what they have and go 'hey we want that feature too!". Is it possible to suggest to them at least, and let them decide if these are features worth adding to their pipeline? Thanks!