Jump to content

Kaphotics

Helpful Member
 View Profile  See their activity

  • Posts

    7841

  • Joined

  • Last visited

  • Days Won

    451

 Content Type 

Everything posted by Kaphotics

  1. Kaphotics
    Trade evolutions require trading. If it has never been traded, it never could have been trade evolved.
  2. Kaphotics
    Those properties can only be used as filters; you cannot set to them because there is no setter in the source code. They're constant values based on the PKM class type. If you are looking to clear all trash, you can do it like so (filter for a specific pattern, clear and reapply): =OriginalTrainerName=Kurt .OriginalTrainerTrash=$[]00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00 .OriginalTrainerName=Kurt =IsNicknamed=false .NicknameTrash=$[]00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00 .IsNicknamed=false
  3. Kaphotics
    Opened in a hex editor; the file looks to be random junk. Probably the battery died and the storage stopped retaining data.
  4. Kaphotics
    Not able to replicate. You shouldn't be using hax anyway.
  5. Kaphotics
    Try a tool other than pk3DS. Probably just a bad ROM dump.
  6. Kaphotics
    Remove any plugins and try again.
  7. Kaphotics
    ALM's intent is to create battle-ready things, and to not necessarily retain input values. You're likely trying to generate something with a PIDIV-correlation, which means that changing it to be shiny after the fact is modifying the PID, and thus breaking the required correlation of values, making it not legal. If you've set up the trainers folder, ALM will regenerate with encounters according to the order of encounter type specified in its settings. Often times you'll need to use an external app to search for a PID combination that satiates your need for predefined trainer data & stats.
  8. Kaphotics
    Can't know unless you're more descriptive on what you're trying to load. A screenshot of the message would help.
  9. Kaphotics

    Bug Report

    Kaphotics replied to JLSgolden's topic in PKHeX

    Check the change log for encounter slot checks. The program requires more than just a valid PIDIV, as it also determines the encounter trigger seed/frame that started the full generation routine. The PIDIV is calculated last.
  10. Kaphotics
    The program gives you a blank save file to act as the holder for whatever mons you import/create. That OT is indicated at the top of the program. As indicated by the popup, the handling trainer is expecting PKHeX, because that is the handling trainer. The original trainer is from Gen4, and you are editing in a Gen9 context (Violet), so the OT could never be handling it anyway. If you want to be in a different context, load your save file, or change the program settings to change which blank save file context is loaded. Plugins not updated by the original plugin author may still be maintained by others who have made a fork.
  11. Kaphotics

    Bug Report

    Kaphotics replied to JLSgolden's topic in PKHeX

    not legal; doesn't have an RNG slot correlation (as indicated by the X when you hover) future updates will indicate it is not legal in gen4. the program is correctly flagging it in gen5+.
  12. Kaphotics
    You're changing more than just the OT name. Can't tell what else you're doing wrong because you're not descriptive enough.
  13. Kaphotics

    Save file size?

    Kaphotics replied to Danstorm1's topic in PKHeX

    Be sure you are transferring your save file correctly. If using ftp, be sure you are transferring binary format so the file is not truncated. If that didn't change anything, plug in your SD card directly and move the file manually.
  14. Kaphotics
    Use the drop-downs to build a set of commands. PK8 do not have WeightAbsolute & HeightAbsolute.
  15. Kaphotics
    Fixed on latest, although there's no real need to rebuild ROMs since cfw can use layeredfs.
  16. Kaphotics
    If a plugin is causing issues, go look for an update to the plugin. PKHeX is not responsible for plugins misbehaving after an update.
  17. Kaphotics
    Gen4 events are distributed with fixed version IDs. They do not match the recipient's version.
  18. Kaphotics
    pkNX does not do anything special with its text entry fields. If the game does not render the characters you are trying to use, then they're not available in the font.
  19. Kaphotics
    The text resources are the same. https://github.com/kwsch/PKHeX/blob/0bbba81fca3dca5d84b5f800a3496cbf4c9a1b45/PKHeX.Core/Resources/text/items/text_Items_en.txt Games that use different lists (like Gen2) have a separate list.
  20. Kaphotics
    Then it needs to be handled by the currently loaded Save File (probably is PKHeX). Don't disable the setting that automatically updates the handler data when you set it to a slot. Try setting it to a slot in the save file, and check again.
  21. Kaphotics
    Commonly happens when you reuse trainer data between games. Trainer name/ID should be unique, not the same (eg Sword and Scarlet should be different). If it has a handling trainer set and the current handler is the HT, then the HT must match the save file. If it matches the trainer data for the save file, then it should be handled by the OT, not the HT.
  22. Kaphotics
    Which trainer have you set the current handler as?
  23. Kaphotics
    Confirm that the file exists and that you dumped your ROM correctly.
  24. Kaphotics
    If they are from Kalos, then they are not from your Ultra Sun trainer. Re-read the popup and my message.
  25. Kaphotics
    No? Read the error message. Why is the current handler the OT, when it is being handled by a save file that is not the OT?
×
×
  • Create New...