Disconnecting during a craft, could there be a solution implemented?

[Kimura410]

Was crafting a 3 star item earlier, when everything stopped and moments later, I got 90ked. Would it be possible for the dev team to make it so that if you get disconnected, when you log back in you are still in the process of crafting the item? Someone suggested that your items should just get saved if dced but then people would abuse that, so that wouldn't be a good fix. Any way for a fix to be implemented, or is it just a "craft at your own risk" situation.

And to answer potential questions, my ISP is pretty good. Its hard wired, and when I got 90ked, I still had an internet connection.

[Shioban]

They already answered this in a community/dev response, there's no way to do this without people abusing it where some would simply disconnect if a synth wasn't going as planned.

"Oh, it's going to blow up....*YANK*"

If you take even one step into the craft you can potentially loose it.

[Bladeglory]

I made a thread asking for this ages ago. It kept getting "Oh it'll be exploitable" or "Somebody will discover an economy-wrecking glitch!"

Bullshit. All we're asking for is a pause button that's automatically activated when your connection lapses. It's not real time combat or anything. Pausing ain't gonna hurt if SE programs it right.

"You were in the middle of Synthesizing [item]. Please Abandon or Continue the synthesis."

Abandoning would give you the same results we have now. Continuing would give you the same Durability, Progress, CP, and buffs that you had beforehand. Can anybody see any issues with that?

[Ninix]

I made a thread asking for this ages ago. It kept getting "Oh it'll be exploitable" or "Somebody will discover an economy-wrecking glitch!"

Bullshit. All we're asking for is a pause button that's automatically activated when your connection lapses. It's not real time combat or anything. Pausing ain't gonna hurt if SE programs it right.

When you disconnects your character is completely removed from the game world and the data is ejected from the server's RAM. To allow for a "pause" button that would persist through logging out they'd almost certainly need to make some fairly big changes to the way the crafting system works internally, with the largest difference being that information on in-progress crafts would have to be persisted to your character's "save file"/database record, making save files larger. Considering how averse they are to other changes that increase character save file size (server-side UI options/macro storage, increased inventory size, etc.) it's not surprising that they wouldn't want to do this either.

Is this an *impossible* issue to fix from a design perspective? No. But it may involve an inordinate amount of work to implement when compared to the benefits.

[Bladeglory]

Is this an *impossible* issue to fix from a design perspective? No. But it may involve an inordinate amount of work to implement when compared to the benefits.

That's the biggest (legitimate) reason I can find for not implementing it. And I'm okay with that! Sort of. It seems like if levequests were a big enough problem to add to character saves in 1.0, 2-star synths should be too. And they're always adding more and more data to keep track of permanently. At the very least, I'd like one of those in-depth explanations on why they're unlikely to implement it that the lead designer people seem to do.

[Shioban]

That's the biggest (legitimate) reason I can find for not implementing it. And I'm okay with that! Sort of. It seems like if levequests were a big enough problem to add to character saves in 1.0, 2-star synths should be too. And they're always adding more and more data to keep track of permanently. At the very least, I'd like one of those in-depth explanations on why they're unlikely to implement it that the lead designer people seem to do.

There already was a JP developer response as far as I recall.

And they felt it was too exploitable, and had no mind to change it (even with your consideration for a pause button as you put it).

They felt it best that the risk remain as-is until it becomes a major problem for the vast majority of players.


There was no in-depth exploitation because there was no need, their decision boiled down to simple choices.