Quote Originally Posted by KisaiTenshi View Post
Logging the last known state requires logging the state of all 30-something buffs, and their time/steps remaining. It wouldn't verify that the player actually crafted the item correctly and isn't actively abusing an exploit. You want what any good database does and "replay" the log file to the state it was in so that any consumables and gear changes don't cheese the end result.

Anyway, the point agreed on is that the game should have a way to resume crafting, and if the easiest way to accomplish that is to "use the workbench in an instance" then that isn't an unreasonable request.
When I say last known state I mean a snapshot of your character before you disconnected while crafting. Something you can't influence as a player. Logging back in would give you the prompt to either continue and be forced into that snapshot at your current location (because housing areas) or take a standard failure like if you had stopped crafting before allowing you to do anything else. We all know SE isn't averse to locking up the interface.

Either way it wouldn't matter if you replayed the entire thing or just the last known state if there was that big of a flaw in how their system works. It would end up at the same outcome because the server is the one in charge. If someone can influence that we have much bigger problems. You still need a snapshot of some point because you can't trust the client if someone somehow managed to change their gear or take a consumable through non-standard means.