TheoTown

True :) Hello Reac Can make Fun conditions can <..> separated fun attribute? For example {Hi im fun template Action 👉} {Hi im seperate fun 1 condition if 👉✅ my result 🌝} {Hi im seperate fun 2 condition if 👉✅ my result 🌚} Or {Hi im fun template i remove building if ✅} {Hi im separate fun 1 if buildi...

... Fix missing car owner could cause city loading issue Change GUI canvas behavior so that the canvas draw function gets an unpadded drawing rect as parameter (before the drawing was dependent on the canvas' padding which is not intended) Update translations

... "width":1,"height":1,"auto join":true, "on built fun":[{ "actions":[ {"type":"rect","x":1,"y":0,"w":9,"h":1,"inner":[{"type":"build","id":"$road00"}]}, ...

... count","id":"$testxlight","min":0,"max":50},{"type":"rect","x":-6,"y":-6,"w":13,"h":13,"min":1,"max":169,"inner":[{"type":"road","level":0}]}]}, ...

Yes.

Wait, so it make 4x4 rectangle, inner means the space inside it, actions are what it will do inside it? Is this a correct way of putting it?

You could also use a 3x3 building that when built removes itself and builds the 9 tiles in the pattern shown.

I agree, this could have been a useful feature, but there are a lot of potential features like this one and it's hard to add each one of them manually. Therefore I would recommend to use :lua: nowadays. This might look like local function buildRect(draft, x, y, width, height, stepx, stepy) stepx = s...

wut?

True

Shouldnt this be in the "fun attribute" section?

... in this context I'm talking about something that is able to detect a target and move towards it, eventually reaching said target. Using fun and rect functionality, we can make a basic, but versatile pathfinding system. First of all, here is the json of the target: [ { "drawground":true, ...

... "height":4, "width":4, "fun":[{ "action":[ {"type":"remove"}, {"type":"rect","h":4,"w":4, "inner":[{"type":"build","id":"$zoneindustrial_lvl2"}]}, ...

... When loading "$blank_coalmine00": May not load action from [{"type":"remove"},{"type":"rect","h":4,"w":4,"inner":[{"type":"build","id":"$zoneindustrial_lvl2"}]},{"type":"build","id":"$coalmine00"}] ...

... When loading "$blank_coalmine00": May not load action from [{"type":"remove"},{"type":"rect","h":4,"w":4,"inner":[{"type":"build","id":"$zoneindustrial_lvl2"}]},{"type":"build","id":"$coalmine00"}] ...

I don't think this is needed, it's easy enough to do with "build".

The code: Should have this result:

CommanderABab wrote: ↑

31 Aug 2018, 02:57

Code: Select all

"destroyable":false

doesn't help in zoned areas to prevent zoned buildings from building atop the canals, but is still a good idea to prevent them being destroyed by disasters.

#rect

I added that code in new update, thanks

... by disasters. So, using this technology , you could use the "on built fun" with part1 (temporary) id of each section using "rect","action","remove" as in the last example which would remove the zone ( not including the build as in the example ), then ...