World_Creator is the tool for building worlds. It is a free software released under GPL license.
You don’t need to install World_Creator. Just download, unzip and run. It will not access critical or sensitive areas in your computer, collect data from your computer or do anything harmful to your computer. You can use it without any internet connection.
Windows user notice:
(1) I recommend you put World_Creator under a path that contains English characters only.
(2) The first time you run World_Creator, you may need to unblock the “unidentified developer” alert.
(3) When you run the test, you may see an alert about firewall. World_Creator will run a local server to simulate the multi-client environment. There’s no traffic to the Internet so there’s no security issue. In fact you can run the test without any Internet connection.
MacOS user notice:
(1) I recommend you put World_Creator in the Application folder.
(2) The first time you run World_Creator, right click the .app and choose Open in the menu.
(3) When you run the test, you will likely see an alert saying “World_Vision wants to monitor input”. You can deny that.
When updating:
Copy all files under Data/Worlds to a temp location. (Mac users need to use show package contents to see the folder)
Remove previous World_Creator.
Unzip the lasted World_Creator and copy the files from temp location under Data/Worlds
How to setup and compile the project:
World_Creator is developed with Qt framework. This makes things simple. Just get Qt Creator ready and open the World_Creator.pro with it.
Before compiling, here’s a few things you should be aware of.
(1) Make sure your native compiler supports C++17.
(2) Compile AngelScript(2.34.0) separately and change .pro file to set the path to this external library.
(3) World_Creator also uses other libraries such as asio and sqlite3. They are used in direct source codes format and already included in the project.
(4) Source codes are all in UTF-8 encoding, with lots of Chinese comments. If you want to compile it with MSVC, you need to change the encoding to UTF-8 BOM, or else MSVC will output strange errors. Personally I think it’s a flaw in the compiler. Apple Clang and g++ don’t have this issue.