Pages: 1
Posted on 04-21-13, 12:57 pm (rev. 2 by  Hiccup on 04-21-13, 03:04 pm)

Karma: 2754
Posts: 533/2091
Since: 06-26-11

always say they are already being edited when they are not.
Posted on 04-21-13, 01:05 pm
Fire Brother

Karma: 3646
Posts: 93/1120
Since: 11-29-11
Yes, that's a really annoying problem. I've the same problem, by that file. But I have this to by w8.nsbmd. I don't understand that.
Posted on 04-21-13, 03:05 pm

Karma: 2754
Posts: 534/2091
Since: 06-26-11
I have added some others which also do this...
Posted on 04-21-13, 05:43 pm
Super Mario
( ͡° ͜ʖ ͡°)

Karma: 10020
Posts: 3261/4457
Since: 06-08-11
Hmhmhm I will have a look, this is an interesting bug
Posted on 05-02-13, 08:17 am
Death by cuteness

Karma: 6574
Posts: 3/598
Since: 05-01-13
If I might add something, it was still working in build 356 but was broken in build 357, unless you already knew that then disregard this post.
Posted on 01-14-16, 11:52 pm
この記号は… 解読できないよ…

Karma: 6044
Posts: 1757/2727
Since: 01-17-13
If you use MKDSe, you can split the .nsbmd into a untextured .nsbmd and a .nsbtx. Then, after putting both back together into a new .nsbmd you will replace the old one with, you will be able to edit it without encountering the error, no matter what NSMBe revision you're using.

To extract/replace the old .nsbmd you fail opening, close and reopen NSMBe, then don't try editing/hex editing the file. Thus, you won't have 'edited' the file, and won't get the 'File is already being edited' error when extracting/replacing the .nsmbd.

I didn't test with every of the files, but it seems to work flawlessly.

Posted by Hiccup

I might add map_dragon.nsbmd?
Pages: 1