Christian Stewart paralin

Patch 6169 - Rem Release Update

Date: January 26, 2026 Client Version: 6164 → 6169 Source Revision: 10398953 → 10400989

New Hero: Rem

Rem (hero_familiar) is now fully playable with complete ability data and weapon stats.

Rem Support Enabler Build

Patch: January 2026 (Hero Release) Playstyle: Spirit Support / Carry Enabler Damage Type: Spirit (hybrid support/damage)

Hero Overview

Stat	Value

Haze

Overview

Haze is a stealth assassin who excels at isolating and eliminating targets from the shadows. Her kit revolves around invisibility, crowd control, and devastating close-range damage. She uses Sleep Dagger to disable enemies before unloading her rapid-fire weapons, and her Bullet Dance ultimate allows her to melt multiple foes while evading return fire.

Base Stats

Vitality

Health: 700 (+33/boon)

git clone https://github.com/ggml-org/llama.cpp
cd llama.cpp
HIPCXX="$(hipconfig -l)/clang" HIP_PATH="$(hipconfig -R)" \
    cmake -S . -B build -DGGML_HIP=ON -DAMDGPU_TARGETS=gfx1101 -DCMAKE_BUILD_TYPE=Release -DLLAMA_CURL=ON \
    && cmake --build build --config Release -- -j 21

# this is important

This document contains my simplified understanding of how this works.

it is by no means an exhaustive explanation and is meant to get the "vibe" of what's happening while glossing over implementation detail.

Ask deepseek R1 to think about something.
It thinks about it for a long time, spending $$$ on compute.
It eventually comes to a conclusion.
Take the question + the conclusion and generate a "thought trace" which is the "correct" version or the "shortest version" of the "thought process"

UI Component State Persistence Design

See a prototype: https://github.com/paralin/jotai-tree-state-prototype

Background

Modern web applications often contain complex UI hierarchies with stateful components like counters, panels, and nested layouts. Each component maintains its own state but needs to persist across page reloads and browser sessions. Additionally, these components may be dynamically nested within each other, creating a hierarchical

	[user]
	# email = my@email.com
	# name = Wheatley
	[commit]
	committerDateIsAuthorDate = true
	# gpgsign = 1
	[push]
	default = simple
	[format]
	signOff = true

	// find-importers.js
	const fs = require('fs/promises');

	/**
	* Finds and lists all modules that import any module whose path contains a specific substring.
	*
	* @param {string} metafilePath - Path to the esbuild meta.json file.
	* @param {string} targetSubstring - The substring to match in the imported paths (e.g., "/multiformats/dist").
	*/
	async function findImporters(metafilePath, targetSubstring) {

	import getWasmInterface from './get_wasm_interface.js'

	// usage
	const bytes = await fetch('mine.wasm').then(r => r.arrayBuffer())
	const m = await WebAssembly.compile(bytes)

	// imports is minimal stub (empty functions) and exports is a list of things it exports
	const { imports } = await getWasmInterface(m)

	// now I can inject my own functions

	{
	"neuronID": "fd764f8cc086705e",
	"neuron": {
	"id": "fd764f8cc086705e",
	"name": "Defy",
	"layers": [
	{
	"id": 0,
	"name": "L1"
	},