Jump to content

papadragon418

Member
  • Posts

    31
  • Joined

  • Last visited

Reputation

10 Good

About papadragon418

  • Birthday 10/25/1988
  1. Aside from making it shiny after it hatches? Question: for your shiny egg, do you give it your trainer information? Because the ID of the trainer that hatches it is the ID that matters for determining whether or not it comes out as shiny.
  2. So I was able to use a firmware spoofing script from GBAtemp to access the eshop and update my games. Yay! However, ram2sav dumps a file that the latest version of pkhex cannot read. Boo! (This is all for Pokemon Y by the way). If I delete the update, then I can use ram2sav just fine. Yay! But then I have to spoof the firmware and redownload it every time I want to get the update. My money would be on offsets getting mucked with. If anyone can help with this, I would appreciate it! Ramsav - bad and good.zip
  3. A quick note: if you've accidentally downloaded the update via spotpass, and it nags you to update every 24 hours or so, you can boot your system in recovery mode. To do so, 1) Make sure the system is off. 2) Turn it on. (DO NOT WAIT FOR THE HOME SCREEN TO SHOW UP) 3) Immediately hold down the shoulder buttons (L and R), the Up button on the d-pad, and the A button. You don't need to hold it for more than a second or two - the system will not proceed until you let them go. 4) A screen should show up asking you to update via the internet. Select "cancel." 5) The system will turn off. And just like that, no more update nag! As for the patch, I'm surprised it didn't get pushed out sooner. As soon as the QR code stuff hit Kotaku, you *knew* that the countdown had started, assuming it hadn't already.
  4. (If anyone notices something wrong with what I'm about to say, please feel free to correct me!) Based on the research done on the Gen VI file format (http://projectpokemon.org/wiki/Pokemon_X/Y_3DS_Structure), it would seem that PID has been divorced from pretty much everything. Gender, ability, nature, even Spinda's spots are now all determined by other bytes in the structure. The only thing I know for sure that PID determines is shininess. IVs, meanwhile, were sort of "accidentally" associated with the PID due to the prng implementation in Gen III and IV, but they fixed that issue in Gen V. Now, as for PKHeX giving legal PIDs and such, the answer to that is: they're probably legal as far as anyone knows. I don't know quite enough to be able to give you a more authoritative answer than that, but so far there hasn't seemed to have been any problems with it in terms of legality.
  5. Yeah, I had this happen to me just now. I had loaded a decrypted save and was editing a Pokemon. When I got to the OT/Misc, it threw this error. However, I was able to continue using the program, it's just that the text looked weird and bolded. When I reopened the program, my Trainer name was in wingdings or webdings or something. When I opened it again, everything was normal. So, it would seem to have something to do with the font. This is what I got. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Runtime.InteropServices.ExternalException (0x80004005): A generic error occurred in GDI+. at System.Drawing.Font.ToLogFont(Object logFont, Graphics graphics) at System.Drawing.Font.ToLogFont(Object logFont) at System.Drawing.Font.ToHfont() at System.Windows.Forms.Control.FontHandleWrapper..ctor(Font font) at System.Windows.Forms.Control.get_FontHandle() at System.Windows.Forms.Control.SetWindowFont() at System.Windows.Forms.Control.OnHandleCreated(EventArgs e) at System.Windows.Forms.TextBoxBase.OnHandleCreated(EventArgs e) at System.Windows.Forms.TextBox.OnHandleCreated(EventArgs e) at System.Windows.Forms.Control.WmCreate(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.TextBoxBase.WndProc(Message& m) at System.Windows.Forms.TextBox.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.0.30319.18444 built by: FX451RTMGDR CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- PKHeX Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Users/Maximus/Desktop/GEN%20VI%20Hacking/PKHeX.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL 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.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR 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.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- System.Numerics Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.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.
  6. Not to mention that having a second 3ds for this purpose will make said patching irrelevant. Granted, this is not practical or convenient for everyone, but still, it is an option. With any luck, the new 3ds will push the price down a bit as well.
  7. Are you sure it isn't an issue with the Hoopa not being flagged as a "Fateful Encounter?"
  8. If you mean PokeBank, then yeah, that is the answer unfortunately. What do you mean "searches the website successfully?"
  9. Whoops, did not read your full post there. Sorry about that. Yeah, that is weird.
  10. Perchance, that wouldn't happen to be the result of the little plastic switch on the SD card itself being in the wrong position, would it?
  11. http://projectpokemon.org/forums/showthread.php?44553-Guide-to-generating-legal-pokemon&p=195788&viewfull=1#post195788 Save it like this. Make sure to type that .ekx extension.
  12. You're going to want to move this over to the thread in Save R&D. The issue, to the best of my knowledge, is that you're not properly saving the file as a .ekx. Kaphotics updated PKHeX to make this easier - just select "All Files" in the file type, and type ".ekx" at the end. Check out SciresM's thread in Save R&D that's currently blowing up. It's actually pretty wonderful. Edit: Dang it Kaphotics beat me to it.
  13. This is kind of a stumper. The bit about not getting the grey bar when you run the web exploit raises an eyebrow. 1) Very stupid question, since I doubt the browser would crash otherwise, but you are connected to the internet right? 2) Quadruple check the address of the web exploit (again, it would seem weird for it to crash if you didn't get the right URL). 3) The only other thing I can think to try is to try accessing the web exploit via the QR code. It seems fairly clear that SciresM's code isn't running at all, given your lack of a debug file. This makes me think it's an issue with running the web exploit more than anything else. They're probably messing up something with the .ekx file, either with the extension or with the contents of the file itself.
  14. It's at the bottom of the settings menu in the browser. It completely resets it, wiping out your history, bookmarks, everything. A couple of users have found this helpful.
×
×
  • Create New...