Creatures Caves

Bifrost wrote:
Holy Shee it works!

There are still a few quirks that needs tuning - a couple of weird gaps, tiny holes and weird nooks, but that should be fixable from the room map. I'm noticing a few areas made too thin and things like that. But it works!

I think those are problems with the algorithm actually, I made it ignore rooms of a certain thinness to avoid some areas being made too thin, but it left the areas that are too thin and put in weird gaps. *shrug* On my todo list.

Bifrost wrote:
What can I do now to inject this world into the Kreatures engine?

Well it'll be weird, I'm trying to fix the scaling now, in the version you have everything will be too big, in my current build everything's the right size but half of it went off screen for some reason.

Okay, let me explain the bootstrap:
Each folder will represents a world when the world switcher is made, aside from common, scripts can load any script in their own folder or in common, but not in other world's folders. This means that if a script is in common then you have permission to use it in your metaroom.

Currently it's hard coded to start by loading every file in Burrows and executing main(), so you need to modify main()

So open Bootstrap/Burrows/main.jc and look for createBurrows(), getBackground is loading a background file into the engine and returning an anchor, the anchor it returns is a handle for the metaroom's coordinate system.

So save the regenesis.bak in the Backgrounds folder, and change "burrows" to "regenesis"

On the next line you can see buro.connect(buro, Direction::Left, 0). This is telling the engine to connect the left side of the coordinate system 'buro' to the right side of the coordinate system 'buro' with a vertical offset of 0. So you don't have to change anything to get the world wrap there.

Next notice in main() we have buroGravity = new PhysicalZone(burro, null); That's saying to create a physical zone that occupies the entirety of the coordinate system 'buro'. the null isn't important.

Above that you'll see that I've created a variable PhysicalZone buroGravity. That has to be declared outside of a function so the gravity doesn't get deleted when the function exits. This is true of all objects except for backgrounds and GameObjects.

Following line you see burroGravity.acceleration = { 0, 256} This is saying to apply a Y acceleration of 256 pixels per second to whatever's in the physical zone every tick.

I'm sure by this point you've noticed the code to add elevators. Yes adapting objects from one metaroom to another is really that easy in the Kreatures engine, so if you want you can start putting in placeholder objects to say where things should go when they get programmed.

Bifrost wrote:
About cutouts and foregrounds, are these supposed to be made in one image now? Like, I can "extract" them from the original background image, into separate .pngs, one for the parts I want affected by lighting, and one for the parts I don't want affected by the lighting, and just "replace" them onto the map?

Yes, I found adding overlays manually far too tedious.