Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

The Alterhistorian's Conquest

Create the elixir of immortality in a world where concepts can be distilled. · By Dystopia-user181

Small bug

A topic by bogusbishop created Aug 09, 2022 Views: 477 Replies: 3
Viewing posts 1 to 3

There is a small bug with the InputMergers: You can connect its output to its own inputs which will mess things up if you put two different materials into the InputMerger.

Developer

Well it always did "mess things up" if you put two different materials into the input merger anyway, I explicitly enabled that behaviour to allow people to put two fuels, like coal and wood in the same furnace. Even if you connect its output to itself nothing bad happens. I don't think it's that big of a deal that I need to explicitly disable it- In fact I'm looking for possibilities that this could be intentionally used as a solution later on.

Yes, I found it very useful. Warning, the following text contains many SPOILERS!

For example for fuel. I like that when you have multiple furnaces and don't know how to distribute wood and coal between them, you can simple throw all wood and coal into one InputMerger and from there distribute to all furnaces. If you want to add coal to an EssencePurifier, you could loop the InputMerger, because if the Merger would be 'stuck' at wood for a while, waiting to distribute it, a looped Merger automatically continuously shuffles itself so it reaches coal much quicker.

You also can set the output of EssencePurifiers to a looped InputMerger, and from there anywhere you need: fire for the advanced furnaces (I forgot the name and can't loop it up as I just finished the game), vitriol for the Transmuter or essence for upgrades. Once the output of the InputMerger hits something that can't be used (i. e. something full or essence), it would stop distributing elements, but if you loop it to itself, it shuffles itself and quickly will reach something usable in its output again. This way when you want to change an EssencePurifier, you only have to change its inputs as its output is automatically distributed.

Also if you want to make a lot of the last thing of a Transmuter (was it quicksilver? I don't remember), you could loop a Transmuter to itself, but eventually it will stop because it can't feed quicksilver to itself, but if you connect it to a looped InputMerger (which itself is connected to the input of the Transmuter), this will filter the quicksilver but continue to feed the Transmuter stuff it can process.

Yeah that was pretty helpful, thank you