These will be in next version. And for gc. I think it is good. But I haven't tried very good for now.Are these things that have been released or have been made? and how close is the GC conversion to playable?

Little endian. And I will try utf16.I asked earlier about the bmg editor. could the you change encoding default to utf16. I was also wondering if you have the number of entries(pointers) as little endian or big endian. If its big endian could you change it to little endian? this is for the bmg files in chibi robo. help on this would be appreciated.


I decided to bring out a beta version. But it's beta so
some things maybe don't work or not good.
http://florian.nouwt...ds/3.0Beta2.zip
Okay, I will release source now. You know that the link is in the first post.I decided to bring out a beta version. But it's beta so
some things maybe don't work or not good.
http://florian.nouwt...ds/3.0Beta2.zip
Just pointing out that you need to honour NSMB Editor's source code license, the GPL, and release the *full source* for every single binary you release.
Yes, ALL of them.
More info here: http://www.gnu.org/copyleft/gpl.html
We GPL'd NSMBe back then to support the open-source ROM hacking community. That's why you can use code from me: the license allows it.
But man, please respect the license terms. It's not that hard. I'm starting to get pissed off, and you definitely don't want NSMBe to go closed source. See what happened to the Wood firmwares for example. That's a real shame for the entire community.
(BTW you reaaally need to check the license salad you have there as a result of taking code from soo many projects. I bet you have lots of incompatibilities there)



I *am* pissed off because this is NOT the first time I've "reminded" him that NSMBe is GPL. That's why he opensourced his project in the first place, because I told him. If I hadn't told him, this'd still be blatantly violating the license.
And he had no excuse to not know: Every single source code file from NSMBe has a bunch of text at the beginning saying that it's under the GPL and blah blah, as required by the license. So, common sense says that if you read that something is under a license that you don't know what it is, then you google it.
I'd like to know much code in MKDS Editor is actually written by him. Probably very little. His source code is just a big folder with heaps of code copied from other projects...
