For some context yesterday Palworld released its first raid, and I decided to start farming out the materials needed to prepare for a battle. Part of this entailed waiting for dungeons to respawn. I decided that due to some at the time limited time constraints to enlist the all powerful cheat engine's built in speedhack to speed the game up. However I forgot to close the program after I had reset its speed value back to 1 for palworld and completed the lengthy fight. Now for some very VERY important information, cheat engine is a blacklisted program for battle eye. The battle eye service will not start a game if cheat engine is open. Except it didn't do that this time. Battle eye opened and ran destiny without so much as a notification that a program capable of manipulating memory was opened on the system (granted not active). However previously this would cause an error in the form of a blacklisted program being run and would ask you to close it and not allow the game to run without closing the program. Presumably all I would have needed to do had I realized the program was running was to switch it to the Destiny2.exe and start poking around the memory addresses. This seems like a really really simple oversight on the part of battle eye, though I'm wondering what bungie could do from their configuration end to solve this issue. I'd rather see this issue quickly patched around before somebody else also figures out how to use this (or something like it) to run blacklisted cheating programs on the game. Hopefully someone at bungie finds this and can get in contact with the right people internally to replicate and fix this problem.