Jump to content

theSLAYER

Administrator
  • Posts

    22827
  • Joined

  • Last visited

  • Days Won

    991

Everything posted by theSLAYER

  1. Your actions seem to speak otherwise.
  2. And it's as tho you didn't read the other comments. @PkHexBoi if you weren't aware, someone already came to your defense with that exact reasoning. And... ... I've literally explained how I wasn't serious at my reply to you, and how it was a multifaceted response. It wasn't just a message having fun with ya, it also aimed to educate future readers or readers that are unaware. And frankly, I went straight to this post isn't really a good reason.. Do people really expect stuff in the Unreleased/Beta PKM Gallery to be legal? As someone who uploads a bunch of files to our main subcategories, I take offense at that Anyhow, sheesh, this is why they need warning labels on obviously hot coffee, and why I typically lock comments on uploads.
  3. I feel like the screenshot bears no relevance to what you are asking, for the most part. There are some situations where PID and IVs are linked in newer games, but presently the known bruteforcable methods (what I linked) are for Gen 3 and Gen 4.
  4. Don't get me wrong, I'm just having a bit of fun. Don't you see the smiley I attached after the image? I wasn't seriously criticizing them. It's just.. we get this kind of question all the time. So, it was a multifaceted response; in one angle, if one received this kind of response, one'll always check the overall section before asking such questions ever again, well at least hopefully that's the case. In another angle, I actually did answer the question; I took a screenshot that spells the answer and focuses on the big bold red test, instead of being plainly rude. In yet another angle, I also taught future readers that there is an overall section header, in case they were unaware. Hopefully, they'll come to realize that various uploads are in various different sections, and each section covers their own niche.
  5. For both, it is probably sufficient to randomly create TID and SID. This is just something you may need to be aware of for the Platinum one: There is a known PID and IV correlation, so you can't just randomly assign values. You gotta search for the values and them type them in:
  6. If it's from one of the recent Gens, you can just assign it randomly. What makes it's "Japanese", is the language dropdown.
  7. Hmmm.. It's as though you didn't read the disclaimer at the head of this section.. :3
  8. Save twice in-game before trying to use it on PKHeX.
  9. You're not supposed to double click on the file. You're not supposed to download and run the file. Only download it. You're supposed to import it into the correct window/form of PKHeX.
  10. Hence why you weren't infracted or anything. I just hid the post and explained my rationale, no other consequence involved :3 edit: like I said, stop putting your fakemon in a thread meant for archival. If anyone here cared about an event that never got English localization, and wants a fake recreation, they can go to your thread. If people want a fakemon "just for fun", they can go to your thread. I've hidden your post again. This is strike two. I'm trying to be nice to you. You're not making it easy.
  11. Well it's a kinda odd issue to have. @Kaphotics @ReignOfComputer you two have any troubleshooting ideas?
  12. I'm unsure if this is properly a PKHeX issue; many others can run it just fine. I'm equally baffled by this. In any case, let's start by trying to get proper user access for the program:
  13. Sorry, was editing my post, so I guess you didn't see my other two responses, being
  14. Did you extract the program from the zipped folder? Did your antivirus remove the program? Did you try to open it in a place where you don't have permissions?
  15. Someone posted a mon here, and I've hidden the post. We're not looking for fakes, especially when it a "fake localization" of an event. I left your other thread intact; it's fine if you want to make it publicly available for other fans of fake stuff, but don't throw that fan-made stuff into this page trying find/archive relevant information about the real event, alright? :3
  16. well, to be fair, how you stay up to date is via reading the changelog. That message was only on Discord cause someone asked there first.
  17. Attach your save file to the next reply to this thread. Only upload your save file.
  18. Plugins periodically have to be updated by their developers whenever PKHeX updates (PKHeX may use new functions, change how their existing functions work etc). The plugins are not managed by PKHeX devs. If you're having issues, create a github account, and post an issue on their github page. https://github.com/darkfiggy/dmaxplugin/issues (I think you're referring to this) Anyhow, I don't think this has anything to do with us.
  19. First off, please don’t multi post. If you had new information to add, and no one had replied to your latest post, just edit into your latest post. Next, PP of moves can’t be restored by Potions, so I don’t know what you’re on about.
  20. It’s a quote from a pin I made in our Discord server. So technically Kaphotics is correct about the handwritten part; it was written by me, just written elsewhere first. link here (you would have to be a part of our server to see the message): https://discord.com/channels/343093766477053953/367479180398428170/827821664900481045
  21. Based on your error, I believe it's this: It's a new legality detection added to the latest PKHeX update. This just means your mon was always illegal to begin with, just that past versions of PKHeX didn't have the check, and well, researchers weren't aware of that RNG relationship. Now that it's known, we can check for it, and expose certain hacked mons as being illegal.
  22. Meltan and Melmetal wasn't programmed into Ultra Sun and Ultra Moon. If you want to get a fake one in, you gotta do a ROM hack, tho at that stage, it's like adding any species or fakemons into ROM hacks ><
  23. Huh? The shiny locking (or unlocking) of an encounter has nothing to do with save editing.
  24. Details for Index 64 of normal_encount and normal_encount_rigel1 and normal_encount_rigel2 (no differences) Rewards for Index 64 of normal_encount and normal_encount_rigel1 and normal_encount_rigel2 (no differences) Details for Index 64 of dai_encount Rewards for Index 64 of dai_encount
×
×
  • Create New...