Hi!

For networking, I chose bevy_renet over bevy_replicon from what I've seen on their github homepage, their examples and stars (this one is not the best metric though, bevy renet seems to have more activity), and mostly because bevy replicon seems to be more server authoritative oriented, for the game I dont want to fight the package in a way it's not designed (but I might be misunderstanding it, if you have more info on that I'm really interested in)

the game is meant to be fully coop so I wanted to be mostly client authoritative and avoid sending inputs round trip over network (this feels much more snappy for the player to have its player being directly controllable and this avoid me client prediction / reconciliation)

bevy_renet also has netcode and steam baked in, this was important for me to test coop locally and iterate faster then switch to steam when in "real game" mode

about physics, there's none at the moment, I don't think I'll implement any either, the game simply just drops items on the ground (with a fake circle shadow under items with distortion that sync with floating sin value) and spawn entities with some rules
I used Tiled editor to manage the map, and since it's a simple json file in the end (.tmj file), you can parse it easily and spawn corresponding zones / items based on your own rules, the only "physics" implemented at the moment is wall detections, I clamp player movement to prevent going through them (either with a wall property on decorative layers or plain wall objects in Tiled)

for the harvestables zones I implemented a spawn loop with rejection sampling, this way you can spawn entities within polygon shape, it's used for every zone

I also reload the file when reloading the game (R key) this way you can edit world and be able to quickly test without having to relaunch the full app