Skip to content

Instantly share code, notes, and snippets.

@LucasOe
LucasOe / conflicts.psm1
Last active November 30, 2023 18:37
Powershell module for detecting conflicts between Witcher 3 mods
# Usage
# 1. Download quickbms.exe and witcher3.bms (The ScriptMerger files are outdated):
# http://aluigi.altervista.org/papers/quickbms.zip
# http://aluigi.altervista.org/bms/witcher3.bms
# 2. Place this file into a directory next to quickbms.exe and witcher3.bms
# 3. Load this module in your PowerShell profile
$quickbmsPath = "$PSScriptRoot\quickbms.exe"
$witcherbmsPath = "$PSScriptRoot\witcher3.bms"
{
"name":"Chrome OneDark",
"version":"1.01",
"description":"OneDark theme for Chrome",
"manifest_version":2,
"theme":{
"colors":{
"frame":[21,21,21],
"frame_inactive":[21,21,21],
"frame_incognito":[21,21,21],
@LucasOe
LucasOe / conflicts.ps1
Last active October 15, 2022 23:58
Powershell script for detecting conflicts between Witcher 3 mods
# Usage
# 1. Download quickbms.exe and witcher3.bms (The ScriptMerger files are outdated):
# http://aluigi.altervista.org/papers/quickbms.zip
# http://aluigi.altervista.org/bms/witcher3.bms
# 2. Place this file into a directory next to quickbms.exe and witcher3.bms
# 3. Change $witcherPath to your Witcher directory.
#
# To show conflicts between two (or more) mods, run `./conflicts.ps1 <mod1> <mod2> <...>` inside the Powershell console.
# For example: `.\conflicts.ps1 modHDReworkedProject modBrothersInArms`
# To list every conflicting mod file, run this script with only one mod as an argument.
@LucasOe
LucasOe / Mirror's Edge Commands.html
Created May 26, 2019 11:18
Known "console" commands for Mirror's Edge
https://udn.epicgames.com/Three/ConsoleCommands.html
To use the following key bindings, you need to locate the TdInput.ini file located in \Documents\EA Games\Mirror's Edge\TdGame\Config
You don't really need to backup that file, because if you screw it up, you can just delete it, restart Mirror's Edge and it will create a default TdInput.ini for you. But create a backup of it anyways.
All bindings look like this: Bindings=(Name="<KEY>",Command="<COMMAND>",Control=False,Shift=False,Alt=False)
Every new binding needs to be added in the [Engine.PlayerInput] section. To keep track of what we edited, we will only add new bindings before the existing bindings (after the line that says bEnableMouseSmoothing=true).
Please note that the commands only work when you are in a level.