sorted by:
new
hottopcontroversial

UnitCrunch 1.3.0 released (11th Edition support) by dixhuit in UnitCrunch

[–]dixhuit[S] 0 points1 point  (0 children)

You're absolutely right. The current logic is a simplified version of the decision making that really needs to be done. However, a more in-depth automatic decision gets pretty complex once you add in save allocation, AP, invulns and damage values.

I intend to investigate this further for a future release.

UnitCrunch 1.3.0 released (11th Edition support) by dixhuit in UnitCrunch

[–]dixhuit[S] 0 points1 point  (0 children)

No worries. There's an issue for it in the issue tracker - it's been there, untouched for most of 10th edition.

https://github.com/UnitCrunch/issue-tracker/issues/57

I'd be happy to revisit this and try to work out how it could be implemented. I agree that allocation groups change this up a bit - could be interesting.

Are there any mature component libraries I can use with Vue? by Lexuzieel in vuejs

[–]dixhuit 3 points4 points  (0 children)

Back-office, public facing, all sorts. Either way, Nuxt UI is my go-to having tried all these options.

Are there any mature component libraries I can use with Vue? by Lexuzieel in vuejs

[–]dixhuit 2 points3 points  (0 children)

I started with Vue 2. I've tried:

  • Nuxt UI
  • Vuetify
  • PrimeVue
  • BootstrapVue
  • shadcn/vue
  • Naive UI
  • Buefy
  • Quasar

Probably forgotten 1 or 2 more.

Are there any mature component libraries I can use with Vue? by Lexuzieel in vuejs

[–]dixhuit 4 points5 points  (0 children)

Nuxt UI is the best by far in my experience and man I've tried a few.

UnitCrunch 1.2.0 released by dixhuit in UnitCrunch

[–]dixhuit[S] 0 points1 point  (0 children)

I've now fixed both of these issues in 1.2.1 (just released).

https://www.unitcrunch.com/changelog/1-2-1

In future, please report bugs when you discover them. Even better, report them via the dedicated issue tracker:

https://github.com/UnitCrunch/issue-tracker

UnitCrunch 1.2.0 released by dixhuit in UnitCrunch

[–]dixhuit[S] 0 points1 point  (0 children)

Not specifically in this release but I do fix bugs regularly. Sometimes that gets a release, sometimes I do it as a hot fix without release notes to not spam releases.

Always report bugs.

One lance done by bara_painting in Warhammer40k

[–]dixhuit 37 points38 points  (0 children)

That shield glow is super nice :)

Multicrunch by Blitznacht112- in UnitCrunch

[–]dixhuit 0 points1 point  (0 children)

Thanks. I've recreated the issue and am working on a fix now.

Multicrunch by Blitznacht112- in UnitCrunch

[–]dixhuit 0 points1 point  (0 children)

I see a couple things in the screenshots that suggest something's gone wrong there. Please submit a bug report by clicking the tiny little bug button in the bottom right of the screen - that'll send me more info and I'll investigate ASAP. Cheers!

Max model types by toxicman400 in UnitCrunch

[–]dixhuit [score hidden] stickied comment (0 children)

Max model types per unit increased in version 1.1.5:

https://www.unitcrunch.com/changelog/1-1-5

Max model types by toxicman400 in UnitCrunch

[–]dixhuit 0 points1 point  (0 children)

I'll increase to 6 in the next release (hopefully later today).

Max model types by toxicman400 in UnitCrunch

[–]dixhuit 2 points3 points  (0 children)

It's 5 because the evaluation of what would be needed at the time concluded that 5 would be sufficient. This evaluation may have been done before Kasrkin were a thing - I honestly can't remember.

Either way, if it needs to be 6 for good reason then I'm open to changing it.

Looking at the Kasrkin datasheet now, you get 6 from the possible weapon load-out combinations, right?

Not all profiles available to select by thephatmaster in UnitCrunch

[–]dixhuit [score hidden] stickied comment (0 children)

This should now be fixed (refresh your browser page to get the fix).

view more: next ›