Sharing tiles and Adding passibility information

[GrandmaDeb]

I am assuming that there is no easy way to associate passibility data with a tileset, like in the txt file.


The only thing I can think of is to make a game with dummy files and the passibility set up in that game.


For example, in the modern day tiles...

you could name files "Not_ModernDay_A2.png" etc, stick template files there, and then set passibility for all of the tiles.


Then someone would literally have a plug and play for their Modern Day tiles with passibility.


The problem with this idea is that you would have to rename all files.


But I am not sure if it would be smart to have dummy files with the "real" name.


Thoughts? Better ideas? With the increasing power of directional passibility and lots of counter options, etc, it seems helpful to be able to pass along this kind of data somehow.

 

[Tsukihime]

Instead of dummy files I would just create a project with the tilesets set up and instruct users to go to the project to "look" at the tileset and if they want to use it in their own project, copy the tileset entry into their own database along with the images.


You can even include sample maps in there with the tileset to demonstrate how the tileset is used.


So have real files in a real project. Unless there's a reason why the project itself should contain dummy files.

 

[Sharm]

I'm pretty sure GrandmaDeb's talking about sharing passability setups for tiles that can't be shared legally, like the one's you'd find in the store here. If not then I completely agree with you Tsukihime.


I think the dummy with the similar or same name is a good option. I'm not sure why having them exactly the same name would be a bad thing, since projects get their own folders there shouldn't be a chance of overwriting the real thing, should there?

 

[Shaz]

I'm thinking along somewhat different lines. What's your motive for asking GrandmaDeb? Who would set up this info, and who would it be sent to? What would be the issue with renaming the files (and why would you want to rename them in the first place)?


I'm thinking of something even easier than what you describe, that would not require a project, but I need to understand where you're coming from first.

 

[GrandmaDeb]

I'm thinking along somewhat different lines. What's your motive for asking GrandmaDeb? Who would set up this info, and who would it be sent to? What would be the issue with renaming the files (and why would you want to rename them in the first place)?


I'm thinking of something even easier than what you describe, that would not require a project, but I need to understand where you're coming from first.

There are three situations I am thinking of.


When I teach my kiddos to add Mack tiles to their games, they all have to change the passibilities, and it adds so much complication for them. So I am thinking of tiles which they add which are complete sets which I could distribute to them in a game, already with passibility set, if that is the best way. It would need to be able to port into an existing game, ideally.


Also, the kids import tiles like Celianna's tileset, or other tiles that I don't want to pass along in game form to them **with tiles included** because it just sends them the wrong message. We have an entire presentation on licensing and respecting ownership, and I don't want to mess up what I straightened up, if you see what I mean. But if I had a way to say "here is the passibility for <populat set number one>" so you can download it and add the passibility settings easily, that is what I am looking for.


Finally, I have a bit of a secret project going with multiple tilesets compiled, and I'd like to make it as easy as possible for someone to use it. So if I can have tile passibility to distribute ~apart~ from distributing the tiles, I'd like to be able to do that.


Let me know if I am clear as mud.


To directly answer your questions:


I would be setting them up.


Renaming would just be to avoid anyone accidentally overwriting their original resource file, but having use the same name would be vastly easier for plug and play, so I am of two minds on that one. My kiddos are still learning file handling skills.


Some files would be sent to my students but others would be distributed publicly. (Mack and my Project.)

 

[Sharm]

I'm all for keeping the names the same.  Project folders are separate so unless they're doing something silly like merging folders that have nothing to do with each other the chances of overwriting the tiles is pretty low.