Repository navigation
Releases: DocFoxHound/BeowulfHunterPy
Release list
BeowulfHunter1.2
🏴☠️ BeowulfHunter
A Star Citizen kill tracker and combat logger for the pirate org IronPoint.
📋UPDATES
1.2
- You only ever need to enter your API key once. The program will automatically load it on launch.
- The program now waits for Star Citizen to launch and will load by itself. This reduces how often you have to tab out of Star Citizen to make sure it's running.
1.1
- Added a crash recovery, so that when StarCitizen inevitably fails you the bot will not. It will automatically detect you starting the game back up and reconnect.
- Added FileLock, which prevents the application from running multiple instances and, comically, logging multiple kills for the same person.
🚀 Getting Started
After downloading...
- Unzip the file to any destination
- Launch BeowulfHunter.exe
- Go to discord
- Start Star Citizen
- Type the following bot command:
/key-create - Put this in the bot
- Click activate
📜 Instructions
- Launch Star Citizen
- Open Discord and use
/key-create
- Copy the Code (only you can see it)
- Paste it in BeowulfHunter and click "Activate"
- Your screen should now look like this. From now on you only need to click "Load Existing Key"
⚙️ Features
- ✅ Real-time log monitoring
- ☠️ Kill detection
- 📦 Auto-submission to API and Database
- 📊 Leaderboard through the Discord bot Beowulf
- 💀 Pirate-themed interface
📦 Installation
- If you do not want to download the .exe, you can simply...
git clone https://github.com/yourname/BeowulfHunter.git
cd BeowulfHunter
npm install
npm start💾 Information being Tracked
- ❌ IP Addresses
- ✅ Username associated with kill
- ✅ Victim's name
- ✅ Ship used (sometimes)
- ✅ Ship killed (sometimes)
- ✅ Dollar Value of Killed Ship
- ❌ Player Location
Which can be verified in the code, itself.
- There is a "zone" tracked in the code, but the zone correlates to where the player is sitting when they make the kill. For most cases, this is the ship itself. This can be chalked up to CiG being bad with naming conventions. There ARE coordinates given in the kill log, but I disregard these.
- Example kill log:
<2025-04-13T17:17:51.279Z> [Notice] <Actor Death> CActor::Kill: 'Mercuriuss' [200146297631] in zone 'ANVL_Hornet_F7A_Mk2_2677329226210' killed by 'DocHound' [202061381370] using 'GATS_BallisticGatling_S3_2677329225797' [Class unknown] with damage type 'VehicleDestruction' from direction x: 0.000000, y: 0.000000, z: 0.000000 [Team_ActorTech][Actor]
Security
- Hash: 0d464ca552d9ab1e8212d07d94734fbe9dd2fd018c12f406dfc747dac1ba9629
- https://www.virustotal.com/gui/file/0d464ca552d9ab1e8212d07d94734fbe9dd2fd018c12f406dfc747dac1ba9629?nocache=1 (hey, my lowest score yet!)
- Signed, but by a self-signed cert (meaning virtually nothing but CA's are expensive for hobbiests)
CREDIT
Created by BlightVeil's developer team, and originally found at: https://github.com/BlightVeil/Killtracker/tree/v1.3
BeowulfHunter1.1
🏴☠️ BeowulfHunter
A Star Citizen kill tracker and combat logger for the pirate org IronPoint.
📋UPDATES
- Added a crash recovery, so that when StarCitizen inevitably fails you the bot will not. It will automatically detect you starting the game back up and reconnect.
- Added FileLock, which prevents the application from running multiple instances and, comically, logging multiple kills for the same person.
🚀 Getting Started
After downloading...
- Unzip the file to any destination
- Launch BeowulfHunter.exe
- Go to discord
- Start Star Citizen
- Type the following bot command:
/key-create - Put this in the bot
- Click activate
📜 Instructions
- Launch Star Citizen
- Open Discord and use
/key-create
- Copy the Code (only you can see it)
- Paste it in BeowulfHunter and click "Activate"
- Your screen should now look like this. From now on you only need to click "Load Existing Key"
⚙️ Features
- ✅ Real-time log monitoring
- ☠️ Kill detection
- 📦 Auto-submission to API and Database
- 📊 Leaderboard through the Discord bot Beowulf
- 💀 Pirate-themed interface
📦 Installation
- If you do not want to download the .exe, you can simply...
git clone https://github.com/yourname/BeowulfHunter.git
cd BeowulfHunter
npm install
npm start💾 Information being Tracked
- ❌ IP Addresses
- ✅ Username associated with kill
- ✅ Victim's name
- ✅ Ship used (sometimes)
- ✅ Ship killed (sometimes)
- ✅ Dollar Value of Killed Ship
- ❌ Player Location
Which can be verified in the code, itself.
- There is a "zone" tracked in the code, but the zone correlates to where the player is sitting when they make the kill. For most cases, this is the ship itself. This can be chalked up to CiG being bad with naming conventions. There ARE coordinates given in the kill log, but I disregard these.
- Example kill log:
<2025-04-13T17:17:51.279Z> [Notice] <Actor Death> CActor::Kill: 'Mercuriuss' [200146297631] in zone 'ANVL_Hornet_F7A_Mk2_2677329226210' killed by 'DocHound' [202061381370] using 'GATS_BallisticGatling_S3_2677329225797' [Class unknown] with damage type 'VehicleDestruction' from direction x: 0.000000, y: 0.000000, z: 0.000000 [Team_ActorTech][Actor]
Security
- Hash: 29d18efb323405303de2e48719d6f14672e1e6b629a329c52bd399bdcc183130
- https://www.virustotal.com/gui/file/67834e330f0ae474e8bf3a90a74a7ff249029200c77a2d3e82712d60db5c44b4?nocache=1
- Signed, but by a self-signed cert (meaning virtually nothing but CA's are expensive for hobbiests)
CREDIT
Created by BlightVeil's developer team, and originally found at: https://github.com/BlightVeil/Killtracker/tree/v1.3
BeowulfHunter1.0
🏴☠️ BeowulfHunter
A Star Citizen kill tracker and combat logger for the pirate org IronPoint.
🚀 Getting Started
After downloading...
- Go to discord
- Start Star Citizen
- Type the following bot command:
/key-create - Put this in the bot
- Click activate
📜 Instructions
- Launch Star Citizen
- Open Discord and use
/key-create
- Copy the Code (only you can see it)
- Paste it in BeowulfHunter and click "Activate"
- Your screen should now look like this. From now on you only need to click "Load Existing Key"
- WARNING
If the game crashes, you need to restart BeowulfHunter!
⚙️ Features
- ✅ Real-time log monitoring
- ☠️ Kill detection
- 📦 Auto-submission to API and Database
- 📊 Leaderboard through the Discord bot Beowulf
- 💀 Pirate-themed interface
📦 Installation
- If you do not want to download the .exe, you can simply...
git clone https://github.com/yourname/BeowulfHunter.git
cd BeowulfHunter
npm install
npm start💾 Information being Tracked
- ❌ IP Addresses
- ✅ Username associated with kill
- ✅ Victim's name
- ✅ Ship used (sometimes)
- ✅ Ship killed (sometimes)
- ✅ Dollar Value of Killed Ship
- ❌ Player Location
Which can be verified in the code, itself.
- There is a "zone" tracked in the code, but the zone correlates to where the player is sitting when they make the kill. For most cases, this is the ship itself. This can be chalked up to CiG being bad with naming conventions. There ARE coordinates given in the kill log, but I disregard these.
- Example kill log:
<2025-04-13T17:17:51.279Z> [Notice] <Actor Death> CActor::Kill: 'Mercuriuss' [200146297631] in zone 'ANVL_Hornet_F7A_Mk2_2677329226210' killed by 'DocHound' [202061381370] using 'GATS_BallisticGatling_S3_2677329225797' [Class unknown] with damage type 'VehicleDestruction' from direction x: 0.000000, y: 0.000000, z: 0.000000 [Team_ActorTech][Actor]
Security
- Hash: 7c37b9a129bee9781cc256868cd4ca367a4d49e52c124b1ebe752d85a32b04a0
- https://www.virustotal.com/gui/file/7c37b9a129bee9781cc256868cd4ca367a4d49e52c124b1ebe752d85a32b04a0?nocache=1
- Signed, but by a self-signed cert (meaning virtually nothing but CA's are expensive for hobbiests)
CREDIT
Created by BlightVeil's developer team, and originally found at: https://github.com/BlightVeil/Killtracker/tree/v1.3