Construct 3 has no option to save in a project folder from browser

Currently I use =>"construct3-win64-c77-stable" instead of The browser version. I tried using the Browser version but realized there is NO option for a Project folder save that has ALL the folders along with it like, objects, events, items etc. so I use the abover version. But I have [2] versions the c75 and the c77. But issues with c77 have me using the c75. I can load updates in around about way but it works much better. I get to see ALL the folders in my project! Does some one have an answer to that browser base not saving to project folder?

Thanks.

Where did you get "construct3-win64-c77-stable" from?

Does c77 mean r77? If so, you're on a verrrry old version of C3, as the current latest stable is currently r276.2

Hey Jase00. Yeah but the version I am running is 276.2 cause I look from the about section form the menu tab. It reads 276.2 :) I tried the C77 64bit but some issue, not loading. So I resorted to the later. C75 stable. that's just the version written for 64bit. I AM running the latest stable C276.2. So this are good. I have ALL the behaviors, addons everything that the browser version offers. Only THIS one allows me to save to Project Folder with ALL the containing subfolders. Sweet. Thanks for the reply though.

Well I got that file from construct 3 website in a response to question I had about a standalone version some years back. Today I loaded a hard drive that had my zip files on it. VIOLA! C77 stable 64bit. Happy, Happy. installed it, downloaded the NW.js version 049 Installed that right over the C77 installation I havve it ALL. Yup save to project folder. Runs great. So; Browser NAH! If there were a way to upload thiose [2] I would. Sincw I can not find them on the site any longer. Yes I download the updates and it finds construct 3 installed and updates that version :p. cool. Have a great day.

Chromium-based browsers like Chrome and Edge support saving to a folder. Currently Firefox and Safari don't support it yet.

I'd strongly recommend just using the browser - the NW.js editor builds are basically deprecated, no longer developed, probably have a bunch of bugs that don't happen in the browser, and providing you use a Chromium-based browser no longer does anything much that browsers can't do now.

Yeah using C3 in NWJS has been an unpredictable mess whenever I've tried to use it - And believe me, I've tried to get it stable and working. But I constantly dealt with losing save data (silent crashes often happened, even on fresh new Win10 install), having to delete my Appdata and reinstall plugins over and over again, etc.

I have had the smoothest experience by using C3 in Chrome. My project is 100% NWJS based, so I test using Remote Preview and the Remote Preview Tool (Found here).

Not a single silent crash or anything when using Chrome.