EasyPickins

The new double-sized tilesets go into the Tiles/2x folder (they should already be there in the Tiles.zip file). There are a few old-sized tilesets in the Tiles folder used by the editor. In TileZed (and WorldEd), make sure the Tiles folder is pointing to "Tiles" and not "Tiles/2x".

Mostly because of all the tilesets.

WorldEd comes with the latest Rules.txt. The "erosion" code replaces the old grass/bushes with new ones when loading the map in-game. The editor only displays the old grass/bush tiles. You can place specific new tiles in TileZed from any of these tilesets and they will appear the same in-game. They must be placed on a "blends_natural" floor tile. d_plants_1 f_bushes_1 e_XXX_1 (non-jumbo tree tiles)

The editor doesn't display jumbo trees. Trees in Forest and DeepForest zones are randomly turned into jumbo trees when you export the map using WorldEd.

These are the most current versions I think. BuildingFurniture.txt BuildingTemplates.txt Tilesets.txt BuildingTiles.txt

The map looks ok on my computer. I'm guessing the Tiles directory isn't set correctly. You can change the Tiles directory in WorldEd's options or in the TileZed's Tools > Tilesets window.

If you attach the testing_0_0.tmx file I can look to see what the problem is.

The image files must be named XXX.png and XXX_veg.png. WorldEd adds _veg to the name of the file you are dragging to get the name of the vegetation image.

The 2x tiles aren't split up like that. Make sure you're not using an older version of TileZed by mistake. Make sure the Tiles Folder is set to "Tiles" and not "Tiles/2x"

Updated the tools February 20, 2017. BuildingEd Fixed crash when pressing the Delete key while moving objects. Autosave files in the user's .TileZed directory can be opened and deleted using the Welcome screen. Autosave files are created for buildings with unsaved changes every 2.5 minutes. If BuildingEd crashes, it should be possible to open a recently-saved autosave file. Note: For buildings that have previously been saved, autosave files are created in the same folder as the original TBX file.

Could you PM me the TMX file?

In this picture, everything looks ok doesn't it? That's the cell opened in WorldEd. In the second picture, it looks like the PZW file is in a different folder (...\ndmapfiles\untamperedbackups\rosebery.pzw) which would explain why nothing is displayed (it can't find the map/building files). So I'm not quite sure what problem you're having now.

The PZW (world) file holds the filename of each TMX (map) file relative to the PZW file. For example: <cell x="0" y="0" map="rosebery/roseberymap5_0_0.tmx"/> In this case, your files should be arranged like this: SomeDirectory/ rosebery.pzw rosebery/ roseberymap_5_0_0.tmx Don't run BMP To TMX again, that will overwrite the TMX files.

Use a "Dormer (E)" for the left-to-right roof object.

I updated the Linux zip to include the missing libQt5GUI.

I updated the zip files to fix a crash with the Roof tool.

It comes with Qt 5.8.0 in the lib/ directory. Possibly I left a library out though.

You can try these for 64-bit Linux. I built them on Ubuntu in VirtualBox. They should be started with the provided shell scripts (TileZed.sh, PZWorldEd.sh) TileZed + WorldEd for Linux 64-bit

Unfortunately it appears the GUI library used by the tools (Qt 5.7) doesn't work on Windows XP.

When the 2x tilesets were created, some tiles were moved to new positions in their tileset and some tiles were removed entirely. When the game sees an "old" map created before the 2x tiles were added, the game will try to fix moved or missing tiles. The official maps were all updated to use the new 2x tilesets. If you look in each map.info file, you'll see this line was added: fixed2x=true When the game sees "fixed2x=true" in map.info, the game will not apply any fixes to the tiles used by the map; the game assumes the maps have already been fixed. You can choose to leave your old maps alone, or update them to use the new 2x tilesets. To update your old TMX files for 2x tilesets, use the Tools > Check Maps menu command in TileZed. You can check all TMX files in a directory by pressing the 'Check now" button, or check only the current map by pressing the "Check Current Map Only" button. This will print a list of tile issues that may need to be fixed. Double-click on an issue to go to that location in the map. There's also a "Check Buildings" command that checks BuildingEd files for tile issues. After updating your maps and buildings, use "Generate Lots" in WorldEd to test them in the game. Remember to add "fixed2x=true" to the map.info file. @AtoxwarriorI think the "Unknown grime_wall" error is because WorldEd is trying to launch an older version of TileZed. You need to change the app that is associated with the TMX file type (so it uses the new version of TileZed, not the old one).

Latest Version Here: https://theindiestone.com/forums/index.php?/topic/23803-latest-tilezed-worlded-and-tilesets-may-14-2018/ If you have a 32-bit version of Windows, download "TileZed + WorldEd 32-bit". If you have a 64-bit version of Windows, download "TileZed + WorldEd 64-bit". Download your TileZed version of choice AND the Tilesets listed above. You should create a folder and unzip both the "TileZed + WorldEd" archive and the "Tileset images" archive into that folder. This should give you 3 folders like this: PZMapTools/ <--- you create this folder somewhere Tiles/ TileZed/ WorldEd/ If you get an error about a missing DLL, run the TileZed/vcredist_xNN.exe installer.

That class isn't exposed to Lua; it can't be called from Lua.

I compared the Linux GOG media/lua/ and media/scripts/ files to the Windows Steam ones; they're identical and there aren't any extra or missing files in the Linux one. So if it isn't a mod or something about the server files then I don't know. Do you know if the client can join other servers?

It could be that the client's files aren't updated or contain other files that aren't on the server. Or mods could be different between client and server. I don't know if GOG leaves old files behind in the game directory, the client might need to delete the game directory then reinstall.

Steam co-op hosts can use all the admin commands even when not admin. /grantadmin in console to make a player admin.