Open LeviSnoot opened 2 days ago
I have created an initial commit for those curious. Before I proceed with further rewriting of playerStatus.py
, I'm going to look into a less invasive check for whether the Fortnite process is running by using the Windows API instead of looping for the process which was a pretty bad idea.
Windows API was a bit too deep of a rabbit hole to dive into, at least for now. I've decided to increase the modularity of the code by splitting the functions of the player status script into multiple scripts that the main script can utilize when needed. So far the basic functionality is starting to come along, but we're still a long ways off.
That said I am getting more and more excited about this rewrite the more I progress on it. It feels like we're gaining a lot of much needed improvements naturally in this process. Plus, building is a lot more straightforward in Rust, so once this is ready for release, we should be able to start making proper releases and updates, so people won't need to worry about installing dependencies if they just wanna get up and running.
Writing this project in Python was great for proof-of-concept, but the code and language is very inefficient at this stage, so I'm taking up the task of rewriting it in Rust. This will take some time to do, as I am not experienced with it yet, but this will certainly improve performance drastically.
Especially when I eventually get to implementing #6. It has always been a goal to have this be runnable as a background service, so the user doesn't manually have to run it every time they start Fortnite.
This should also make the idea of creating a GUI wrapper around this project more feasible.