nickludlam

@echo off

:: 1. Path to the game (NOT the server)
set "GAME_ROOT=E:\SteamLibrary\steamapps\common\Arma Reforger"
set "GAME_EXE=%GAME_ROOT%\ArmaReforgerSteam.exe"
set "GAME_DATA=%GAME_ROOT%\addons"

:: 1. Path to the game Executable
set "SERVER_DIR=E:\SteamLibrary\steamapps\common\Arma Reforger Server\arma_reforger"
set "SERVER_EXE=%SERVER_DIR%\ArmaReforgerServerDiag.exe"

nickludlam

@echo off

:: 1. Path to the game Executable
set "SERVER_DIR=E:\SteamLibrary\steamapps\common\Arma Reforger Server\"
set "SERVER_EXE=%SERVER_DIR%\ArmaReforgerServer.exe"

:: 2. Path to the Game Data (The core game folder)
set "GAME_ROOT=E:\SteamLibrary\steamapps\common\Arma Reforger"
set "GAME_DATA=%GAME_ROOT%\addons"

nickludlam

# Code Assistant Directives for Svelte 5 Runes

This document directs code assistants to write code using **Svelte 5 Runes**, the new reactivity model in Svelte 5.

## Overview

Svelte Runes are a set of powerful APIs that provide fine-grained reactivity in Svelte 5. When writing or modifying code in this project, always use runes instead of the legacy reactive declarations and statements.

## Core Runes

nickludlam

{
  "bindAddress": "0.0.0.0",
  "bindPort": 2001,
  "publicAddress": "local",
  "publicPort": 2001,
  "a2s": {
    "address": "0.0.0.0",
    "port": 17777
  },
  "game": {

nickludlam

	override void RefreshSeizingTimer()
	{
		if (!m_fSeizingStartTimestamp)
			return;

		int servicesCount;

		if (m_Base)
		{
			array<SCR_EServicePointType> checkedTypes = {

nickludlam

[WorkbenchToolAttribute(name: "Entity Query Tool", description: "Queries the map for resources, inside an AABB, and allows you to reject based on substring of the XOB path", wbModules: {"WorldEditor"}, awesomeFontCode: 0xf6e2)]
class EntityQueryWorldEditorTool: WorldEditorTool
{
	////////////////////////////
	// State vars

	World m_currentWorld;
	ref array<IEntity> m_entityResults = null;
	ref array<string> m_excludeStringArray = null;

nickludlam

#!/usr/bin/env ruby

# File: personalize_mammoth.rb
# Description: Adapt the Mammoth project to a personal bundle identifier and development team
#              and change the entitlements files to match the desired bundle identifier
#              When run again, it will revert the changes
# Usage: ruby personalize_mammoth.rb
# Deps: xcodeproj

require 'xcodeproj'

nickludlam

My experience coming to SvelteKit from Rails and Ruby

This is specifically because my experience in webdev is very informed by Ruby on Rails. I've done plenty of work with strongly typed languages, but never webdev. My experience is also from 2018 and older, so there may well be modern solutions that achieve parity with the clever things I'm finding in SvelteKit that I feel were not as present in Rails work. Don't at be bro!

Strong types are extraordinary at catching inter module communication issues. Any time you’re putting polymorphic messages into Redis, etc. Also it's very nice having a strongly typed, schema-aware database client. The auto-completion is very useful.

Idea: make some playgrounds to show examples live

Frustrations

Sometimes the VSCode plugins don’t update when you push prisma schema changes

nickludlam

<script lang="ts">
  import { onDestroy } from "svelte";
  import { writable } from "svelte/store";

  import type { SuperValidated } from "sveltekit-superforms";
  import { formFieldProxy,  superForm } from "sveltekit-superforms/client";

  import * as Form from "$lib/components/ui/form";
  import { Slider } from "$lib/components/ui/slider";

nickludlam

## Good Conduct

- Fix all warnings in your code before commits
    - I don’t want to have to turn on Warnings as Errors, but I will if I have to discuss this more than a few times.
- Keep an eye on runtime warnings. If they’re ones you’ve introduced, fix them before committing.
    - If they’re ones you think you can fix, please fix them.
    - If you aren’t sure what’s causing them. Let the rest of the team know so someone who knows the root cause can fix them.
- Check your references for NULL and handle gracefully, don’t just assume they exist.
- If you see something broken
    - FIX IT if you are confident you know how and it won’t massively impinge on your current work