Results 1 to 4 of 4
  1. #1
    Player
    Frank_Penote's Avatar
    Join Date
    Nov 2012
    Location
    Limsa
    Posts
    5
    Character
    Frank Penote
    World
    Sargatanas
    Main Class
    Pugilist Lv 50

    The problem with desynthesis

    I think there needs to be a major overhaul to the desynthesis system in regards to how one skills up and how the points are reduced from other skills (btw that whole concept is really quite silly). So today I wanted to change EITHER my arm or my bsm desynth skills because they weren't really panning out like I had hoped. I hit a giant brick wall when leveling bsm and I don't feel like farming primals all day to try to desynth weapons. That's just not an effective or attractive use of time while I play. So I decided I was going to do culinary desynth skill instead so that I can cash in on this swimsuit market while it is still viable. Anyways, so I'm pushing culinary's skill with fish I'm buying off of the markets and I'm seeing some small decreases on other skills here and there as normal.

    Now I get to my 300 point mark because I already had bsm and arm to 70 and gsm to 100, and I start to see massive decreases in my skills because I'm getting big skill ups for culinary. Now my problem is this: I have now deleveled about 3+ full levels from my 100 gsm desynth skill, and now since RNG decided to decrease my goldsmith so much as opposed to THE OTHER TWO that I didn't really care for, I'm now out a ton of gil having to now relevel gsm. And as I try to relevel goldsmith off of i90 items (with only a 63% desynth rate at 96.96 goldsmith desynth skill) I find myself losing a ton of gil and I'm fairly unhappy with this. Not to mention the gains that I get from redoing gsm, are now going to be large decreases in another desynth skill, which could effectively make me "run in circles" for lack of a better term, if RNG decides to lower my culinary desynth skill... Anybody else see the issue here?

    The ONLY aspect of the game that limits what you can level is desynth and changing one's mind has massive consequences!. I'm not particularly happy that I'm about to be out a LOT of gil, simply for changing my mind with a system that is pretty heavily flawed in the first place. Even when I wasn't at 300/300 points I was seeing losses to skills that weren't capped. Why? The system needs somewhat of an overhaul and I hope it happens very soon. I don't particularly like dropping massive gil when I already had that skill leveled up. We need some kind of menu option that lets a player set priority for what they want to have decreased in skill as other things skill up, otherwise you can just essentially hemorrhage gil for no reason other than a design flaw (as skill A increases, skill B decreases and then to get skill B back up skill A decreases as you do that, simply due to RNG).
    (2)
    Last edited by Frank_Penote; 08-17-2014 at 08:10 AM.

  2. 08-17-2014 07:42 AM

  3. 08-17-2014 07:43 AM

  4. #2
    Player
    Eye_Gore's Avatar
    Join Date
    Jun 2014
    Posts
    1,628
    Character
    Yolanda Freebush
    World
    Malboro
    Main Class
    Gladiator Lv 80
    Just an FYI, type out your whole post in one shot, then copy the section to wind it down below 1000, post, then click edit post, paste the rest back in. Its a way around the 1000 limit.
    (1)

  5. #3
    Player
    Raldo's Avatar
    Join Date
    Jul 2011
    Posts
    2,563
    Character
    Raldo Volca
    World
    Coeurl
    Main Class
    Marauder Lv 80
    I believe there was a dev response regarding the ability to choose which of your skills delevels in the future (no date specified -- also, I'm not going to find the quote for you), but in the mean time, this is your best option:

    http://forum.square-enix.com/ffxiv/t...ill-To-Delevel
    (1)

  6. #4
    Player
    Frank_Penote's Avatar
    Join Date
    Nov 2012
    Location
    Limsa
    Posts
    5
    Character
    Frank Penote
    World
    Sargatanas
    Main Class
    Pugilist Lv 50
    What a find! Surely appreciated (though as we all know this kind of work around really shouldn't be needed)!
    (0)