(This hasn't been mentioned before, has it?)
I think I've just found a quick way to fix the problem with bgpalfx in stages with SFF files compiled by MCM:
Simply open the stage in a hex editor, and change byte 32 (the one highlighted in the screenshot) from 01 to 00 (it's the byte that specifies whether the palette type is shared or individual). That's all.

I haven't tested this thoroughly, but it's worked 2 out of 2 times for me.

I still wonder why Sés still has not fixed this easy bug.

Because he's Sés, master of ALL THINGS MUGEN! HOW DARE YOU SPEAK AGAINST HIM!

... he's a lazy bum.

[quote author=XGargoyle link=board=4;threadid=1403;start=0#msg15913 date=1056021265]
I still wonder why Sés still has not fixed this easy bug.
[/quote]
Because WE pointed out HIS mistakes...
and while i'm there, i'll remove that shameless (Ok, not really) plug too =P

Edit:
Oh yeah, maybe characters that look bad (all black or messy colors) in Linux Mugen can be fixed the same way?

[quote author=Foxy guy link=board=4;threadid=1403;start=0#msg15930 date=1056077675]
Because he's Sés, master of ALL THINGS MUGEN! HOW DARE YOU SPEAK AGAINST HIM!

... he's a lazy bum.
[/quote]

...or maybe cause I'm NOT working on MCM since a loooong time... and I DO NOT read the forums... and I DON'T have any notice about this.

If you are not "a lazy bum", make a MUGEN editor yourself.

People like you make me hate programming FREE programs.

Bye.

Chill out, dude. As far as I know, this bug has been in MCM since time began. You really should have fixed it by now, rather than putting in more half-broken features.

And if you're going to get so upset over someone calling you a "lazy bum," you're gonna be seriously hurting in the real world. Grow a thicker skin.

Realmente no me importa que me llamen "lazy bum", es el tono de todo su mensaje lo que me cabrea.

Estoy harto de que cada vez que asome la cabeza en el mundo del MUGEN aparezca gente insinuando que yo paso de todo y que voy de chulo o algo así, como si quisiera hacerme famoso o algo.

Todo lo que hago es GRATIS y para vosotros (recuerdo que yo JAMÁS hice ningún personaje).

Sinceramente, no entiendo como se me puede exigir o reprochar que no arregle ciertos fallos (que hasta hace unos días ni sabían que existía) cuando ninguno de vosotros paga nada por mi trabajo.

Hace mucho tiempo que tengo el MCM abandonado por varias razones, estoy con otras cosas y no sé si lo retomaré algún día. Si corrijo este error es porque alguien me lo dijo de buenas maneras y no criticando como otros.


P.D.: Si alguien lo quiere traducir que lo haga, yo no lo pongo en inglés porque no sabría decir justo lo que quería.

[me=XGargoyle]looks at his signature: What's the problem being a lazy bum? [/me]

Btw, as requested by sés, here's the translation:

I don't mind about being called a "lazy bum", but it was how it was said that really upsets me.

I'm tired of seeing that everytime I pop into the scene people tells me that I don't hear their feedback and that all I want is to become famous or something like that.

Everything I made was FREE for you (I should remind you that I NEVER made a character).

To tell you the truth, I don't understand how someone could demand or reproach that I don't fix certain bugs (that until a few days ago I didn't know they existed) when no one has paid me for my work.

It's been a long time since I haven't worked on MCM by several reasons, I'm currently working in other things and I don't know if I will continue working on MCM. If I fix that bug is because of someone commented me that bug in good manners and without criticizing as other people did.

Well Ses has a point in there, the manner of communication may have also hurt him somehow. I know, I'm susceptible to this as well. If they give you feedback in a haphazardly written manner, you are most likely to revolt than to listen, especially if mixed with swearing.

But soon, you'll find out you'll have to listen to them anyway.

There are people who likes the comments, criticisms and feedback and all, but minus the brutal frankness, brutal truthfulness and insensitivity towards the listener.

Just my two cents.

PS:I'm probably the worst lazy bum around in the mugen community right now. look how many times i've held back releasing updates! T.T

uguu~~....

Or.... he could just release the source to MCM

It's his work....would you want to just give away a project you've spent countless hours on so sombody can fix a couple things and take all the credit??? I know I wouldnt.
Seriously if we paied em $20 a copy I'm sure the thing would be perfect but we don't...he's donating his time to the Mugen community and you bash him. Considering all this stuff I don't blame him one bit for puting it on the back burner.
BTW whats stopping you from making everything the old fashon way with notepad and a couple DOS programs if this causes so much trouble?

Sés keep up the good work.

Herman: What the heck is that "ubuu" thing you've been using? I want to know it.

BlackxKnight:
The problem isn't so much with us using one program or another (I've always just used Notepad and Sprmaker myself) as it is with the multitudes of Mugen creators/converters out there who don't even realize there are any problems with MCM.

Sés:
Sorry, I don't know why it didn't occur to me to e-mail you. I guess I was just under the impression that you'd basically left the scene.

[quote author=Bemitri link=board=4;threadid=1403;start=0#msg16499 date=1057872095]
Herman: What the heck is that "ubuu" thing you've been using? I want to know it.
[/quote]

UGUU!

That is my cute impression. My trademark! ^.^

Well there you have it. Go watch the Kanon anime if you need proof.

By the way, Sés, since you're here: If you do decide to update MCM, how about fixing a couple other errors while you're at it? Bytes 16-19 are supposed to specify the number of groups in the SFF, but it looks like MCM always sets them to zero. And bytes 28-31 are supposed to indicate the size of the subheaders, but MCM always sets them to 00 02 00 00 (512) instead of 20 00 00 00 (32). I don't know of any significant problems these two errors might cause, but they should be pretty easy to fix, even if just for the sake of conforming to the file structure format specifications. And I expect they could become problems in the future, particularly if any future SFF editing tools try to make use of that data.