Jump to content

PlasmoidThunder

Global Moderator
  • Posts

    5,918
  • Joined

  • Last visited

Everything posted by PlasmoidThunder

  1. CHARACTERS Added the following by YochiThMaster333: Pikachu Litten
  2. Pretty much all the links were dead anyway and it's not like I've been adding new ones even when they're posted here. No point in me sitting on the fence about it. I'm sure someone will make a new repository if people want them that badly.
  3. I've now removed all vore characters like I said I would, which includes the half-arsed vore removal edits and any of Alosson/Black Kyurem's characters that featured certain Yoshi edits. CHARACTERS Added Mew? by Monaka. Added Gatigorasu (Tyrantrum) by sametikuwa. Added September by Earth, Wind & Fire Tweenies_1998. Fixed link to MetalGuy's Pikachu.
  4. Set a var's value to the desired duration when you activate the buff and have it decrement until it reaches 0, which then turns off the buff.
  5. That should be all the characters added. Too many to list. This is already in the collection under [ Misc. ].
  6. You already have this thread, don't make any others requesting the same thing.
  7. Most characters don't, given the feature was added in 1.0 and people were still using old A.I. methods after the fact, hence I said to hope they do. They'll use AILevel if they do or var (usually 59) if they don't. There's many ways to code an A.I. with varying levels of complexity, so there's seldom ever a one-size-fits-all approach to it. Some split the A.I. stuff into its own set of ChangeStates while others append the A.I. logic to the human ChangeStates. Very basic ones typically check p2(body)dist x to throw out moves at specific distances in conjunction with random to limit how often it does this.
  8. You can either hope the A.I. adjusts itself with the difficulty setting (or has its own) and lower it, or understand how the A.I. was programmed so you can tweak it.
  9. It's valid, but I doubt it's correct. 01 is the same as 1. 01 = p2life = 1 && movecontact will return either 0 or 1. In short, the value can only be interpreted as the following: 1 = 0 && 0 (returns 0) 1 = 1 && 0 (returns 0) 1 = 0 && !0 (returns 0) 1 = 1 && !0 (returns 1)
  10. https://kohaku.trinitymugen.net/type-mugen-1-0/add-ons.html They're not clean rips and it only uses two of them, though.
  11. Firstly, don't post the same topic in multiple places. Secondly, the error refers to a code/memory exploit that only works in WinMUGEN.
  12. Moved to offtopic because this isn't MUGEN. It might help if you provided context.
  13. You don't have to pull a sob story every time you're called out on something either, it's really not that big a deal unless you keep doing it. Now then, let's avoid further disruption to this thread.
  14. Please don't pretend to be a moderator. This is his thread, he's allowed to post videos like this.
  15. I imagine most if not all the OD links are down, which is going to be a hassle to fix.
  16. I believe so. Depends on whether movehit resets immediately when you get hit, or at the very least before -2 is processed on the following frame.
  17. On trade, the character is no longer in the attack state, so none of that code will execute.
  18. Hi, please don't hijack other people's threads. Make a new one if you have a query.
  19. Was wondering if anyone had the Hong/Lie shown in this video (excuse the volume, it's from 2008): The version in the Touhou collection is from 2007, though Waybacking Daiya's site shows it was updated in 2008, which I'm guessing added all the Lie stuff. The file itself wasn't archived, unfortunately. This is all assuming it's not a completely separate character edited from the original.
  20. Add single=1 to the boss' select entry. Make sure to check the default select.def, there's a bunch of new parameters in IKEMEN.
  21. Lifebars don't support their own localcoord, they're scaled by the screenpack's localcoord. Unless the 1.1 edit changed it, EvE's localcoord is 320x240, while your lifebars appear to be intended for 640x480.
  22. Assuming this is MUGEN, lifebars don't support unique localcoords. The lifebar being too big means it's designed for a localcoord that's higher than the current screenpack's. Note that making the game window larger doesn't increase the localcoord, as everything is being scaled up.
  23. Then you'll have to ask someone to grab them for you. There is no secret alternative way in outside of ban evasion, which I can't condone.
  24. I appreciate the enthusiasm, but you didn't need to make three separate posts.
×
×
  • Create New...