Shamrock said, September 27, 2009, 09:09:15 amI see we are concentraiting on the character stuff. But what about expanding on stuff outside the character. I mean for a more full game environment. Till now we have been making characters and we code stuff into them.What I'm talking about is a common state for stuff like Variables and helpers. What if we had a common file just of helpers. Then we could have any character call on a helper that is in common. So you could have the gems of marvel, or the helpers characters of MVC, or fatalities, or the first hit thing of SNK, or the MVC "Great" on first contact but all of these things would be in a common file in your data folder. All characters could call them. So instead of programing a Jubilee that jumps out for each character, you could release the jubilee helper that any character could call on.It may be good idea to have a common cmd for these helpers but that might be pushing things a little.This same thing could be used for Variables as well. If we had that kind of helper system you could even program a stage interaction using the helpers in the common folder. Am I crazy or am I on to something?Does anyone know if this went any further then just a couple posts? If not my question is WHY?I would really like to see this discussed further!
Because it's hard enough as it is to keep proper standards for things so simple as gethits, let alone helpers.That's the bad thing about standards, only 3 people follow them and then someone else comes along and starts a new one for the same thing.
Agreed, that it would be tough to put in place and to keep up with. But this forum does have a MUGEN starter kit, so setting a standard may be easier to put in place. (at least a MFG standard)
Has the problem of there being 1000's of characters who may already be using those states or variables for something else. We have this issue with animations too (thanks asian countries who keep making up your own shit) but less so in a problematic sense. Calling on the existence of a helper that wasn't actually what it should be is more of a problem than calling an animation that will look wrong in a custom state.
I see... So making a new group following a new standard out of the blue would just further this problem even more.Maybe making a specific MUGEN version would help this problem.For example, we couple put together a new kit called "MUGEN ver. 1.1+helpers" and then people could release things specifically for it. As if it was a totally different version of MUGEN. That would clear up any confusion or problems.. correct?If a section was made for it on the forum we could then pin a thread showing the latest version of common file. Since I am sure it would need to be updated as time goes on. That shouldn't be to to hard for people to update their versions through the years.
In a way, many variations of this have been tried in the past.In mugenchina for example there were about 2 or 3 different releases of a moleboxed MUGEN build for encrypted characters. The problem was that the releases that were coming out for them could only be used on those specific versions, and this happened in what was (probably) the better organized community at the time (in terms of compatibility and releases).Rather than trying to venture into these kind of alternate-mugen-build affairs I think that a good method would be properly documenting instances of known (used and not completely made up) standards.I think that one of the core issues that have been present with this is that coders get overambitious with what they want to achieve with standards (adding things like bloodtype, hotness level... skin material?). Starting out small with actual needed standards and then building everything from there is a far better approach, in my opinion.
The best way to manage this would be compiling said list of genuinely important stuff and having elecbyte put it inside the engine documentation. That way everyone gets the doco when they DL the new version, and those people who have used "made up version Y" will then technically ahve to update to "official version X" because the doco says so.We do have an anim standard topic here at guild, i believe it's also at RS if that's still up and possibly at the TM forum too. If that could be pared down because it has lots of duplicates or "blah full game only" things in it, would probably be worth flicking on to elecbyte integrated into the air.txt file already using the same format as is already in said doco. So all they'd have to do is update the .zip.http://mugenguild.com/forum/topics/optional-animation-standards-138791.0.htmlTopic. JMM was working on it, spose it depends how much of that is worth "officially" sending to elecbyte.
Sweet, I will check that topic out.While we are it I think that a better method of encouraging compatibility would be to in someway implement (at least) a common version of this list in Fighter Factory itself and other competing IDEs for MUGEN-specific programming.
