Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Miiza

2
Posts
A member registered Aug 04, 2017

Recent community posts

Why do you need to catch an exception if it never occurs?

If you make the robot do:

Repeat forever

      Repeat until hand is empty

            find nearby tree

            go to tree

            use tool

      end repeat

      go to storage for pole

      go to workbench designed to make an axe

      go to storage for plank

      go to workbench designed to make an axe

      pick up axe

end repeat

It will never throw any error, since it will create its own axe as soon as the one its holding breaks. The setup above is also able to restart without the robot getting stuck on making a new axe, since it checks its hands first.

I don't know if it's a duplicate bug:

When you send a robot to recycle an item, the robot still think that it has that item in the inventory, although the visual effect and ability of the item disappeared, and the robot cannot pick up any other item - I tried to make an infinite loop of having a robot recycle a bucket whenever he milks a cow, and then make the robot make a new bucket from the resources received by the recycler, this loop would milk the cows without ever filling up the milk storage.

If you take the "non-existing" bucket from the robot you will get the bucket, and if you place it down anywhere you cannot pick it up anymore.

You cannot do anything with this non-existing bucket.