Just download the version for your OS. It contains all the files you need.hi,im new here.
im confused on how to download,the download doesnt lead to rpg maker,but a file called "nwjs"
im window user,which one i should download?
or do i need the base of the prigram the first place?
im confused,which one should i download if i wanted download newest mv / mz?Just download the version for your OS. It contains all the files you need.
The newest ? That should be 0.85 I think. Can be found here :im confused,which one should i download if i wanted download newest mv / mz?
If you just need the engine, download one of the archives suitable for your OS from the bottom of the list.I'm.... not really sure what I'm supposed to be doing here.
i think he meant the “nwjs-v” one the one that before the x64 folderI'm.... not really sure what I'm supposed to be doing here.
The OP has some links to some old versions of nwjs, which is the core RPGM MV games are based on. Once on the linked repository you can then find all versions of nwjs, old and new, by going up the directory tree. That's about all I can tell you I'm afraid.I think I'm in the wrong thread, does this thread have the link to download the engine and make your own game in RPGMaker MV? If this isn't the place what is this thread about?
I'm quite a beginner so I'm a bit lost here
pk2000 that link is dead. can you please reupload itRpgmaker MV Newdata (upgrade/downgrade files)
You must be registered to see the links
symbol means "debug symbols". it is a version you give to bug testers so that their bug reports contain more useful information in case of crash.but,what about the other files inside that folder are they relevant / somewhat important?
like, "nwjs-symbol”, “nwjs-SDK” , “nwjs-sdk-symbol” or inside folder "x64"?
I honestly don't recommend you even mess with any of this.and whats the differences between the content thats inside “live-build” folder,and the “newest version” thats on the main indexes? (the "v.0.88.0" folder)
i see.so the important ones are the main 3,the nwjs are the engine the 2 are needed if something needed to use for the engine incase of bugs and wanted upgrade, downgrade or just want something helps you to build or play content.symbol means "debug symbols". it is a version you give to bug testers so that their bug reports contain more useful information in case of crash.
SDK means "software developer kit". it is a version that contains both the stuff you need to play, but also the stuff you need to create content.
nwjs-sdk-symbol is a combination of both.
the program might be needing the sdk to apply updates to the game engine.
as updating the game's engine before running it is an option it has (you have to choose it, it won't do it automatically).
which usually improves performance and solves bugs. although in rare cases it can introduce new bugs. so keep this in mind.
It might help if you inform us which OS you are using.Hi, this is kind of related to this thread but 've been running into an issue with saving when using the nwjs engine. Specifically for Daily lives in my countryside. It crashes when I try to turn the sound of or turn auto dash on. When I search for a save file nothing comes up. I've been asking around for a couple of days and haven't gotten any response as of yet.
Hi, this is kind of related to this thread but 've been running into an issue with saving when using the nwjs engine. Specifically for Daily lives in my countryside. It crashes when I try to turn the sound of or turn auto dash on. When I search for a save file nothing comes up. I've been asking around for a couple of days and haven't gotten any response as of yet.
It might help if you inform us which OS you are using.
/private/
== a folder named private sitting on root/private/
. so it isn't android./private/
.Hi, this is kind of related to this thread but 've been running into an issue with saving when using the nwjs engine. Specifically for Daily lives in my countryside. It crashes when I try to turn the sound of or turn auto dash on. When I search for a save file nothing comes up. I've been asking around for a couple of days and haven't gotten any response as of yet.
You're on the right track, but it's not a permission issue in the way you are thinking of./private/
== a folder named private sitting on root
Windows does not use /, it uses \. So it isn't windows.
Linux does not have a private folder sitting on root. so it isn't linux
I had to look upYou must be registered to see the linksandYou must be registered to see the links
android does not have a/private/
. so it isn't android.
macos DOES have a/private/
.
thus he is using macOSX.
according to the error, the folder the game is trying to write into is marked as read only. so this is a permissions issue.
I would suggest trying to change the permissions on that folder.
note: I do not mean setting unlimited permissions on /private/.
I mean find the specific subfolder as close to the right end of that long folder name as you think is needed. (it might take a few tries).
or it might be some other issue.
although I am a bit weirded out by the need to give write permissions into private directory.
maybe it has a virus or something? this needs investigating further.
I recognize this game from the picture, and someone in that game's thread just recently mentioned that this game's appdata folder is full of his passwords and credit card info in plain text. which suggests it is virus infected.
Wow, that is the dumbest form of quarantine i have ever seen.Problem here is that RPGM wants to write the save files inside the game folder inside the app, which it can't because it's running from this ad-hoc read-only location. That's where the error comes from.
It's not exactly a sandbox. The intention is that apps that want to write data write it outside of the app (to Application Support of the user). It's only RPGM that doesn't do this. So maybe it's RPGM that's poorly designed here? I don't know, nor do I really care.Wow, that is the dumbest form of quarantine i have ever seen.
I had no idea macOS was that poorly designed.
not giving a quarantined program access to its own folder is beyond stupid.
every other sandbox implementation i have seen gives a sandboxed program the illusion of full access.
where it "can" write anywhere it pleases. (it just won't actually write anywhere outside the sandbox. so if it is trying to change c:\windows... well, it will think it is but actually won't be thanks to the sandbox.)