[ramikalai]

It is the just Forest haha.

Yeah, having a target number of ants or varying sizes could be interesting but I don't want small ants dying either :'(

Agreed in game time is nice to match up to real life. But, do you really need detailed location data though? You can get rough location/timezone in a much less intrusive way using IP. You could even get timezone just in JS on the client side even. That should be enough to match up time (not sunset sunrise but better than nothing and less input from user)

[SeanAnderson]

Yeah, fair, ants shouldn't die. I will think on it. Maybe they just go low on energy and hibernate. :)

Yeah. All of this code is written in Rust and running in WASM. I found it challenging to interface async JS callbacks with my Rust code. After I spent a bit of time trying to get what I thought the easiest route was to work (geolocation API) and failed on a simple callback, I decided to just throw in the lat/long inputs and see if people liked the feature at all. I agree that the best solution is one where the user doesn't even have to think about this feature

[ramikalai]

Afraid I don't have much in the way of experience with Rust or WASM so can't help there.

Maybe instead of lat/long, you expose a dropdown of popular cities? Again not bulletproof but does make the user's life easier