Eventlog was by no means an original concept, the original idea for me developing Eventlog was by developing on the concept of Smartlog in Pinewood Builders, created by Irreflexive and maintained by Coasterteam. Eventlog works by allowing group event hosts to log player points in a far easier way, and export them into lists that can be submitted directly into leaderstat entries or into an external database.

Eventlog uses these concepts developed by Smartlog, however integrated many further features into it. My version of this concept allowed you to export the points into already made currencies, not specifically to a single points variable, by using conversion metrics set by the event host. My system had a far more complex take on the backup and restore system too, bringing in a more dynamic restore feature allowing you to pick from either the original or the backup or merge both during a restore. My version also gave more visual queues as to tracking information, highlighting players who had negative points, highlighting players with personal notes, and far more! My version also allowed notes to be submitted with the log, as well as notes for specific individual players which could be used to specify punishments or bonus reasons, very useful for group hosts. This version also allowed hosts, or the people defined as having automatic access, the ability to add other users or roles to log access roles, allowing them to modify logs too. It also introduced a hover system where once enabled, you could add or remove points from users by hovering over their character and clicking them, launching a profile of them showing their current points and notes, changing them there, previous attended events and more. Finally, I also developed a more dynamic import and export feature, allowing already exported logs to be re-exported, and allowing group leaders to accept/deny individual player point levels during the import stage which enforced player point safety, including doing this whilst in-game.

Acticheck, or Activity Check, is a small project I developed to assist smaller games using Adonis-based admin systems to track how long players were playing on specific teams in their games. It utilised datastores to effectively track how long a player was in a group or team by using a dynamic check system that could be changed or modified by the developer, and would present it in an easy to use UI. This was built for the Chronos Science Corporation group, who had various smaller subgroups representing roles within the game. A suggestion arose in the community by one of the leaders of one of these groups, and so I thought, why not turn this into a little pet project.

Whilst Acticheck does not send data outside of Roblox, it's data can be queried using Roblox Open Cloud, given that Acticheck sorts it's data into easy to find and locate scopes, as well as assigning player identifiable information to these records allowing developers quick and easy methods of deleting player data if deletion requests are made. Acticheck allows users to offline search too, searching players who are not in the game, or players who have never been in the game. All of Acticheck is configurable, however given that this project has been specifically made for this group, it's mechanics are tailored to this game, and would require some tinkering to get it working for each game.

I've developed various types of Discord to Roblox verification over the years, whilst I'm aware databases such as those of Bloxlink are open source, I and many other clients don't believe it suits our needs because of its guidelines, terms and dependencies. This is why some opt for their own verification systems that they even integrate into their games.

Some of the types of Discord to Roblox verification I've made in the past are:

• Going to a website where you log in uring your Roblox account using an OAuth2, then do the same with Discord and link them
• Inputting a code into a Roblox UI given by Discord, then verifying the right Discord account appears on the UI
• Legacy methods (putting a code in your player description)

These have been used in many ways including mirroring Roblox to Discord bans, automatically inviting players in the Discord to an appeals server or channel on a punishment, checking Discord users can perform actions based on their Roblox group rank, getting the players stats from their Discord account without having to specify their username and much more! Linking accounts to third party services can offer many interesting features and opportunities for developers and their games, and taking the time to build your own system to do it allows you to have a good understanding of what's possible and how to put systems like this into use properly, tailored for your experiences needs.

In all honesty, I never expected to make this website. I had a server which originally had a small portfolio on it which went over things likethe languages and libraries I'd used, as well as a small introduction. It was very small, not very good, and after I changed my server host, I never put the old website back up and instead put up a maintainence page.

One day, I was bored and decided to undertake a website as my pet project. I'd never really used HTML5 and CSS properly before and didn't really know what I was doing, but I ended up creating this website. The layout and functionality hasn't really changed since it's early stages, and I make semi-regular changes to the portfolio buttons on the website as well as adding images to the slideshow as time goes on. I'm proud of what I was able to accomplish in a paradigm I had no idea how to use.

I decided to undertake this project because I wanted to join onto development teams or undertake contract based development projects, but needed a method to show them to potential employers in a way under my control, totally by my design. This website has stood as a great way of doing that, allowing me to modify the website in any way needed to be able to show off individual projects, experience and my talents.

I've made many Discord bots in the past, for moderation, levelling, game management, community management and more. Each one uses a similar framework centered around the newest Discord features such as embeds, interactions, slash commands and more. The bots I make for clients are fully customised to their clients needs and are made in a model that aims to be 100% configurable without developer intervention which has been a target for me over all of my projects.

My bots are able to echo things from games, listen to internal webhooks, listen and respond to Redis messages and even modify Roblox game settings from outside of the game, such as being able to send broadcasts into the game, scheduling events, shutting down games, changing the Avatar Editor clothing availability, adding experience boosts and lots more. They also encompass a console system on the host server, so owners or administrators of the server can easily go into the bot, debug it and launch administrative commands from inside the console itself.

In Roblox, due to the, as of now, unfortunately poor Open Cloud Group API, groups have to make use of Roblox accounts created for the primary function of being controlled by scripts to make automatic group shouts, change the ranks of users, exile and many more things that should really be available through Open Cloud. There have been many repositories helping to do this such as Noblox.js and bloxy, however during the creation of another service at the time, I found that neither of these popular libraries seemed in-depth, up-to-date, or secure enough for me to use them for my work.

Thus I created my own library for Roblox bots which makes use of the bot accounts Roblox security token and X-CSRF-Token to log in and make changes on the website whilst posing as the user. Due to the methods of control used, my library is able to bypass Roblox bot checks and effectively disguise itself as a regular user whilst still yielding results. My library is faster, far better developed from the start, and uses the most up to date libraries and paradigms with current Roblox infrastructure, and is built around timeouts and error handling which is a common issue with it's popular counterparts.

In the future, I may release this as it's own Node.js repository, however due to my current resources, this is not yet planned.

I'm well-versed in creating responsive, fast and secure webservers using Typescript through Express. These are primarily put to use on Roblox when external databases, Redis instances or Discord bots are used in conjunction with a game or service. I've designed the infrastructure for many of these webservers and create fast and easy debugging and hosting methods including a console system, API token-based access system with levelled access and logs, all which can be used to assist developers on the projects.

All of my webservers make use of sensible rate limits, as well as API request protection systems. These include an API blacklist, a public and private key system where access to specific API endpoints can be locked to specific users, a body-based validation system that uses HMAC tokens to validate the integrity of post data, and logging of every HTTP request the webserver receives. These are all incredible, state of the art features that ensure that data on the webserver is safe, and that malicious users cannot weaponise the functionality of the service.

These webservers have been used for many things, including other systems mentioned on this portfolio, including Eventlog, Acticheck, Punish, Avatar Editor, the Quiz Centers, Discord Verification and more!

Xenforo is an enigma, it's a very popular Minecraft premium website software, but isn't the nicest in terms of it's API sometimes.

My experience using XenForo is minimal, and was my first and only time using PHP in a project. I used XenForo and it's API to create a Minecraft and Discord based account linking system for a client. This worked by creating linking sessions on a database, then sending the user to the session token on the website, and linking whatever account they were logged in as to the Minecraft account that was in the session. This worked similarly to the one used for Discord, where the user would be taken to a link page with a created session, this time without a pre-registered Discord account within the session, the user would click a button to authorise an application on their Discord account, then Discord would link back to the original link page with the token needed to fully link the account.

These were impressive systems used to reward players for linking the account, allowing them to post on the forum, it would echo bans to Discord and the website where Discord access would be removed and the website would prompt the user to appeal, allowing them to select the punishment they're appealing without them having to input a punishment code or staff having to go looking for it. It was a fun to make system and I enjoyed how effective it was once it was published. It was also used to verify ownership of accounts through Tebex, where the logged in user would have their IP checked alongside IP's they'd previously logged in as, so users couldn't buy something in the shop as another user, then charge it back leading to the user being falsely banned from the network. Unfortunately I do not have an image of this one in action.