The issue has been closed

Some object types files from older versions don't import correctly? #3472

YourBuddyBill posted onGitHub

Describe the bug Importing an Object (now Class) Types Editor file that worked fine in 1.8.6 only imports the names in 1.9, none of the custom properties themselves appear to be importing correctly.

To Reproduce Steps to reproduce the behavior:

Create a project
Import the attached object types file
Open Custom Types Editor
Select a custom type
See that there's no properties
Get confused

Expected behavior I expected the object types to have their custom properties imported as they were defined in the file, and each be individually visible in that big empty space, and for them to then be usable to reference in maps and stuff.

Media Importing the attached object_types.json file in 1.8.6: tiled_1_8_6_objecttypes Importing that same file in 1.9.1: tiled_1_9_1_customtypes

Here's the file in question (Github doesn't let me upload json files, so rename this file from .txt to .json and try it) object_types.txt

Specifications:

OS: Windows 10
Tiled Version: 1.9.1 (worked fine in 1.8.6)

Ah, this isn't really a bug but unfortunately quite bad usability. The JSON format changed in Tiled 1.9, and when importing types, it expects you to select the right file type:

Importing of "Object Types JSON" files does not work when you select "Custom Types files" (the default).

I will have a look at auto-detecting the old format in the Import dialog, but I'm afraid the distinction will remain relevant for the Export dialog, since the extension is the same.

posted by bjorn over 2 years ago

Fund this Issue

$0.00

Funded

Pull requests

Some object types files from older versions don't import correctly? #3472

Company

Community

Support

Connect