F159 Fenris159

Commander tooling / web systems / .NET interop

Fenris

I build practical software for players and developers: colony planning tools, EDMC companion workflows, release pipelines, and native input libraries that survive contact with real machines.

View Projects GitHub
Player-first Tools tuned against live workflows, logs, and real edge cases.
Release-minded Version files, changelogs, packages, and automation kept in sync.
Pragmatic Small fixes, concrete verification, and maintainable code paths.

Selected work

Projects Worth Tracking

EDMC Companion

RavenColonial EDMC

A companion plugin that brings build project tracking into EDMarketConnector, including overlay workflows, aggregate tracking, and safer update handling.

  • Track All overlay
  • Digest checks
  • Locale parity
  • Windows-safe updater
Source
.NET Library

GameInputSharp.Core

A practical C# wrapper around Microsoft GameInput, packaged for NuGet with CI behavior that handles real runner and hardware differences.

  • NuGet package
  • GameInput interop
  • CI diagnostics
  • Release notes
Source NuGet
Assistant Workflow

OpenClaw Discord TTS Attacher

A Discord-focused plugin that turns assistant text replies into spoken MP3 attachments for more natural voice channel workflows.

  • Discord
  • TTS
  • JavaScript
  • Assistant tooling
Source

Live GitHub signal

Top 5 Tracked Repos

Ranked by stars, then forks, then latest push. The RavenColonial website repo is intentionally excluded; RavenColonial EDMC is included.

01

EDMC_GalaxyGPS

A plugin for EDMC to make your life easier when using Spansh updated to support Fleet Carriers

Python 7 stars 2 forks
02

ravencolonial_edmc

EDMC companion plugin for colonization tracking, overlay workflows, and update handling.

Python 4 stars 1 fork
03

GameInputSharp.Core

Idiomatic C# wrapper for Microsoft GameInput for .NET 8+ on Windows.

C# 3 stars 0 forks

How I tend to build

Engineering Style

01

Start from the runtime path

Logs, crash reports, live endpoints, and named examples come before theory.

02

Keep releases coherent

Versions, changelogs, package metadata, and workflow output should agree.

03

Design for messy machines

Windows file locks, optional hardware, CI variance, and user-local state are real inputs.

04

Write for players

Tools and docs should explain the action to take, not the architecture behind it.

Find me

Fenris on GitHub

Most of my public work lives around player tooling, Elite Dangerous workflows, package maintenance, and automation that keeps projects shippable.

Open GitHub Profile