Free FFXIV Craft Bot - Craft While Minimized! (Limited Time)

[elm33]

Bug Report:

Issue:

Program failing to release Synthesize button after Stop button used

Cause: Lack of Shards to complete synthesis

Conditions to recreate Issue:

1. Select a specific number of items to synthesize
2. Begin synthesis
3. Prior to overall progress completion, deplete shards required
4. Click Stop to end the synthesis queue and release the program back to normal state

The outcome of this will result in Pause, Stop, and Synthesize remaining unavailable, forcing user to close program, and then restart.

---

This is not a big issue but I thought I would report it as it appears its a bug in the Stop logic.

Thanks

[Aethenoth]

Originally Posted by elm33

Bug Report:

Issue:

Program failing to release Synthesize button after Stop button used

Cause: Lack of Shards to complete synthesis

Conditions to recreate Issue:

1. Select a specific number of items to synthesize
2. Begin synthesis
3. Prior to overall progress completion, deplete shards required
4. Click Stop to end the synthesis queue and release the program back to normal state

The outcome of this will result in Pause, Stop, and Synthesize remaining unavailable, forcing user to close program, and then restart.

---

This is not a big issue but I thought I would report it as it appears its a bug in the Stop logic.

Thanks

Lucid can correct me if I'm wrong, but he has not yet accounted for running out of shards before the materials do. (Materials are accounted for being exhausted)

Originally Posted by lucid

Yeah, I forgot crystals would run out at a different place than materials, I'll work on that one.

Also, the stop button is stuck because it will try to carry out the entire synthesis process and bring you back to the synth menu. If it cannot achieve this (due to exhausted shards, in this case) it will remain unobtrusive in the background and poll the memory until it detects its back to start.

In this case the best thing to do is not run out of shards :lol: but in the case you do, just close and reopen to keep thing going

[lucid]

Thanks for reporting this. The small things do matter to me, that little bit of polish is what makes the bot really nice versus just "ok".

Aethenoth is correct, I will try to find a simple way to address this.

[elm33]

Originally Posted by Aethenoth

Also, the stop button is stuck because it will try to carry out the entire synthesis process and bring you back to the synth menu. If it cannot achieve this (due to exhausted shards, in this case) it will remain unobtrusive in the background and poll the memory until it detects its back to start.

In this case the best thing to do is not run out of shards :lol: but in the case you do, just close and reopen to keep thing going

I understand the intent i.e. to finish the synthesis and the goal of creating that level of eloquence within the program.

With that said, I believe the Pause/Resume functionality already satisfies this. When pausing, the program will finish its current synthesis and then pause.

When I think of stop, I think of "stop all actions now" so perhaps the simple fix is when stop is pressed is to just close all threads/processes associated and return to normal state, since the ability to pause and complete a synthesis is already implemented.

Either way is fine, I guess it just seems like a double implementation of the functionality that already exists with pause-

[lucid]

You actually make a really valid point.

The only problems are that people are used to the way it works, and clicking stop will allow the shutdown action to complete, so you could stand up/logout/shutdown without having to wait for the synth to complete or complete it manually.

The best compromise might be:

• Click Stop button once, it turns into "Halt"
• Click Halt, and the bot stops what it is doing and resets immediately
• If the bot reaches the end of the synth with the button in the "stopping" state, then the button will be reset with the rest of the UI

Thoughts? Be honest, I don't mind if you disagree

[Aethenoth]

Originally Posted by lucid

You actually make a really valid point.

The only problems are that people are used to the way it works, and clicking stop will allow the shutdown action to complete, so you could stand up/logout/shutdown without having to wait for the synth to complete or complete it manually.

The best compromise might be:

• Click Stop button once, it turns into "Halt"
• Click Halt, and the bot stops what it is doing and resets immediately
• If the bot reaches the end of the synth with the button in the "stopping" state, then the button will be reset with the rest of the UI

Thoughts? Be honest, I don't mind if you disagree

Remember when I wanted the "emergency stop" added? We could compromise and have it "stop" at one press, and then if you press it again it emergency stops? I guess it makes better sense when someone else explains it. I'll be happy if you call it "Emergency Stop" rather than "Halt"

Sounds like a plan? :thumbsup:

[elm33]

Originally Posted by lucid

You actually make a really valid point.

The only problems are that people are used to the way it works, and clicking stop will allow the shutdown action to complete, so you could stand up/logout/shutdown without having to wait for the synth to complete or complete it manually.

The best compromise might be:

• Click Stop button once, it turns into "Halt"
• Click Halt, and the bot stops what it is doing and resets immediately
• If the bot reaches the end of the synth with the button in the "stopping" state, then the button will be reset with the rest of the UI

Thoughts? Be honest, I don't mind if you disagree

I think that is a very good idea and it satisfies both desires.

Since you asked me to be honest, If i was implementing it in code, I would probably just add an additional button and change the label of the existing button

Ex: "Finish and Stop" and "Stop Now"

That adds a little more detail to the difference between stop and halt. It is a little less slick than a changing button, but it seems more informational/user friendly, and I think the existing UI size could accommodate a 3rd button on the Synthesis tab by shrinking the existing buttons a bit.

edit:

It also just occurred to me that once Synthesize is pressed, its grayed out so serves no real purpose at that point (other than letting you know the program is active, which should be visually obvious)

Another approach may be once the synthesize button is pressed, to then have it relabel itself as "Finish Synth and Stop" and then covert the existing stop button to "Stop Now" or something like that.

That would allow you to keep a simple 2 button interface, implements the slickness of a changing button, gives people an additional option, and seems more user friendly / clear to the end user on what each button does.

Thanks!

edit:

A 3rd possible idea may be to put Stop Now, and Finish Synth and Stop on the same page as Pause (since they are all related to stopping synthesis) and just have the synthesize button on the Synthesis options page.

Originally Posted by lucid

Thanks for this, I will look into it later today. BTW, was the bot running, or did you have it paused? I have a feeling the empty number of items to synthesize was the problem.

I neglected to respond to this earlier!

The bot was neither paused nor running. It had completed its previous task and was in the same state it would be in as if it was just started. I am sure the issue was the having the "All" box unchecked, and a blank "Number of Items to Synthesize" field. When the program tried to convert the str to an int, it found nothing and threw an exception.

[Aethenoth]

Originally Posted by elm33

I think that is a very good idea and it satisfies both desires.

Since you asked me to be honest, If i was implementing it in code, I would probably just add an additional button and change the label of the existing button

Ex: "Finish and Stop" and "Stop Now"

That adds a little more detail to the difference between stop and halt. It is a little less slick than a changing button, but it seems more informational/user friendly, and I think the existing UI size could accommodate a 3rd button on the Synthesis tab by shrinking the existing buttons a bit.

edit:

It also just occurred to me that once Synthesize is pressed, its grayed out so serves no real purpose at that point (other than letting you know the program is active, which should be visually obvious)

Another approach may be once the synthesize button is pressed, to then have it relabel itself as "Finish Synth and Stop" and then covert the existing stop button to "Stop Now" or something like that.

That would allow you to keep a simple 2 button interface, implements the slickness of a changing button, gives people an additional option, and seems more user friendly / clear to the end user on what each button does.

Thanks!

edit:

A 3rd possible idea may be to put Stop Now, and Finish Synth and Stop on the same page as Pause (since they are all related to stopping synthesis) and just have the synthesize button on the Synthesis options page.



I neglected to respond to this earlier!

The bot was neither paused nor running. It had completed its previous task and was in the same state it would be in as if it was just started. I am sure the issue was the having the "All" box unchecked, and a blank "Number of Items to Synthesize" field. When the program tried to convert the str to an int, it found nothing and threw an exception.

The button needs to look like this:



Or I'm not playing anymore.

[elm33]

Aethenoth - I guess now that I think about it, that button is already there, its that red X in the upper right corner =)

[Fanfic1]

Thanks alot for your work on this bot it's helping me tremendously with my busy life.

Just a question (so I don't have to scroll through 20 pages)

Has anyone gotten banned for using this bot? How do people normally use it (timeframe wise)?

Thanks again and keep it up!

[Aethenoth]

Originally Posted by Fanfic1

Thanks alot for your work on this bot it's helping me tremendously with my busy life.

Just a question (so I don't have to scroll through 20 pages)

Has anyone gotten banned for using this bot? How do people normally use it (timeframe wise)?

Thanks again and keep it up!

If anyone has, it hasn't been reported. I don't know ANYONE who has been banned for botting yet though.

Regardless I keep the synth times to roughly 8 hour stints. Sometimes I'll fish over night after messing around but never more than 12 hours of play time at once. Just think what the limits of a human playing would be and as long as you dont go over that you should be fine. Anything more than that is going to be too obvious.

[timebleeds]

The key to that is moderation. Don't craft more than 24hrs non stop and try to take a few breaks occasionaly (like go afk near a repair npc and got your stuff fixed or go do other stuff away from pc 15min or more).

Keep a sharp eye on conversation so people know you're not afk, some people put the away status and that's bad idea. I've used it when I go to sleep but I look for spots no one and I mean no one would dare go to. Like a zone filled with 50-60 mobs and I hide somewhere safe and just mad craft, or an instance quest (any location) just go afk there.

Like I said, the key to using this is moderation and monitoring.

[Aethenoth]

Havent heard from you in a solid day. Been busy with the latest and greatest?

[lucid]

v1.3.2.7 is out!

• Guildleve support
• "Stop Now"/"Emergency Stop" button click "Stop" first
• Synthesis log
• Play sound on complete (or not)
• Popup on complete option
• Added requested abilities: Maker's Muse, Hand of the Gods

Guildleve mode can also be used to perform a synthesis which is not in your recipe book yet.

Everyone is forced to upgrade, hopefully having everyone on 1.3.2.7 will make it clear which issues exist. Some people were still running 1.2.x.x... talk about living in the stone age, they didn't even have abilities!

[jdstang]

The new version isn't using skills for me. Everything worked fine in previous versions.

Also would it be possible to add the skill "Pefection" in future versions? With maybe an option to use either standard, rapid, bold, on success of the skill.