Skip to content

v1.27.1
Compare
Choose a tag to compare
@Lailloken Lailloken released this 25 Jul 09:14
· 1186 commits to main since this release
v1.27.1
a6005fc

New feature: delve-helper

  • categories: experiment, proof-of-concept, UI-testing, coding-practice, fluff

  • description: feature that helps you find hidden delve-passages (it's a HELPER, not a solver, i.e. it's not 1000% accurate and requires basic deduction by the user)

delve-helper.webm

Delve-helper: setup

  • this feature has to be enabled and calibrated in the settings menu

    • open the delve-map (e.g. via Niko) and find a large area with chambers
      image

    • zoom into the delve-map as far as possible (that's also the default), then open the LLK settings menu, go to the delve-helper section, and enable the feature

    • a sample grid will open with which to calibrate the grid size (it's NOT click-through), so you have to get used to moving the map underneath by clicking its side-edges that are not covered

    • align the borders of the chamber-area with the grid and resize it until they match more or less (also use the borders of biomes/tiles to double-check)
      image

    • you can close the grid by pressing ESC

  • this is also where to resize the button with which the feature can be toggled (it's free floating, so it can be dragged and positioned across the screen, just like the alarm and notepad icons)
    delve

    • optionally, you can have this button shown only while you're in the azurite mine (enabling this will scan the client.txt-file generated by the game, which may or may not affect general performance depending on its file-size and your hardware)

Delve-helper: usage

  • this feature can be toggled by clicking its button (right-clicking will reset the grid)

  • important note: you ONLY need to input pathing for sections (squares in the grid) that actually have a node/checkpoint

    • that means: do NOT click sections that only have a path but no node/checkpoint (because the code assumes that every path set by the user has a node/checkpoint and thus includes that in its calculations)

    • PROs: fewer clicks needed, more visibility, faster inputs

    • CONs: you can't feel the weight of your clicks, this feature can't account for path collisions (i.e. whether a path blocks the way to a hidden node/checkpoint) but only with neighboring nodes/checkpoints

  • always make sure to set the pathing correctly (it's sometimes a bit difficult to tell at first glance in which direction paths lead because nodes are not always centered in the sections, and pathing can be quite crooked sometimes)

  • interaction-loop:

    • align the map with the grid so that the hidden node is somewhere around the center

    • set the paths for nodes/checkpoints around the hidden one by clicking the directions next to the center of a section

    • after every (logical) surrounding node/checkpoint has its pathing marked, right-click the center of the hidden node's section/square to mark it as such

    • plausible nodes will be marked green, unlikely/impossible nodes will be marked red

  • integrated QoL: you can click the center of a section to toggle between zero and four paths

    • this means you can mark three-way intersections with two instead of three clicks

Feedback

How to update

Update.webm
Assets 2
Loading