Is it possible to create my world using WorldPainter and export it to a playable Minecraft world?
Yes, that is more or less the point of WorldPainter. However you mention that you are a school teacher, which makes me think you may be using the Educational edition. If so then unfortunately WorldPainter doesn't support that; it can (for now) only create maps for the Java edition of WorldPainter.
On that note, would you know if it's possible at all to create maps for Education Edition?? Other tools etc...
I have heard of such tools, which can convert Java edition maps into Pocket edition maps (which I believe the Education edition uses), which would also be able to concert WorldPainter-generated maps. I don't know anything about these tools though, such as where to find them and how well they work.
So forgive me if I am doing something horribly stupid, but I am getting a weird problem when I am working with a large map.
The map size I am attempting to create is 20480x17220 blocks, so it's decently large. I had created the heightmap in World Machine, and I set out to begin coloring and populating the terrain in World Painter. It imports fine, everything works as it should except it wont let me view the very bottom of the map.
This is not the end of it either. When I zoom in, not only does the problem continue, but the further I zoom in, the less map becomes visible. I also am unable to scroll to the eastern side of the map, with the problem also worsening as I zoom in.
Now, the weird part is that this trend of the problem worsening as I zoom in doesn't continue forever, as when I zoom in to an extreme amount, the problem disappears, allowing me to scroll over the entire map. If I attempt to scroll out over these hidden areas, it lets me, and it even allows me to then scroll over the entire map as if the problem didn't exist, until I zoom in again, causing the problem to return.
I tried updating the program (I was on an outdated version) to no avail. I tried running it in compatibility mode for both Windows 7 and 8, both with the same result. I tried running it with both DirectX and OpenGL. I even tried just leaving it for an hour, hoping it would magically fix itself (while I ate dinner). Surprisingly the last attempt didn't work, and the problem persists.
I just released version 2.4.4 of WorldPainter. This is a minor functional and quality release which fixes some problems and usability issues:
The usability of the Complex Custom Material editor has been improved. Instead of continually adjusting the occurrences so that they add up to 1000‰, which made it extremely difficult to set them to exact values since they would be changed from under you continually, that redistribution is now done when saving the material, in such a way that their proportions stay the same (so it will not affect the result)
WorldPainter can now be started in safe mode. In this mode it will not load plugins or custom brushes; not change the visual theme or graphics acceleration method; not load the background image; etc.. This may allow it to start successfully if a problem with one of these is causing normal startup to fail. Functionality may be limited; this mode is not intended for doing work, but for diagnosing problems and changing preferences. To start WorldPainter in safe mode, use the new "WorldPainter (Safe Mode)" start menu entry, or on the command line add the parameter "--safe"
An advanced setting has been added to specify the Minecraft installation directory, if you have it installed in a non-standard location. See here for details
For unknown reasons, initialising the Minecraft runtime in order to be able to load .nbt files sometimes failed, causing an error when trying to add custom objects to a Custom Object Layer. This failure should now happen silently so that you can continue normally (but without .nbt support)
A workaround has been implemented for a bug in the JIDE docking framework that prevented WorldPainter from starting on Mac OS X with Java 10 installed
If you have been getting crashes while trying to start WorldPainter on Java 10 on a Mac, or when trying to add custom objects to a Custom Object layer, please upgrade and let me know if you're still having the problem! You will automatically be offered this new version when you next start WorldPainter, or you can download it from the first post. Please enjoy!
Got the same problem. But, if you just leave it to its error spamming business then it will export the map eventually. I also have a few other issues I didn't have on previous versions such as the brush size resizing itself up again when I reduce the size of the brush...
It could be cause I still use Mavericks OS X 10.9.5. and world painter is developed for newer versions of OS X.
I just released version 2.4.5 of WorldPainter, which (hopefully) fixes a few bugs. Hopefully, because two of them are on Mac OS X, which I don't have so I can't reproduce the bug or test the fix. So if you're on a Mac, please let me know if these problems are now fixed!
On Mac OS X with Java 10, lock the visual theme to Metal to work around a bug in a support library. To use other visual themes, downgrade Java to version 9, or wait for a new release of WorldPainter with the fixed support library (it is not yet known when this will be released)
Bug fix: fix a recurring error message while Exporting a world on Mac OS X
Bug fix: fix a problem with the scrollbar range being too small when zoomed out, making it difficult to scroll to the entire extent of the world
You will be offered the new version automatically when you next start WorldPainter, or you can download it from the first post. Please let me know if you still encounter any problems, and enjoy!
Hi! I'm creating a map for upcoming 1.13 version using Custom Biomes feature for the new ocean biomes. When I export the map for Minecraft and open it with Minecraft 1.12.2 the map seems OK (without the new biomes, but with my terrain). But if I open it with the last snapshot of 1.13 the world is generated from zero, using the seed.
I wonder if 1.13 can only upgrade valid 1.12.2 maps. If you remove those custom biomes (quickest way is Global Operations -> reset biomes to automatic), and any other aspect you may have added (mod blocks?) which aren't valid for 1.12.2, does 1.13 open the generated map correctly?
I just released version 2.4.6 of WorldPainter, which fixes a bug introduced in version 2.4.4, namely that when creating or editing a Custom Terrain, the thicknesses of the layers of a layered material were also being normalised to add up to 1000. It should only do that for noise or blob-type materials. This has been fixed. Sorry about that!
You will be offered the new version automatically when you next start WorldPainter, or you can download it from the first post. Let me know if you encounter any additional trouble and please enjoy!
I found the problem. This error (world regenerating with the vanilla seed) happens when I export any world with the "Allow Minecraft to populate the entire terrain" checked and open it with the snapshots of 1.13. If I left that unchecked, the terrain generate successfully.
That's good to know! Unfortunately there's not much WorldPainter can do about that. The way it flags that a chunk should be populated is correct for version 1.12.2. Presumably version 1.13 will also regenerate the chunks around the edges of an existing 1.12.2 map, which will also have that flag set.
This flag has changed in 1.13 and become much more complicated. It will be a while until I have reverse engineered it and can provide full 1.13 support in WorldPainter.