Thanks! Really good points here, will have to find some time to apply them.

Yeah I moved it over and it got a lot nicer, nice to have this type of thing built in to cargo.

Thanks for the great points.

• Using the BufRead trait sounds like a good improvement!
• Yes, this is a stupid temp thing that I have to fix once I get better errors in place. Which you also had some good ideas on :)
• Good idea, should be helpful
• As mentioned above, this sounds great!
• Yup, left over from the initial CLI application
• Yeah it is there as an example, need to look into how examples are better set up

ah the IO module is left over from the initial CLI calculator. Will have to clean that out at some point.

And the inline server module is also left over from when I was writing everything in the same file first before splitting out.

Good catches! Thanks

I guess that it makes sense. I’ve been doing Go for the past two years.

Neovim here as well. Though I do use LSPs. I write mostly Go in a fairly large code base so “go to definition” is pretty much a must have.

I was considering going without and just using grep like tools, but not yet.

It didn’t feel like I rushed it, maybe I missed some bits in act two, but it still took just over 50 hours.

It took me just over 50 hours

Oh, I am one of only 368 people… I guess that explains why the wife was a bit grumpy

The only times I load a save is if I get wiped, so this first campaign has been interesting to say the least.

The last inn was my first big disaster in a string that has made my first play through quite sad.

Everyone except my party died at that inn, and my party only just survives with less that 5hp between all the characters.

Compared to act one this turned dark really quick.

By default dive rolls are not truly random, check out the “karmic dice” setting under gameplay settings.

It is not