In Update 9.0 we introduce a resource cost and crafting time multiplicator which enables you to easily adjust the gameplay to your preferences, without having to modify files.
The cause and effects explorer was removed in a recent version to be overhauled for a future Update, though not 9.0.
Yeah, definitely set it to No Collaboration. You can select multiple specializations - they are gained at a base rate every day, plus a multiplier (that you can upgrade through food and housing in the game) and that setting changes the base multiplier. If you're only 3 people, you'll need lots of specializations each to fill out the needs of the tech tree. Generally, the games' wiki, https://eco.gamepedia.com/ is a great resource since it explains a lot more than the ingame text.
Please no longer link to gamepedia, we stopped our cooperation with them and the wiki is no longer official nor endorsed by us or worked on by the former wiki admins. We use https://wiki.play.eco now, without ads and recent software. It also allows anyone to edit, without permanently required approval by Wiki-Admins nor with the requirement to register. Registered accounts get patrol rights automatically after a while, just like on Wikipedia.
Not without cheating them in or finding them on another island. That problem is supposed to be fixed in alpha 9. If it ever releases.
Indeed, Update 9.0 allows you to use any seeds for the farming book. The spawn rate of seeds has only been slightly adapted, though, as it's intended for them to be taken care of by farmers with the respective specialty.
While the veins are indeed very big, them being on the surface is a bug that is fixed in newer versions.
Likely caused by an outdated EcoSim.eco file in your Configs directory. Remove the configs directory, repair via Steam and create a new world. You can also use the old one, but it will take several real time days to recover.
The chance is 1 in 1000 when eating Elk Tacos, so i'd rather congratulate you, if this was Diablo III you'd got a nice legendary. *g*
All you need to do is actually relog, then it's gone.