I’d like to see opposite: export to grimtools. Last grimtools version also have devotion path/build order, but have not planner function that highlight posssible variants, that I mainly uses planner for.
just a little wish: please spent the tool a symbol which is shown as Browsertab-symbol.
Yep, your “EDIT” has it correct. This is a little tricky to understand, but the problem here is the selection of Scales of Ulacana which requires 8 Order/yellow and is not “self sustaining” (it only gives 2 order if you complete it).
Dryad costs 5 points and gives only 3 Order. Lion is only 3 stars for the same 3 order.
This might be easier to see if you deselect Lion and the Scales and try to build up from there.
If you pick Dryad and get 3 order for its 5 points you end up here: Grim Dawn Devotion Planner
You have 7 order, and have used 49 points (so 6 remaining).
Scales is costs 6 points but requires 8 Order, so you can add the Order/Yellow crossroads to get to 8 and select a subset of the stars in Scales, but you would need 56 points to select the entire constellation and get its 2 Order points so you could deselect the yellow crossroads.
I normally find when I hit these situations that deselecting the constellation whose requirements I haven’t satisfied yet (and that’s causing the extra points to be reserved on the bar in brown) and building up to it helps me figure it out.
1 Like
This would be really cool. Unfortunately, Grim Tools doesn’t have any APIs that it makes public that lets builds be created.
I was able to figure out how to get the devotions out of an existing build, that was relatively easy (though it’s a bit fragile as if anything about how the grimtools site works, it’ll break).
I’ll do some investigation into this. I do agree it would be useful.
1 Like
Making sure I’m understanding, this is asking about adding a “favicon” that is specific to the grim devotions site so that it doesn’t have a generic icon in your browser’s tabs?
Let me see what I can come up with.
2 Likes
Added the crossroads constellation as the favicon, it’s a little small, but not much you can do at that icon size:
2 Likes
thats what i mean 
2 Likes
Thanks, I just recently noticed that you can use the tooltip in the NEED section for exactly that. Awesome!
That wasn’t there before, I just added that to help me understand it when trying to answer your question :).
2 Likes
Full round-trip of grimtools builds to the devotion picker is now implemented. It was a little easier than I feared. I still consider this experimental and fragile because grimtools doesn’t have a published contract, so if anything changes in it, this could break.
As an example, if I have this build in grimtools: Infiltrator, Level 100 (GD 1.2.1.6) - Grim Dawn Build Calculator
I can import that into my app using the grimtools import on the right, which brings the build’s picked devotions into Grim Dawn Devotions: Grim Dawn Devotion Planner
If I make a change to another valid build (it has to be a valid build with everything supported as grimtools does not support partial builds like my tool does), I can press the export button, and it’ll update the link to a new build on grimtools with all items/class abilities/etc picked, but updated devotions.
Here I’ve removed Hawk and Swapped in Scholar’s Light, which makes the “export” button available on the right.
Pressing that makes a new grimtools build with everything the same except the devotions: Infiltrator, Level 100 (GD 1.3.0.7) - Grim Dawn Build Calculator
One thing to be aware of is that grimtool’s builds are immutable. so when we export back, it creates a new build/url with the changes. It does not update the old url’s devotions.
Also, my tool does not have support for picking abilities associated with celestial powers, so if a new constellation with a celestial power is picked, that will be blank on the new grimtools build. Constellations that were selected remain.
1 Like
Bummer. Looks like Dammit was unhappy with the new feature to import/export builds and has forbidden my app’s user agent string. This now returns a 403 FORBIDDEN:
curl -s -L -o /dev/null -w '%{http_code}\n' \
-A "grimdawn-devotions-import/1.0 (+https://github.com/tednaleid/grimdawn-devotions)" \
"https://www.grimtools.com/calc/qNYgbjeV"
403
I could work around it with a different (untrue) user agent string, but this was an unpublished API and I’m not trying to hack anything. Which is why I sent an honest user agent saying the request was coming from my grimdawn devotions app.
I’m going to remove the import/exports functionality from the UI.
2 Likes
Bummer indeed, I used this feature all the time to import my builds into GT and then into Devo Picker to tweak the devotions.
Maybe you could implement a feature that reads the devotions directly from the player.gdc file?
1 Like
Hi @tednaleid, thanks for this tool!
I would like to understand how the build order is being defined, because it is the same no matter what order I actually use with the tool, and I think it’s not really optimized. Take a look at this specific case:
- Hound
- Crossroads (SE)
- Wolverine
- Eel
- Messenger of War
- Empty Throne
- Sailor’s Guide
- Vire, the Stone Matron
- Rat
- Lion
- Crane
- Obelisk of Menhir
- Lizard
Your tool will set Vire for the very last points, but a much shorter, and with more usefulness in game, route is:
- Crossroads (N)
- Hound
- Crossroads (SE)
- Wolverine
- Eel
- Messenger of War
- Empty Throne
- Sailor’s Guide
- Vire, the Stone Matron
- Rat
- Crossroads (NE)
- Lion
- Refund Crossroads (NE)
- Crane
- Obelisk of Menhir
- Lizard
- Refund Crossroads (N)
Loading a character file wouldn’t be too hard. Do you think it’s something you’d use? It feels like it’s quicker to just pick the devotions because it can be done a constellation at a time. I’m open to it if people would use it.
I would use it for sure. The alternative would be starting a game session with the character, opening the devo screen and awkwardly scrolling around to see which devotions are selected (I hate that you can’t even zoom out), then select them in GDDP. That’s slower than just importing the data, even with the extra step of loading the data into GT and generating a link first, like I used to do.
But that’s just me, dunno how other people see it, if they even care about this. It’s not a biggie though, just a small QoL that would be nice to have. No worries if you have other priorities.
The build order is there mostly to prove that it’s a viable build. It really hasn’t been optimized much. There are thousands and thousands of possible paths for most builds. The underlying algorithm puts T3 constellations last because they give no affinity to the build.
1 Like
This is my new favorite Devotion calculator!
1 Like
What does “close Grim Dawn first, or the file will be locked” mean? Loading a player.gdc while playing that character works fine for me. Or is the tool able to write the devotions to the player.gdc as well, and that only works when GD is closed?
oh! I hadn’t actually tried this specific thing with a running instance. Other grimdawn tools (like extracting assets) failed when the game was running because the grim dawn app had them locked. If it works, I can remove that text (and it can be ignored till I do that)
I did think about actually allowing it to create an updated save file with new devotions picked, but there are edge cases to that, and would definitely not work if the game is still being played. For now it’s read-only.