Glint Spotter

Glint Spotter

Puts a map marker on the thing you are looking at with Blinding Flash or a button press

A glint goes off half a kilometre away while you are flying, and by the time you land, you have lost which ridge it was on. Look at it with Blinding Flash, and it is on your map.

How it works

There are two ways to place a pin, built for different moments.

Blinding Flash marks glints for you. Use the flash, put a glint on the crosshair and hold it there for about a second. The pin lands where the object actually stands, and the controller buzzes to tell you it took, since the map is not open at that moment. Distance does not matter: a glint six hundred metres away marks as easily as one at twenty. The aim is forgiving on purpose, because nobody holds a crosshair still in the air. The flash shows glints through hills, and the mod marks them there too. A glint you have already looted stays unmarked, because the mod reads which ones your save has down as taken.

A button marks anything. Right bumper, left bumper and A together on a controller, or F9 on the keyboard, pins whatever is under the crosshair. Ruins, camps, ore veins, bridges, shops, a dungeon mouth on the far side of a valley. The mod reads the game's own level data, so most things worth walking to are in it, and there is no range cap. If you can see it, you can pin it. This trigger is precise on purpose: it fires the instant you press, so it expects you to be pointing at the thing.

Removing a pin

Open the map and put the cursor on a pin. The prompt at the bottom changes from Marker to Remove Marker, the same as it does over a marker you placed by hand. Press it and the pin is gone. There is no extra key and nothing to learn, because the mod's pins are entries in the game's own marker list and the game treats them like its own.

One press of Blinding Flash marks a thing once, so taking a pin off while the flash is still lit does not fetch it straight back. Use the flash again and the same glint can be marked again, because pressing it again is you asking.

Where the pins are kept

Not in your save file. The mod keeps its own list in GlintSpotter.pins beside the plugin and puts the pins back whenever a world loads, so they survive a quit and relaunch, and they survive loading a save from inside the game. Removing a pin on the map takes it out of the file as well.

Because nothing goes into your save, uninstalling leaves no trace and there is no reason to back anything up before trying the mod. The file is plain text with one pin per line, so you can read it, edit it, or delete it to clear every pin at once.

Pins belong to the save you were in when you dropped them. The mod watches which save file the game opens, so a second character has its own pins and never sees the first one's. Saving into a slot you have never used before takes that save's pins along with it, which matters because the game makes a new slot every time you save by hand. Each save is a group in the file, so you can clear one playthrough's pins by deleting its group and leave the rest alone.

Installing

Glint Spotter needs Ultimate ASI Loader and does nothing without it. Its winmm.dll goes in the game's bin64 folder, the one CrimsonDesert.exe is in.

With the game closed, copy GlintSpotter.asi into bin64 beside it. The mod writes GlintSpotter.ini on its first run with every setting explained, and leaves one you already have alone. Mod managers can take the DMM archive, which holds the plugin by itself.

Start the game and load a save. The pad pulses twice when the mod is ready. That's a few seconds after the world appears, once the game has finished listing its glints.

Settings

Everything is in GlintSpotter.ini and every setting has a comment. These are the ones worth changing.

Chord is the controller bind, written as button names joined with a plus: A B X Y LB RB LS RS Up Down Left Right Back Start. Key is the keyboard bind, also a name: F1 to F24, a letter, a digit, Insert, Delete, Home, End, PageUp, PageDown, Pause, ScrollLock or Numpad0 to Numpad9. F9 is the default because the game binds nothing to it. The log prints both binds back in words at startup, so a typo shows up straight away.

A DualSense or DualShock 4 needs no Steam Input: the mod reads it directly, so the game keeps its PlayStation button pictures. The names map by po