Results 1 to 6 of 6
  1. #1
    Community Member
    Join Date
    Dec 2013
    Posts
    92

    Default Be able to feed named items with augments to sentient weapons

    If a named item with an augment is feed to a Sentient Weapon, maybe have a warning appear: "Named item contains a regular augment! Are you sure you want to consume the named item?"

    Could possibly get more sentient XP with augments fitted.

    I think named quest rewards from Storm Horns and Wheloon and possibly others (event named items Crystal Cove etc), should also be able to be feed to Sentient weapons.

  2. #2
    The Hatchery Enoach's Avatar
    Join Date
    Nov 2006
    Posts
    8,580

    Default

    I think a less prone to accident method would be to …

    1. Implement and item similar to the Filigree Removal tool you can purchase at vendors so players can simply destroy the augment
    2. Implement a recipe at the Stone of Change that will destroy all augments slotted in a Named Item - similar to what was done when they upgraded an item and you could remake an old version to a new one
    3. Add to the disjunction of Crafting the ability to put named items in with a disjunction that would only remove the augments.

    This makes the removal of augments require a very conscious decision, thus avoiding the accidental "I clicked the wrong thing".

  3. #3

    Default

    they did this so you can’t plug a ML 28 augment into a ML1 cheese named item, making it ML 28 for sentient xp purposes.

    I get the reserve in their decision but it was lazy. As above, they needed to add another option which was an augment destroyer. Many named items drop with augments & folks have old useless gear with augments they would munch.
    Wiki dashboard with some useful stealthplay links. LONG LIVE STEALTH!
    Proud Knight of the Silver Legion, Cannith: Saekee (main) and some others typically parked at some level to help guildies and other players


  4. #4
    Community Member
    Join Date
    Dec 2013
    Posts
    92

    Default

    Quote Originally Posted by Enoach View Post
    I think a less prone to accident method would be to …

    1. Implement and item similar to the Filigree Removal tool you can purchase at vendors so players can simply destroy the augment
    2. Implement a recipe at the Stone of Change that will destroy all augments slotted in a Named Item - similar to what was done when they upgraded an item and you could remake an old version to a new one
    3. Add to the disjunction of Crafting the ability to put named items in with a disjunction that would only remove the augments.

    This makes the removal of augments require a very conscious decision, thus avoiding the accidental "I clicked the wrong thing".
    I don't think that much effort is required. As currently there isn't anything stopping someone from accidentally feeding their favorite non-augmented named items.

    I think id prefer a message box saying: "You will earn 200 sentient experience. Do you want to consume your Purple Dragon Shield ?". As an example. This option could be disabled in the options menu.

    Some of the things id like to feed would be epic items found in 3BC, which some come with augments, so aren't really modified.

    If an augment destroy item could be bought for platinum, that wouldn't be a bad alternative.

  5. #5
    Community Member Vish's Avatar
    Join Date
    Dec 2006
    Posts
    2,593

    Default

    This has something to do with hard coded
    Don't worry it, they're rare
    Just junk them and move on
    Run wpm for 1k gems
    Kil Glory
    30 alchemist
    HOW
    Sarlona

  6. #6
    Community Member RevCo's Avatar
    Join Date
    Jul 2013
    Posts
    30

    Default

    Ok I heard a rumor as to exactly why you can't feed named items with augments to a sentient weapon...

    THEY CAUSE KIDNEY STONES! hehe

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

This form's session has expired. You need to reload the page.

Reload