Skip to main content

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

Another idea for making this configurable might be to use eval[]. For example, if you have an expression as a string (which could be a contraption attribute):

expr:"(n-10)/2"

You could then evaluate it under a dictionary of variable bindings:

(x+floor eval[expr ("n" dict grid1.cellvalue)].value) ...
(1 edit)

I'll keep it in mind. Since I'm using it in two different contraptions, I'm thinking a module is better than anything that belongs to one contraption since both contraptions can access it equally?

(Edit: there's even a deck-level script which is probably a simpler solution than a module)