Looks really cool!
I think I noticed a typo in the docs here: https://flaque.github.io/merchant.js/#totalof
Should "Map({GOLD -2});" have a colon between the key and value?
Show HN: Merchant.js, a state framework for creating idle games
11–20 of 31 posts
Re: Show HN: Merchant.js, a state framework for creating idle games
#12Why Map is used instead of plain object {} ? And why it's Map and not new Map ?
Because their Map type is not the JavaScript Map type but immutable.Map.
Re: Show HN: Merchant.js, a state framework for creating idle games
#13This is great for your phone By the way, follow my website to get tips about https://www.gmaillogin.help/
Re: Show HN: Merchant.js, a state framework for creating idle games
#14I've recently been playing a fascinatingly complex mobile incremental/idle game called Almost a Hero [0] by Bee Square Games, and as a case study in game design, it's rather fascinating to think about how the developers must have implemented the game logic to result in the reliable behavior the game exhibits. While OP's framework is well-suited to an online idle game, in which you can count on a constant thread modif…
Not sure what your point is. You think it should be possible to run the simulation at increased speed?
Re: Show HN: Merchant.js, a state framework for creating idle games
#15Looks cool! Alternatively I found that Vue.js rather than React makes it really simple to handle these types of games (though you no longer have the immutability and history which can be useful for persistence). At last Ludum Dare, I quickly hacked one of those games (look at the source to see how compact it can be) http://aqua.gistnoesis.net/ld39.html .
Re: Show HN: Merchant.js, a state framework for creating idle games
#16That paperclip game is insanely addictive!
Re: Show HN: Merchant.js, a state framework for creating idle games
#17I've recently been playing a fascinatingly complex mobile incremental/idle game called Almost a Hero [0] by Bee Square Games, and as a case study in game design, it's rather fascinating to think about how the developers must have implemented the game logic to result in the reliable behavior the game exhibits. While OP's framework is well-suited to an online idle game, in which you can count on a constant thread modif…
Not sure what your point is. You think it should be possible to run the simulation at increased speed?
I think the point is that they'd like to be able to simulate things that happen while the player is not on the page. So, save the state somewhere with a timestamp, and when re-hydrating it compute things that would have happened while they were gone.
Re: Show HN: Merchant.js, a state framework for creating idle games
#18I like immutable objects. But my worry is it will lead to lots of small objects being created just to get destroyed right away, putting lots of pressure on GC. I wonder if this is a known issue in the immutable js community.
Re: Show HN: Merchant.js, a state framework for creating idle games
#19The live example is broken right now
Re: Show HN: Merchant.js, a state framework for creating idle games
#20I like immutable objects. But my worry is it will lead to lots of small objects being created just to get destroyed right away, putting lots of pressure on GC. I wonder if this is a known issue in the immutable js community.
When you insert into an immutablejs collection, a copy is not made. It's reusing a reference to the old object. That means iteration is a bit slower while insertion and similar operations is faster, which is an acceptable tradeoff