The most important thing to note at the moment is that this is an early stage work in progress.
When I started working on this project (and even at the time of writing this), I have had no professional or academic experience in coding/programming/development. I chose an ambitious and challenging project specifically to help me learn to master Python and eventually other languages. Some of my methods may appear unorthodox as a result of my self-taught nature. If you're following changes as we progress, you might even notice significant changes being made to the code and my approach. This has already happened several times before I decided to creat a GitHub Repo to host my work on. One example is when I made the decision to switch from using plain text files (wrestlers/moveslists) to json. Discovering json format has made this project much more efficient and easy. Who knows what similar discoveries I'll make as I learn?
Work is currently in progress. All the options relating to Asset Management are complete (pending any issues conflicting with match sim or new ideas). I'm going to work on simulating a normal 1v1 match, before moving onto matches with additional participants and team settings, and then on to customisable rulesets for different match types. Once satisfied with that, I will move on to the booking options.
It will likely take a long time before I'm ready to show anything from the match sims. It's important to me that the story of the match is as compelling as possible. That means that there shouldn't be too much repitition, the flow and momemtum should be logical, there should be unbroken continuity (for example, it should not be possible to knock an opponent down in one part of the arena and then uppercut them in another without transitioning through the relevant position states and arena locations first), and it should be possible to pre-determine the winner or let the system decide. Hopefully, you can appreciate how painstaking this proccess will be to get everything right and the depth of testing required for quality assurance before it's ready for sharing.
If you're familiar with efeds then you'll probably think that they're a bit out of style now. You're probably right. I've not been an efedder for nearly 15 years, but it's something I used to enjoy and understand very well. I'm still in touch with lots of friends I've made through efedding who I can call on for advice and opinions. There's still plenty of active efeds around and there's no reason to think that (with the right tools) it could see another surge. More honestly though, I still miss it and would love to work on something related.
One of my first programs was written in Visual Basic while I was still an active efedder. It was for a site called GFed Wrestling (now closed) which used markdown language. The application had a simple GUI to reflect how a roleplayer might interact with the site when posting roleplays. It was designed to help newer roleplayers conform to a customisable format for their roleplays. It also gave them an ability to save and archive their RPs so they would not be lost when a fed closed.
My primary interest is in information security. I'm about to start a degree course on that, but I'm not ready for sharing any work on that yet (I do have a very simple looping RCE script for CVE-2021-42013 if anyone is interested though).
This is a hobby project and I think GH is perfect for reaching out to eFed communities with an interest in coding for constructive feedback while I work on the project.