For those who can't seem to edit the legendary core count, there was a little mistake in the code. You can find the correct .exe attached to my post (and I've submitted a pull request on Github too @Type_O_Dev )
How bad are the chances of getting banned from using this save editor for an off-line game?
I want to keep my switch clean until we have a more mature and secure scene (still haven't hacked my console), but I'm seriously considering using this to save 50 hours of my life. I just need it to hack a crapton of core crystals and a couple of overdrive protocols... that's all.
My OCD got the best of me with this game... and I really want to be done with it to never touch it again.
But isn't the stuff that is needed to just get the save off the console enough to get us banned? Because it is an illegal program.Thank you, I merged your changes.
If there are more offsets wanted please let me know. So I can add to final project
--------------------- MERGED ---------------------------
It would be extremely hard to get banned with this editor as we are not hacking code. We are only editing for items, stats. We are not changing characters and hacking game
But isn't the stuff that is needed to just get the save off the console enough to get us banned? Because it is an illegal program.
Is there an updated compiled .exe file for the editor?We are not running the tool on console.
This would be no different from sharing a save, there is no checksums I have heard about that compare saves to actual game play.
The bans being issued were from people accessing N shop servers and download titles not purchased
Is there an updated compiled .exe file for the editor?
Awesome, I thought Checkpoint (how I get my saves off my console) itself still had a change of getting people banned.We are not running the tool on console.
This would be no different from sharing a save, there is no checksums I have heard about that compare saves to actual game play.
The bans being issued were from people accessing N shop servers and download titles not purchased
what's "battle Exp" ? and whenever I try to set it's value I get an error
what's "battle Exp" ? and whenever I try to set it's value I get an error
Every number greater than 1 gives me an error and btw this happens even with the options that used to work in the previous versions of the save editorWhat did you set it to
I am also getting an error every time I try to edit a value. (was using 99 and 9999999).What did you set it to
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.FormatException: Additional non-parsable characters are at the end of the string.
at System.ParseNumbers.StringToInt(String s, Int32 radix, Int32 flags, Int32* currPos)
at System.Convert.ToByte(String value, Int32 fromBase)
at XC2Editor.HexEditor.SaveDecimalValue(Byte[] fileBytes, HexDataInfo info, Int32 value)
at XC2Editor.XC2MainForm._Lambda$__0-1(HexDataInfo hexData, Int32 value)
at XC2Editor.XC2FieldTypeEditor.SaveValueToFile(Button btn, EventArgs e)
at XC2Editor.XC2FieldTypeEditor._Lambda$__R6-2(Object a0, EventArgs a1)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs 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.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(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.7.3101.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Xenoblade Chronicles 2 Save Editor
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
I am also getting an error every time I try to edit a value. (was using 99 and 9999999).
Code:See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.FormatException: Additional non-parsable characters are at the end of the string. at System.ParseNumbers.StringToInt(String s, Int32 radix, Int32 flags, Int32* currPos) at System.Convert.ToByte(String value, Int32 fromBase) at XC2Editor.HexEditor.SaveDecimalValue(Byte[] fileBytes, HexDataInfo info, Int32 value) at XC2Editor.XC2MainForm._Lambda$__0-1(HexDataInfo hexData, Int32 value) at XC2Editor.XC2FieldTypeEditor.SaveValueToFile(Button btn, EventArgs e) at XC2Editor.XC2FieldTypeEditor._Lambda$__R6-2(Object a0, EventArgs a1) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs 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.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(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.7.3101.0 built by: NET472REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- Xenoblade Chronicles 2 Save Editor Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0
You mean that I should ignore the error message ?ok let me check
--------------------- MERGED ---------------------------
hit set value fisrt then save
I was able to set 99190 no prblem
no need to apologize when you've followed through and fixed it my man . thank you so muchyes I broke it but now is fixed sorry
updated release