Please Implement Auto-Reclaim on Disconnect (90% success, 10% failure)

[Katlyna]

Please Implement Auto-Reclaim on crafting Disconnection (90% success, 10% failure). That pretty much is the start and end of my proposal. This would be trivial to implement and not abusable (since it would be the same as reclaiming early for no reason).

While this is NOT a perfect solution for crafting disconnection... it would save 90% of the headache when it occurs. It would be a relatively good quality of life improvement for crafters, while being extremely trivial to implement (and not require any bandwidth on the server... just a simple client patch).

Also you would need to require reclaim is equipped... or make reclaim baseline. IMO reclaim should be baseline to all classes anyway. You could also require the user has at least 55 CP to cast reclaim.

Please do this for us SE Devs... we could really use a cookie right now!

[Nezerius]

This would be trivial to implement and not abusable (since it would be the same as reclaiming early for no reason).

Except it would be abusable, as a crafter could just completely ignore Reclaim as a cross-class ability, and then force a disconnect whenever a craft goes bad.

[Katlyna]

Right you would need to require reclaim is equipped... or make it baseline. IMO it should be baseline to all classes anyway.

[Dererk]

They already stated they can't do this because of yes abuse.

It would happen people would force a dc its also too tempting because with expensive mats even if the person says they would never abuse it. They would. Its too easy a tool to abuse.

[Katlyna]

What are you talking about ... how is forcing a disconnection triggering a 90% success 10% failure abusable?! That's the exact same as casting reclaim and risking loosing your synth at 10%. Its like you're saying reclaim is abusable O_o

[Roth_Trailfinder]

Except an automatic Reclaim would occur if you did not have the skill slotted, and would occur whether you had the CP for it or not.

Run out of CP on a craft that goes sour? Disconnect to force a Reclaim would be abusing it.

[Katlyna]

That's why I claused above only if you have reclaim slotted and 55CP (that's how I would implement it if I were to implement it). But most smart crafters will know if they are going to hit 90% or not before the GS/Byregot's. I suppose if the CP requirement didn't exist.

You all must use reclaim more than me. I haven't reclaimed in three months... I think the risk of reclaiming is terrible... and you guys are making it sound like reclaim is some kind of hack LOL.

[Sibyll]

Except an automatic Reclaim would occur if you did not have the skill slotted, and would occur whether you had the CP for it or not.

Run out of CP on a craft that goes sour? Disconnect to force a Reclaim would be abusing it.

I just don't see why they can't save your buffs and progress. I've played MMOs where any buffs/effects you have on when you log out are remembered for when you log back in, so I know it's possible. I don't understand why such a basic QoL feature like this is outside of the bounds with the technology that exists.

[Katlyna]

I just don't see why they can't save your buffs and progress. I've played MMOs where any buffs/effects you have on when you log out are remembered for when you log back in, so I know it's possible. I don't understand why such a basic QoL feature like this is outside of the bounds with the technology that exists.

Technically speaking one of the biggest goals and points from the 1.0 to 2.0 transition was building better faster clients and servers which were lighter with better capacity. Technically speaking such a feature does require some bandwidth/state. The bigger problem is its a fairly significant investment of development time, debug, testing and polish. Which is why I don't think we'll see such an "advanced" feature ;-/

[Roth_Trailfinder]

Technically speaking one of the biggest goals and points from the 1.0 to 2.0 transition was building better faster clients and servers which were lighter with better capacity. Technically speaking such a feature does require some bandwidth/state. The bigger problem is its a fairly significant investment of development time, debug, testing and polish. Which is why I don't think we'll see such an "advanced" feature ;-/

Which is why such constant character save state should only be done during crafting.

You're slowed down during crafting anyway. They SHOULD make it so that the entire synth state is saved when you are crafting, at the end of each step. Don't like how things are going and try to DC? You come back to a still unsavory synth. In the middle of a craft and your Internet goes out? You come back to being at the same spot you disconnected at.

THAT is inherently not abusable. Having that happen only during actual recipe crafting (IE - not during Quick Synthesis or any other time) would not be an undue imposition upon speed for anyone.