Crafting and DC, will we ever be able to resume crafts after a 90k?

Hey there, lately we've seen a lot of changes to the crafting system, and with patch 3.05 we got 60/2 star recipes that actually require a lot of work and effort to get done.

Due to this fact I'd like to ask the devs if there's any plan to implement a resume feature to avoid mats loss after a DC mid-craft. I'm not asking for a guaranteed reclaim - that would be pure madness since people would abuse it everytime they get bad quality etc - but at least the possibility to resume the craft after we log back in from the state it was before the 90k.

I mean, if I get DC'd while crafting a common item i don't mind, really, cause I know I can quickly get mats again from MB or at least farm them somehow (gathering, precrafting etc.). But if it happened during a 60/2 craft star I would get a bit mad, due to the fact that these crafts require some limited mats obtainable from weekly capped tokens after a lot of effort (farming crafts/nodes to cap scrips and then do favors for up to 11.25 hrs/week).

Will we ever see something like this in the future?

Personally, I'd like to see it adjusted thusly :

After every move, your character state gets saved. This would include the exact state of your crafting. Step you are on, Condition, Progress, Quality, buffs, how much CP you have, everything - though I don't think that this can apply to FOOD buffs, because those continue to count down even when you are offline.

Get disconnected? You're right there where you were right before the disconnect - including any and all progress made on your current craft. Failing the craft? A forced disconnect won't save you, you'll come back to a failing craft. Succeeding at the craft? Your ISP or other problem over which you have no control can't rip your mats away from you.

This needs to get addressed.
Everyone talks about the possiblity of getting 90k'd during a craft and I have had it happened to me on Friday. A lot of people within Idyllshire got 90k'd and so did I while I was in the middle of crafting the Boltmasters Dreadnaught.

Needless to say I lost a vast amount of materials, over 30 hours wasted gathering and crafting for the server to hiccup on one moment and to waste all that effort.

If the developers want to keep this system time gated AND require a lot of effort to cap off and to actually utilize the system, safeguards must be put in place to prevent stuff like this.

Edit: It is very disappointing because I would've accepted if I failed the synth normally or failed on a reclaim. This is just a kick to ones nether region since you have absolutely no control when this can happen, IF it does.

Quote:

---

Originally Posted by Irving

Needless to say I lost a vast amount of materials, over 30 hours wasted gathering and crafting for the server to hiccup on one moment and to waste all that effort.

---

Sigh, I feel bad for your loss :\

Also, I'd like to add that today and yesterday 2 servers (Phoenix - and I'm glad I was sleeping when it happened - and Tonberry) crashed for a "Server Program Issue", so this should really get addressed since we all know that a DC doesn't only happen because of our connection/ISP.

They need to do something... especially since most of the DCs are on their side.

Bumping, I hope this might help to get feedback from the dev team.

Swarm them with tickets. When their CS become overwhelmed, they'll have to do something about it. Especially you, Irving - you lived through the exact reason why I haven't touched red scrip crafting yet. Definitely put in a ticket and I sincerely hope you get your mats back because that's just plain unfair.

That is a terrible but good idea... so very tempting.

Quote:

---

Originally Posted by Irving

This needs to get addressed.
Needless to say I lost a vast amount of materials, over 30 hours wasted gathering and crafting for the server to hiccup on one moment and to waste all that effort.

---

For me, that's another issue entirely. SE can hurr durr durr all they want about casual. Dropping 30 hrs of grind inside a disconnect window (a few minutes at most) says this game will never be for casual people. More on topic, Try crafting in your Free company house if you have one. Isolate yourself from area disconnect as much as possible. Though in your case it would be a cold day in hell before I ever tried no matter what conditions.

Would be a nice if its implemented but i dont see it become factible mostly because there is no way possible to know if it was a real disconnection and not a "faked" disconection (where you force disconnection in order to exploit the system when see the result not going to be good/perfect).
So the only way i could see it be possible would be using some kind of special 'ticket' that on use recovers(or prevents) 100% from a next failed craft, something like reclaim but instead cp to be obtain exclusively from mog station wich will reduced a lot the way of it usage into a emergency/very special items only.

Quote:

---

Originally Posted by Zorlinta

Would be a nice if its implemented but i dont see it become factible mostly because there is no way possible to know if it was a real disconnection and not a "faked" disconection (where you force disconnection in order to exploit the system when see the result not going to be good/perfect).

---

Make it save everything exactly as it was when you go linkdead. You disconnect while doing a craft, you come back in doing that craft - exactly as though you never left (except any food buffs or other timed buffs may have expired; non-timed buffs like Inner Quiet and Steady Hand 2 would retain their charges).

If you force a disconnect when you "see the result is not going to be good/perfect" you should come back to seeing that "the result is not going to be good/perfect".

Saving the status right after every step eliminates any worry about forced disconnects. It would also eliminate any worry about unwanted disconnects.

Quote:

---

Originally Posted by Roth_Trailfinder

Make it save everything exactly as it was when you go linkdead.

---

Would be so lovely that it happens. But as easier to do sounds more nightmarish becomes to implement and with the developers so likely to give persistent space like 3rd free retainer, more inventory, housing instances and so... have hopes that they "store" more data for crafting well... ill keep dreaming too :)

bump ;_;

I think the only method that would work is the "save state" after each action. That sounds like it would be tough on servers to handle that though. Anything other than a solution such as that which equates to "pick up right where you left off" it would be abused.

If they could consolidate the information from crafting into bits of data that could easily be saved there would be a way as long as the data wasn't easy to compromise. However this is a thought to keep in mind, is the server does save every 15 secs then it should be plausible to make a "save" system for crafting, even if it was just for higher end gear aka ones that use precious materials.

Er, rather than bit=1, try Kilobyte=1024 bits

Thought in my head is this. Each bit of Kilobyte could represent a a specific part of the synth. so with 1024 you could have a grid, 102x102

So it could have something like
0 1 2 3 4 5 6 7 8 9=would represent a value for the vertical number
1=the single digit value of the step
2=The Double digit value of the step
3=Single digit quality of synth
4=Double digit quality of synth
5=Triple digit quality of synth
6=Thousandth digit quality of synth
7=Single digit CP value
8=Double CP
9=Triple CP
10=Single Progress value
11=Double progress value
12=Triple progress value
13=Thousandth progress value

Basically with example it be something like. 1/4, 2/0, 3/5, 4/6, 5/3, 6/2, 7/4, 8/9, 9/2, 10/3, 11/3, 12/5, 13/2

Which would be:
Step=4
Quality=2365
CP=294
Progress=2533

So in this scenario each bit in the kilobyte is read as a unique piece of data by the server so rather than have to carry a heavy load on the server to read the data it could take in the kilobyte designated for crafting easily digest it, and throw it back and forth to keep it "saved", While it's definitely not an easy feat, I Know they did something similar when it came to storing gear in FFXI, the storage slips were bits of data and they basically just turned on/off the bit that the gear was designated to, so basically when you were say storing AF armor, body, head, legs, feet etc, it would look at the slip and see if that slot was on or off, if it was on it meant that the armor was already there, if it was off it meant the armor had not be placed there yet and it would take the armor, turn that bit on and then remove that armor from your inventory while storing it into that bit.

Though if I'm wrong I completely apologize, I just recall a similar method used to consolidate data while not easy could be plausible if resources were put into it.

I'm sure they could do it if they wanted to. You've got an interesting idea, that I hope they take note of. That said, one byte is 8 bits. A kilobyte is 1024 bytes, or 8192 bits. That leaves a bit more room, don't you think?

Quote:

---

Originally Posted by Airget

If they could consolidate the information from crafting into bits of data that could easily be saved there would be a way as long as the data wasn't easy to compromise. However this is a thought to keep in mind, is the server does save every 15 secs then it should be plausible to make a "save" system for crafting, even if it was just for higher end gear aka ones that use precious materials.

Er, rather than bit=1, try Kilobyte=1024 bits

Thought in my head is this. Each bit of Kilobyte could represent a a specific part of the synth. so with 1024 you could have a grid, 102x102

So it could have something like
0 1 2 3 4 5 6 7 8 9=would represent a value for the vertical number
1=the single digit value of the step
2=The Double digit value of the step
3=Single digit quality of synth
4=Double digit quality of synth
5=Triple digit quality of synth
6=Thousandth digit quality of synth
7=Single digit CP value
8=Double CP
9=Triple CP
10=Single Progress value
11=Double progress value
12=Triple progress value
13=Thousandth progress value

Basically with example it be something like. 1/4, 2/0, 3/5, 4/6, 5/3, 6/2, 7/4, 8/9, 9/2, 10/3, 11/3, 12/5, 13/2

Which would be:
Step=4
Quality=2365
CP=294
Progress=2533

So in this scenario each bit in the kilobyte is read as a unique piece of data by the server so rather than have to carry a heavy load on the server to read the data it could take in the kilobyte designated for crafting easily digest it, and throw it back and forth to keep it "saved", While it's definitely not an easy feat, I Know they did something similar when it came to storing gear in FFXI, the storage slips were bits of data and they basically just turned on/off the bit that the gear was designated to, so basically when you were say storing AF armor, body, head, legs, feet etc, it would look at the slip and see if that slot was on or off, if it was on it meant that the armor was already there, if it was off it meant the armor had not be placed there yet and it would take the armor, turn that bit on and then remove that armor from your inventory while storing it into that bit.

Though if I'm wrong I completely apologize, I just recall a similar method used to consolidate data while not easy could be plausible if resources were put into it.

---

Quote:

---

Originally Posted by Roth_Trailfinder

I'm sure they could do it if they wanted to. You've got an interesting idea, that I hope they take note of. That said, one byte is 8 bits. A kilobyte is 1024 bytes, or 8192 bits. That leaves a bit more room, don't you think?

---

Keep in mind that it takes an entire byte just to store a 0-9 or a-z "space". it's possible to store a 2-digit number in 1 byte as well. That being said, I think it would take more than a kilobyte to store the "state" of your craft because you would also have to keep track of which buffs are active (would take at least 2 bytes with the number of buffs), the stacks remaining (another byte or two because of unique buffs), the step you're on (a byte or so), and the current condition of the craft as well (poor, normal, good, excellent - this would take another 2 bits at least). There would also be overhead involved because it would have to store what particular item you're crafting, and whether you opted to select HQ or NQ materials and the total quality gained from those (it has to take this into account when the synth finishes so it knows what items to subtract from your inventory).

The system you presented representing digits would also require 1/2 of a byte per digit (it takes 4 bits to store a number from 0-9, and can actually store a number up to 16). I'm not sure where you were going with your 102x102 grid (comes out to 10404 spaces), but that doesn't multiply up to 1024 either ...

Quote:

---

Originally Posted by Airget

If they could consolidate the information from crafting into bits ..... etc

---

That's good thinking, but you left out a whole lot of other stuff...

The state of the synth.
Is SH up? SH2? WN2? Manipulation? Is it a good? excellent? How many stacks of SH, SH2, WN, Manip, CZ, ING2, ING1, GS, Innovation, Maker's Mark, IQ stacks (and if using specialist actions), Whistle stacks, etc etc.

It is LOT of information to track. Oh, and durability too. Left that out.

So, without breaking it down to how many bits they can pack all this stuff into.. you probably start to realize that it becomes fairly complicated once you do this for every synth across every server for every character.

However... do you really care if you DC during a synth of steel ingot? No. An adamantite nugget? Meh. I guess losing 15k is annoying.

What about a 60 1-star craft? A 60 2-star craft? Both of those. Certainly.

Solution. Track the synth state ONLY when requested by the player. Player goes to an NPC. NPC engages something w/ the server to track the synth. Probably wouldn't be used all that often. But used when it counts. All this business about consolidating bits... doesn't matter nearly as much. Instead of tracking every synth and storing that data after every step for every synth, you'd only be doing it for players that actually need it and when they want to do it.

And that is reasonable.