Custom Object sub folders

Yes, this is a tutorial on how to place custom objects in a sub folder. For example, you could have a separate folder for your foreground custom objects, a folder for your critter objects, etc. All these folders must still go in the Custom Objects folder, though. Here's how it works: When KS retrieves the object name, it takes the string after "image=". It then tags than onto the application path > Custom Objects. Assume your KS folder is at C:\Users\Pineapple\Games\Nifflas\KS\. It will take that pathname and add "Custom Objects\" on the end to find the custom objects folder thus: C:\Users\Pineapple\Games\Nifflas\KS\Custom Objects\. Finally, it takes the string after "image=" and places it on the end. If you put image=flower.png in the ini, it will put flower.png on the end to get C:\Users\Pineapple\Games\Nifflas\KS\Custom Objects\flower.png. Surely now you see what happens. If you add a sub folder called wildlife in the Custom Objects folder, and put flower.png in that, you simply tell the game to look for "image=wildlife\flower.png," thereby producing C:\Users\Pineapple\Games\Nifflas\KS\Custom Objects\wildlife\flower.png! Tadaa!

---

In summary:
Create sub folder "example" and put the object in with name "ex.png" Put this code in the ini:
[Custom Object #]
image=example\ex.pngFurther examples can be found in my level here.

Wow. That its interesing.

You can also use the parent directory - i.e. '..' - in the image path, as in '..\..\otherlevel\Custom Objects\CO1.png'; it's mostly useless, but you could share Custom Objects between levels like that if you wanted.

You can also use the parent directory - i.e. '..' - in the image path, as in '..\..\otherlevel\Custom Objects\CO1.png'; it's mostly useless, but you could share Custom Objects between levels like that if you wanted.

I would strongly avoid doing this (use CO's from other worlds).

I'm failry sure that by doing so, the custom object will not be packed into your knytt.bin file, and it will break your level if someone else doesn't have this other level, or have a modified(corrputed?) version of it.

CO's are not big files, so copying them is easy enough. Besides, would you make another level dependent of a CO, it means you can never alter it again, or it will be altered in both.

You can also use the parent directory - i.e. '..' - in the image path, as in '..\..\otherlevel\Custom Objects\CO1.png'; it's mostly useless, but you could share Custom Objects between levels like that if you wanted.

I was thinking about that, but I couldn't find a good reason to use it (until now)

You can do an automatic check if someone else has a level with custom objects in it. For example "..\..\mr person - blah\Custom Objects\whatever.png" and then make a little arrow or something pointing out an otherwise nearly impossible secret area to find. In that secret area you could say, "Hey! You have mr person's level! That makes you cool."

Cool idea! Very 'Psycho Mantis'-esque.