YesNoOk
avatar

why does MWC always kill my system.def-settings? (Read 395 times)

Started by steffano, April 08, 2009, 03:26:10 am
Email this topic
View printable version
Share this topic:
Page 1 of 11   Go Down

steffano

why does MWC always kill my system.def-settings?
#1  April 08, 2009, 03:26:10 am
i like to add characters and stages with MWC, cause its really comfortable. but everytime i save it, my screenpack-settings and other codings i edited in the system.def are back to standard settings.

WHY?! that makes really no sense for me, cuz where the fck does this program get the infos, when MWC and mugen only can use the infos from this system.def with my edited codes? there should be NOWHERE other infos on my whole hard-disks.
Last Edit: April 08, 2009, 05:54:38 am by steffano

XGargoyle

Re: why does MWC always kill my system.def-settings?
#2  April 08, 2009, 08:59:05 am
  • *****
  • Hedgehog Whisperer
  • Red Bull addict
    • Spain
    • xgargoyle.mgbr.net
Check that you're actually editing the system.def from the screenpack, not the one that comes with mugen by default. Also, check the file permissions for the system.def are not on "read only"
XGargoyle: Battle posing since 1979
http://xgargoyle.mgbr.net
http://www.pandorabots.com/pandora/talk?botid=e71c0d43fe35093a  <-- Please click that link

steffano

Re: why does MWC always kill my system.def-settings?
#3  April 08, 2009, 05:45:17 pm
maybe i found the problem. seems mugen ignores all changes when i open the system.def after opening mwc, and when i click "save" mwc sets all changes in the system.def back. i didn't know that -.-

anyway, thanks for response
Page 1 of 11   Go Up