bherila

Recommendation

Emblem for Costume Thalassa and field the costume by default.

The costume gives up only 50 boosted health on the first cast—500 instead of 550—but its fully charged cast gives 800 boosted health instead of 650 and four turns of status-ailment immunity instead of three. Both versions can receive the costume-unlocked insanity resistance, so that is not a reason to prefer one form over the other. ([GitHub][1])

Use regular Thalassa as a situational alternative when the enemy relies heavily on mana reduction or effects that prevent Special Skills. Her Cleric-class Manashield can be more useful in that matchup than the costume’s Sorcerer-class talent. For normal raid, war, and event use, the costume’s stronger second cast is generally more valuable. ([empiresandpuzzles.com][2])

Talent path through node 20

bherila

Site-wide Cmd+K navigation — implementation summary

Goal

Add fast Cmd/Ctrl+K navigation to pages using the default site navbar, while leaving Finance, PHR, and other layouts with their own navbar/palette untouched.

The command palette should:

• search immediately from an already-hydrated in-memory payload
• avoid a new endpoint, eager background fetch, or extra database query

bherila

Temps MariaDB PITR / Postgres Upgrade / CI Handoff

Date: 2026-06-24 UTC (updated end of day) Repo local path: /home/bwh/proj/temps Fork: bherila/temps Upstream: gotempsh/temps

Goal

Unblock upstream PR #138 (MariaDB) by extracting unrelated fixes into separate,

bherila

Here’s a recap of the flow you should follow after you commit an order edit using orderEditCommit:

1. Commit the Order Edit

You already do this with orderEditCommit.

2. Fetch Fulfillment Orders for the Edited Order

After the edit is committed, fetch the fulfillment orders for the order to see if multiple fulfillment orders exist (which can happen if new items were added and the original fulfillment order was not eligible for modification).
Operation

bherila

# Download in m4a format
--format="ba"
--extract-audio
--audio-format m4a

# Continue downloading if the download failed previously
--continue
--no-overwrites

# Set track number, album name, and artist name metadata tags

bherila

{
    "buildings": [],
    "geospatial": {
        "buildings": [],
        "centerCoords": {
            "lat": 37.775971,
            "lng": -122.412758
        },
        "containerSize": {
            "width": 703,

bherila

{
  "listings": [
    {
      "listing": {
        "listingIdSHA": "1227583713283266489",
        "compassPropertyId": 63839393134201230,
        "feedListingId": "1227583713283266489",
        "listingType": 2,
        "sourceFilters": [

bherila

ls | grep -e "\.json$" | while read file; do
  in2csv $file > "$(echo "$file" | cut -f -4 -d .).csv"; 
done

bherila

FORT RESTful Order API v1.04 Documentation

The following reference guide will allow you to create orders and retrieve their status within the FORT Warehouse Management System (WMS).

Overview

The RESTful Order API is intended to be used by an external system that would like to fulfill orders within WMS. The RESTful Order API allows a system to create and view the status of orders securely over HTTPS.

Flow

bherila

A
A acid
A b station
A battery
A bond
A derrick
A la marengo
A la maryland
A level