Layer data base64

I “forgot” it because I couldn’t find the value for it (0x10000000) at the time (github really needs a grepping feature). I’ll edit it into the post above. Thanks for finding it!

The hassle is having to clone the whole repo and locally store all these files I don’t need just to make a PR that doesn’t touch any of them. For something like a resources repository, that just doesn’t make sense. Plus, a lot of people using TIled and writing scripts for it don’t even use git at all, and wouldn’t know how to do any of this. It’s also a hassle to find specific files on Github if you don’t know the filename, so as someone looking for resources, I probably wouldn’t find them there. Browsing the repo is also annoying since there are only file names to guide you.

The GB Studio Community Assets repo is set up a little better with directories for different types of resources and credits in the readmes, but it’s also a bit annoying to browse and search, and it’s actually mainly useful for its list of externally hosted resources, which is more convenient to scroll through and search.

Aseprite has a Scripts section on their forum where people can post their scripts. This isn’t ideal since while it’s searchable, the forum search isn’t specialised for searching code and descriptions and will turn up a lot of false positives, and because there’s always going to be a lot of noise in the form of misposts and replies, but it’s more convenient than a git repo.

The ideal solution would probably be some sort of Resources section on the site where people can submit their files, with a description and a category (e.g. “Custom Formats”, maybe with Importer/Exporter checkboxes since those can vary, and Python/JS options just in case the user cares). That would be a lot of work to implement and moderate though, so I think a forum section would probably be the simplest option. A forum section could be made cleaner by including subsections or requiring some special notation in the topic name, e.g “[Custom Format Exporter] CSV with Flip Flags”.

Edit: If you do go with a forum section, do not make a big sticky like the Aseprite forum has. Though it is more compact than a list of topics, it’s nearly impossible to search on Discourse, because Discouse hijacks ctrl+F and only shows results as posts, making it impossible to search a large post.

1 Like

Actually it’s very easy to add a file to a git repository on GitHub. There’s an “Add File” button at the top, and then you choose either “Create new file” and paste in its contents, or “Upload files” to upload some files. No need to check out the repository at all.

I agree a lot could be done to make finding extensions easier. The tiled-extensions repository is meant to be a start, but it currently doesn’t have enough visibility and there could be a listing of the currently available examples (maybe just the README.md) because just browsing the files is indeed not ideal.

For sure it would be nice to provide an easy way to install and update various extensions, but it’s quite a big project so I’ve decided to wait with that until there is a more clear need. I kind of expect most extensions to be rather project-specific (since those that aren’t could be written as part of Tiled itself), and such extensions would generally be checked into the project’s git repository.

Oh, TIL :D

I think having everything listed/described in the readme would be great. It’s an extra step, however, and it means adding an example would no longer be as simple as using Add File, as the readme would need to be amended. Though I suppose a prospective uploader could add their info in a comment on the change for you to copy+paste.

I agree that most scripts are likely to be project-specific and there’s no need for a comprehensive directory. I think exporters/importers for various engine-specific formats are the most general kind of extensions that would be needed, and they’re perhaps not something you’d want to clutter the core program with.
On a related note, I think code examples included in the documentation are also more helpful than a repo of examples ;D

Right, though after adding a file GitHub will have created a fork with a branch for the pull request, and editing the README.md can then be done by just clicking towards that branch, the README.md and then click the “Edit this file” icon to make another change for the pull request.

While there should definitely be more examples in the documentation, the repository is really to provide some larger scripts that would be unwieldy to fit into the manual.

1 Like