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

[Syllenus]

i too am having trouble with hasty hand not working. i tried using 1.3.2.2 and .4 with the same issue. it worked great for me before HH was changed to the detection method.

[dinin991]

Any ETA on the fish bot? I would love to try it out.

[lucid]

Originally Posted by dinin991

Any ETA on the fish bot? I would love to try it out.

The memory scan is running while I fix some of the bugs in the craft bot. The craft bot will always be a priority, but there shouldn't be a problem doing them in parallel. Hard to give an ETA on the fish bot, I'd like to say in the next 1-3 days, but want to work the craft bot bugs out first.

[aesculapius]

Originally Posted by Aethenoth

You're saying that you are unable to click synth after choosing stop? You need to let the program finish the last synth then you'll get prompted with the synth complete summary dialogue. After clicking that you can start again. You might need to reclick the icon in the task manager to make the dialog box show up because it doesn't pop to the front

Yes, the icon gets greyed out.

[lucid]

Originally Posted by aesculapius

Yes, the icon gets greyed out.

It is probably because the statistics message box popped up, but is not on top. This will be fixed in the next release, where the message box is removed and the statistics are on the status tab of the bot.

[elm33]

I noticed that if you have "wait up to 3x" selected, but your durability is 5 or less, it may still try to wait 3 times, causing a default failure. Perhaps a check could be put in place for example if durability 10 or less then do not wait. =)

[fancypantscat]

I just wanted to say awesome bot! I saw this post earlier but didn't try it out until tonight.

Can't wait to see what you do with fishing .

[aesculapius]

After a crash today I keep getting error. I tried restarting FFXIV, PC, getting a new copy of the bot, placing it in a new directory, and checked my processes for extraneous instances that might be interfering but couldn't find the problem

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Access is denied.

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

************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): Access is denied
at System.Diagnostics.ProcessManager.OpenProcess(Int3 2 processId, Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.OpenProcessHandle(Int32 access)
at System.Diagnostics.Process.get_Handle()
at MastrKraftr.MemoryAccessor.GetProcessDetailsFromPI D(Int32 SelectedPID)
at MastrKraftr.MemoryAccessor.SelectWindow(IntPtr RequestedPID)
at MastrKraftr.MainForm.Button4_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.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/Admin/Downloads/FFXIV/MastrKraftr/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.

[lucid]

Originally Posted by aesculapius

After a crash today I keep getting error. I tried restarting FFXIV, PC, getting a new copy of the bot, placing it in a new directory, and checked my processes for extraneous instances that might be interfering but couldn't find the problem

Has anything changed? Do you normally run it as a different user? On a different computer? It sounds like an access restriction, so something must have changed in the environment you're running it in.

Which version are you using? Any new hardware or programs? Configuration changes?

[aesculapius]

Nope. Nothing has changed. Same computer, same user, no new hardware. Running 1.3.2.4.

I can start the bot, but it gives the error when i press synthesize.



EDIT: ok.... so apparently it decided to start working again. Don't know what happened last night. But it started after I accidentally triggered the macro bar to run while the bot was running.

[lucid]

Originally Posted by aesculapius

Nope. Nothing has changed. Same computer, same user, no new hardware. Running 1.3.2.4.

I can start the bot, but it gives the error when i press synthesize.



EDIT: ok.... so apparently it decided to start working again. Don't know what happened last night. But it started after I accidentally triggered the macro bar to run while the bot was running.

Not sure what "the macro bar" is, but if it locks access to the FFXIV process, then it would mean MastrKraftr would be unable to read memory values (which is consistent with the debug info you posted).

Glad it's working, let me know if you find it happening in other circumstances. I'm in the process of doing some cleanup in the code, I'll try and include some handling for those cases so you get an intelligent message instead of a program crash.

Originally Posted by elm33

I noticed that if you have "wait up to 3x" selected, but your durability is 5 or less, it may still try to wait 3 times, causing a default failure. Perhaps a check could be put in place for example if durability 10 or less then do not wait. =)

This will be fixed sometime this week, but I need to figure out how it should really work. I'm thinking something like "if the remaining waits will break the synth" or similar logic instead of a fixed number.

Update: I'm currently testing 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

Maker's Muse has been held back until I can make further UI adjustments and do some refactoring.


Fish bot won't be ready for a few days still, damn real life responsibilities are getting in the way!

[aesculapius]

Here is the macro bar I was talking about btw.

Restart didn't help. It turns out a complete shut down did help though.

[lucid]

Originally Posted by aesculapius

Here is the macro bar I was talking about btw.

Restart didn't help. It turns out a complete shut down did help though.

Does it only happen after you open that program?

[aesculapius]

Having it opened didn't cause problems. What caused it was triggering a macro to run while the bot was running. I'll see if I can repeat it when I have more time.

[lucid]

it is likely because that program is locking the process in some way. My "fix" would only be for MastrKraftr to alert you of the problem without crashing, but I don't think it would work while a macro is working (unless the macro program is changed), if that's the case.