Jump to content

OroCrimson

Member
  • Posts

    77
  • Joined

  • Last visited

6 Followers

About OroCrimson

Recent Profile Visitors

6,704 profile views

OroCrimson's Achievements

  1. Sorry, I will not and cannot support Nightly releases. They update far too often to keep on top of and don't have a clear versioning system to provide support for. When IKEMEN decides to release a new stable build, I will update my screenpacks to support it. Otherwise, anyone is welcome to release a patch for it themselves.
  2. Okay I've finished my tests. 125 characters in category 1, 16 characters in category 2, 159 characters in category 3, and a few stray ones in categories thereafter. All of the characters were available fine. 159 characters were able to share the Darkstalkers slot, 125 characters in the street fighter slot, with nothing missing. Certainly not stopping as short as 28. So I'm afraid the issue is user error. Either one of your characters are invalid (they wouldn't appear in a normal roster either, and as such break the rest of the slot they're in) or you're using an unsupported version of IKEMEN Go (If Nightly put a hard limit on slot sharing, there's nothing I can do.) Tested In versions 0.98.2 and 0.99, both work as expected.
  3. Let me investigate this. I think it should be infinite, iirc I confirmed it with the IKEMEN Go devs prior to releasing it with such claims. But I don't think I tested it properly with really large rosters in one slot. 28 still seems low even for my tests though. But it's been a while. Note if you're using a later version of IKEMEN Go, like the Nightly release, I can't guarantee compatibility. This is only supported for certain on IKEMEN Go 0.99. Later versions of the engine might break things or put a limit on how many characters can share a slot. Anyway I'm copying my biggest roster over and will do some tests (using 0.99) to see if I can recreate this issue. In the meantime, I also remember that slot characters can break if any of them in the chain are invalid for some reason. If any character wouldn't show up in the roster normally for whatever reason (invalid name, path, or something else), then it can wreck the whole slot past that point (weird wonky character order or controls, missing further characters down the line, getting stuck in the chain no longer able to change characters in that slot, or stopping the chain entirely.) So checking which character is first missing in that slot can sometimes help troubleshoot the problem. Assuming of course it's not a hard limit on the engine that surprisingly no one ran into until now. If I run into the problem as well with a known good roster then we got a big problem and that really sucks.
  4. Afraid not, this isn't a game. This is a screenpack for IKEMEN Go. Think of it like a menu replacer mod for a video game. And think of MUGEN/IKEMEN as like, Gmod but for fighting games. It comes with a very bare bones package and then you can download content for it. Anyway sorry, this isn't a Capcom vs SNK game. Just a menu people can use to make their own.
  5. Apparently it's time for my annual "remember that this community exists and check up on it". I keep thinking that I'll get emails for replies on here but I don't. I should look around if there's an option for that. So the main reason I include POTS' active tag is because it has toast messages for Tagging In and Out, which by default uses sprites while my lifebars use text with a bitmap font. So I include it so I can edit it to use text and match the combo counter and other messages. A lot of these wouldn't need any edits on my part, the player can add these modules themselves. A player may want to edit the position of the Dash gauge in the Universal Dash Cancel System, but otherwise these modules seem plug and play. The Clashing system looks like it already uses text toasts, if not it may need an edit. I imagine the Training Mode Attack Data Display uses the debug font, which is changed in the installation instructions for this screenpack and should be fine. As for a 4:3 version, it's a pretty popular request. And nowadays I have more incentive to use it myself with things like ShaderGlass and EmuVR Window Capture support. It would just take a pretty considerable amount of work and isn't a small maintenance update, and I've not been further developing ILX with more features. Still, if there is one more update I want to make to ILX it'd be making a 4:3 version. I just sadly wouldn't hold your breath, I'm (clearly) not super active in MUGEN creation and come in and out of it in rare bursts. Hopefully you've already figured this out by now, but I believe this is already toggleable in IKEMEN's options menu. Oh boy, an issue with the included action.zss I guess. Seems the current nightly may have broke something here since the last time I updated it. This is why I don't like nightlies but they really are taking quite a long time to release 1.0 or even 0.100... I do wish they'd release some more stable releases to bridge the gap to 1.0, instead of waiting years for the perfect build to release as their big 1.0. 0.99 is about 2 and a half years old at this point and the nightlies have gained a lot of features since then, and I feel like the only reason it hasn't mandated a stable update is because they don't like the aesthetic of a pre-1.0 release going past 0.99. Which I'm starting to feel isn't worth holding onto. Right now, the latest version of the screenpack supports the Nightly build released on 1/22/2025, so its the latest version actually supported. Will probably work on some after that, but after a certain point changes will break it. I may come back to fix it but keeping up with a Nightly release is not something I can feasibly do. I strongly encourage the IKEMEN Go team to put out a stable release soon, as its clear the userbase has largely moved on from 0.99, and it's hard to target support for ever-changing Nightly releases. Damn, these are sick. This is definitely pretty advanced stuff (custom zss code and the like) that I'm not personally familiar with how to do. If he's cool with other people bastardizing his code though, I can take a look at what he's done and see if I could learn how to reincorporate some of the stuff. Again I can't guarantee it'd come in an ILX update, but I've been long sitting on a project for IL3 that I could explore new options for. Using a more custom action zss would definitely make future version compatibility even more tricky though. That's definitely worth looking into, I'll check it out!
  6. Woah, you got the link to work! I was trying that method but I guess I didn't do it right. Thanks!
  7. As seen here: The links unfortunately are dead. Does anyone have this stage?
  8. So fun fact, the IKEMEN version is a little different. Instead of having 5700 hidden slots, it only has 15, including RandomSelect. That's why it can run so well in IKEMEN Go. IKEMEN adds a new feature MUGEN doesn't have called "shared slots", which lets multiple characters share the same slot and you can toggle them with a button press. A theoretically infinite amount of characters can share the same slot, and it only renders the one that's currently selected so it doesn't tax the engine. So I just set the buttons to toggle the slot character to Left and Right, and a theoretically infinite amount of characters can fit in each category. I haven't really tested it with extremely massive character lists yet, but in theory this would run even better than MUGEN when getting into absurdly high roster counts.
  9. Oh huh, I missed a lot of new replies to this post for some reason. I need to check in more often. --- That is super bizarre. I hope you managed to fix this. I'm not sure why a screenpack would affect a character, but I suspect whatever did is related to the older action.zss or POTS tag files included with the screenpack, as those are the only things I can think of that affect character behavior. I included them so I could change the text/aesthetics for those things, but they probably are in need of an update so I should work on that. --- Ah yeah, Discord cracked down on direct links to files. FWIW, you can still download it if you copy the link and paste it into Discord first. Discord just wants you to access the link from their client, then it'll download fine. This was an April Fool's gag, runs abysmally bad, and isn't being updated so only works correctly on v0.99. So I wouldn't really recommend it anyway. But the option is there if you want to try it. --- Unfortunately I have no plans to work on MUGEN versions. My screenpack uses some IKEMEN GO exclusive features and imho IKEMEN GO is the next evolution of MUGEN and where my focus lies. I don't really intend on going back to standard MUGEN. I give permission to anyone who wants to backport my work for MUGEN (or any other modifications of my work to be honest), just be sure to credit me.
  10. Its updated to fix this issue. All the slots def files were out of date. This is fixed in 1.0.7, but rather than download the whole thing you can just download this slots.zip and replace the slots folder in data/cvsbe with this one.
  11. Alright, it's 2 am for me right now but I'll look into it tomorrow. It sounds like I might have forgotten to make the correct adjustments on the 840 slot system.def file.
  12. Sorry for the late response. Are you using the latest version of this screenpack (1.0.6?) Versions before 1.0.5 were made for 0.98, and this is what happens when you try to use them on 0.99. This is what v1.0.5 fixed.
  13. It might not. I haven't developed it for nightly builds since they're always changing. I only support the latest stable build.
  14. Unfortunately, I wouldn't know because I didn't use IKEMEN Go until 0.98, and this screenpack specifically is designed for version 0.99. You'd have to edit data/ikegen/system.def, but to what extent I'm not certain.
  15. This sounds like a possible bug with IKEMEN. You should ask about it in the IKEMEN discord's help channel. VSelect is outdated as it has not been updated since the release of IKEMEN Go and does not support IKEMEN Go's new features, including Cell Skip which this screenpack uses. You can't use vselect with this.
×
×
  • Create New...