Which will behave like that

let settings = await prettyConfig('rollup', { configFiles })

if (!settings) {
  settings = await prettyConfig('rolldown', { configFiles })
}
console.log(settings)

instead of above we can hide it to look like that

const settings = await prettyConfig(['rollup', 'rolldown'], { configFiles })

if (!settings) {
  console.log('no config file

In particular, when a rare enough event occurs near the start of your game, consider adding a tutorial hint explaining it. For events that occur very often, if the message is long, it should instead be restricted to the first (few) occurrences. Depending on the case, this may or not may be easy to do, so may require a separate ticket (please open, as needed).

Grep for MsgTutorialHint to see h

Would be very effective against regenerating foes (then we can add and/or improve foes that are very weak, but regenerate and possibly avoid melee to be safe from big hits that they can't regenerate against). Can be a throwing weapon, because swapping it in and out as a melee weapon worth it only for regenerating foes could be too tiring.

Edit: let's make sure there is proper feedback on hits

Check out this simple guide.

• Create a fork (click on fork, top right)
• Edit README.md
• Add your name and your Github URL as mentioned in the README.md
• Create a pull request.