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

[lucid]

If it was a bug, it may already be solved in the 1.3.2.5 changes. I have a hard time reproducing the problem so it is challenging to test. I don't want to release it yet because I made some pretty major changes and want to make sure there aren't any cases where it might get hung up and stop synthing (mid synth)

[Aethenoth]

Maybe loosing my internetz for a week is a good thing. You'll have a killer new UI for MK and then MB will (hopefully) be out too! There won't be any fish left!

[vadrek]

Originally Posted by lucid

If it was a bug, it may already be solved in the 1.3.2.5 changes. I have a hard time reproducing the problem so it is challenging to test. I don't want to release it yet because I made some pretty major changes and want to make sure there aren't any cases where it might get hung up and stop synthing (mid synth)

Thanks for the program.

Can you add Perfection if used = Rapid synth?

Also Hand of the gods = 4 syths without dur loss
Thanks

[lucid]

Originally Posted by vadrek

Thanks for the program.

Can you add Perfection if used = Rapid synth?

Also Hand of the gods = 4 syths without dur loss
Thanks

Thanks for those notes, they will be useful when adding abilities.

Once all users are able to use abilities reliably, support for more abilities will be added. With each iteration, I try to iron out the major bugs so the program doesn't deteriorate into a pile of ****.


Testers needed!
Test version 1.3.2.5 is out at
PLEASE WATCH THIS VERSION CAREFULLY! There are considerable modifications to the way abilities are detected, and I am the only one who has tested this version so far. The best way to test is probably to use hasty hand (only), since you know it will always be up the first attempt and can debug more easily - without having to interact with the game, which can interrupt the bot.

It is especially important for people who have had a hard time using abilities to test. Don't leave it unattended, it might bomb your synth; but I hope not!

Changes in 1.3.2.5:

• Shutdown action didn't occur after running out of materials/crystals
• "Always On Top" can now be toggled anytime
• Success/Failure moved to status UI, msgbox popup removed
• Disabled maximize button
• Wait will be skipped if the synth will break
• Abilities including Hasty Hand should always trigger at appropriate times

[pezzjunky]

Excellent work Lucid!

I have been running your tool off and on for several days and it has been working great. I have not had any issues with the abilities you have available for 1.3.2.5 or 1.3.2.4. I have a question regarding the “Bold if Extra Durability Exceeds ###.” Is this not working with patch 1.18. I think they changed Bold > Careful and this may be the problem. Similarly, an option “Touch up until ##” would be awesome for finished goods. I know your probably too busy fixing actual problems to deal with enhancements at this point. Thanks again and I will let you know if I find any bugs.

[lucid]

Originally Posted by pezzjunky

Excellent work Lucid!

I have been running your tool off and on for several days and it has been working great. I have not had any issues with the abilities you have available have for 1.3.2.5 or 1.3.2.4. I have a question regarding the “Bold if Extra Durability Exceeds ###.” Is this not working with patch 1.18. I think they changed Bold > Careful and this may be the problem. Similarly, an option “Touch up until ##” would be awesome for finished goods. I know your probably too busy fixing actual problems to deal with enhancements at this point. Thanks again and I will let you know if I find any bugs.

Thanks!

Pending abilities working, there are actually few major bugs. All of the ones I can think of off the top of my head are only issues in very laggy situations. There is some tuning I want to carry out, but not many people complain about the pace of the bot so it doesn't seem to be a high priority.

Once abilities are confirmed working by a few more people who experienced the problem more abilities and other features (possibly including touch up) will be added. Touch up has been requested by a couple of people, but several requested various crafting abilities, so they will be prioritized accordingly.

Bold mode does work! 0 will bold unless the synthesis is going to break, 40 is a conservative value for using bold ("careful") at R50 on a synth that is ~R40. You can adjust as you see fit - lower is more aggressive. It will not bold when the element is unstable due to the greatly increased durability loss. I know bold mode is far from intuitive, there are plans to simplify it in the future.

Thanks for reporting on your experiences, the feedback from a broad array of people really helps to focus on the improvements that will really make a difference.

[pezzjunky]

Got it! I figured the feature only used Bold if durability was over the specified number.

So I guess I spoke to soon about no issues. I was so impressed that it was working at all that I really didn’t pay close attention (I could never get Moetoy to even start a synth).

1.3.2.5 does not use any abilities when they are available.

1.3.2.4 missed abilities on 3 out of 8 synthesis. By missing 3 out of 8 I mean that at least one time during the run it had and abilities available and did not choose it (excluding times when an ability was already chosen. It seems like your algorithm accounts for that) The only common factor was that Fulfillment was at the top the list of abilities available. One time it was by itself and not chosen, another time it was above TT and neither was chosen, and the last time it was above Preserve and neither was choosen. There were times during this trial that Fulfillment was on the top of the list and an ability was chosen...

I hope that made sense and will help you trouble shoot. If id didn't make sense let me know and I will try and clarify.

Overall though, 1.3.2.4 is still VERY functional and I will continue using it!

Thanks again!

[lucid]

Originally Posted by pezzjunky

1.3.2.5 does not use any abilities when they are available.

I am going to cry myself to sleep

[dellsharpie]

Im at my wits end here!

I downloaded the program but cannot get it to run. Every time I try to open the program my FFXIV window crashes, similar to if I were to alt-tab out of full-screen mode.

I updated my DX, most recent drivers to my GPU, but cannot open the MastrKraftr program without experiencing this crash. I believe it must be a driver issue, because FFXIV also crashed when I tried to update other programs.

When I attempt to run MastrKraftr by itself I recieve an unhandled exception:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MastrKraftr.MainForm.MASTRKRAFTR_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.235 (RTMGDR.030319-2300)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MastrKraftr
Assembly Version: 1.2.4226.15011
Win32 Version: 1.3.2.4
CodeBase: file:///C:/Users/Brad/Desktop/MastrKraftr.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.232 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.235 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

I'm not the most technical guy in the world, but any information would greatly help.

[lucid]

dellsharpie - You must run the game in windowed mode, and I'm pretty sure you need to be administrator to prevent UAC popups.

If the UAC dialogue (Wikipedia) pops up, then it will crash FFXIV.

Really, anything which requires fullscreen access OTHER than FFXIV, will cause it to crash. This includes alt+tabbing out of FFXIV when the game was started, UAC, other games, etc.

Unfortunately, this is a limitation of FFXIV, not MastrKraftr.

[Aethenoth]

Originally Posted by dellsharpie

Im at my wits end here!

I downloaded the program but cannot get it to run. Every time I try to open the program my FFXIV window crashes, similar to if I were to alt-tab out of full-screen mode.

I updated my DX, most recent drivers to my GPU, but cannot open the MastrKraftr program without experiencing this crash. I believe it must be a driver issue, because FFXIV also crashed when I tried to update other programs.

When I attempt to run MastrKraftr by itself I recieve an unhandled exception:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MastrKraftr.MainForm.MASTRKRAFTR_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.235 (RTMGDR.030319-2300)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MastrKraftr
Assembly Version: 1.2.4226.15011
Win32 Version: 1.3.2.4
CodeBase: file:///C:/Users/Brad/Desktop/MastrKraftr.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.232 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.235 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

I'm not the most technical guy in the world, but any information would greatly help.

That error code comes up for me if you run MK without FFXIV open. If it doesn't detect it then that code comes up for me. You can still hit continue then choose to open FFXIV if you want, I think everything was still functional for me when I chose to do this.

If you want alt tab cabapility, you need to get an FFXIV windower. If FFevo is up and running, you can download their FFXIV Windower. Its the most reliable one I've been able to find (reliable i.e. updated) as the other ones I've found had better UI/programming, but patches seemed to break them. You can't alt tab with that one, but others alllow it if you find a copy that works for you.

I just run 2-3 windows at 800x600 cascaded across two monitors (one being a 58" Plasma when I'm at home, and I have plenty of space to manage everything. If you aren't happy with the smallest sizes FFXIV config can give you, there is a way to get 800x600 resolution or any custom resolution your card can handle. It requires a little hands on hex editing but there is a guide out there on ffxivcore that will help. Just search "run ffxiv in 800x600)

Just reading back over your post, it seems that you're saying you have ffxiv open then open MK then ffxiv crashes? and it also crashes other times.

If you go into your UAC settings you can go one setting less strict, and when MK opens it will still prompt for permission, yet the screen will not go black and cause FFXIV to close out.

Hope that helps somewhat.

[lucid]

Originally Posted by Aethenoth

That error code comes up for me if you run MK without FFXIV open.

That's surprising, it should give the following error in a popup: "Final Fantasy XIV is not running."

Maybe I broke that when adding dual box; will look into it along with abilities

Edit: I hate to be the bearer of bad news, but the fish bot will be on hold until the craft bot's features are 100% stable. There is no sense in beginning a new project if this one isn't up to par.

[perdosa]

Originally Posted by lucid

Edit: I hate to be the bearer of bad news, but the fish bot will be on hold until the craft bot's features are 100% stable. There is no sense in beginning a new project if this one isn't up to par.

I didnt have any Problems so far.. so im lucky and happy i dont use most abilties except Preserve and Hasty Hand, which were working fine.

I dont think that is bad news. Its actually good news that you are working on a Fish bot. If you want Craft bot's features are stable in the first Place im totally ok with that and can wait for the Fishing one.

Great work so far.

[Aethenoth]

Originally Posted by lucid

That's surprising, it should give the following error in a popup: "Final Fantasy XIV is not running."

Maybe I broke that when adding dual box; will look into it along with abilities

Edit: I hate to be the bearer of bad news, but the fish bot will be on hold until the craft bot's features are 100% stable. There is no sense in beginning a new project if this one isn't up to par.

I got that before the dual box update, but then get that. All it requires is opening FFXIV first which you need to do regardless if you are dual boxing, or MK doesnt capture the PID anyway.

And I'll try out the newest version and see how things go and get back to you today.

As perdosa was saying, its not bad news! Its great that you'd rather get one finalized working project, then move on to work on another. Otherwise you won't be happy with the workmanship. I'd rather have 1 excellent working program than two broken *** ones (seems to be par for the course on programs ive used =-) )

Keep up the good work!

[lucid]

Thanks for the encouragement, it just sucks when things still don't work for everyone after a week. It would be nice if I could see it happen on a computer, but I guess I will have to make the program get debug info from someone who does experience it. The problem is not knowing which information is going to be relevant to the issue.

For anyone who has the problem with abilities: Does your computer have a difficult time running the game? Perhaps the issue happens on computers that are slow, so they take longer to load values into memory?

The problem with abilities does not seem related to code (a "bug"), it appears to be memory or latency-related.