- Sep 16, 2023
- 1,397
- 1
- 474
- 111
In-game name: See forums signature.
Steam ID:
Age: 24
For how long have you played on our servers?: Since August, 2023.
What country are you from?: UK
Time Zone: GMT/BST
Do you have a mic?: Yes
Is this your first application for Developer? If not, link previous ones:
No.
Have you received any bans?: No.
How confident are you with GLua? (Rate yourself 1-10 using rating guide): I believe Maxnet is no longer a thing with the death of DarkRP, so I'm a bit unclear on the feature set of it. I'd say 6, possibly 7.
Do you have any experience with Git?:
Yes. I'm a software engineer professionally and use it regularly, along with GitHub and GitLab, and have familiarity with things like CI in both.
Do you have previous experience as a Developer for GMod?:
I have not directly worked on anything for any Gmod server, beyond possibly some minor bug fixes a long time ago if I recall correctly, but I do have a fair bit of experience with GLua, along with enough familiarity with Hammer to look around a map file and find info about bugs/issues.
Some examples of work I have done:
I have not provided the code or anything for the addons mentioned here. If anyone in the dev team wants to see that, I can send that upon request via Discord DM - just DM me at deniz3n.
How many hours can you commit to developing per week?: At least the 4 hours per week required on average, likely more some weeks, depending on what work and other commitments I have.
Why do you want to be a Developer? What can you help us with?:
I really like SCP-RP and want to help improve it. I can help anywhere needed, whether on 65 or 9, and on bug fixes, improvements, or full new features. Some things I'd like to work on are:
Steam ID:
Age: 24
For how long have you played on our servers?: Since August, 2023.
What country are you from?: UK
Time Zone: GMT/BST
Do you have a mic?: Yes
Is this your first application for Developer? If not, link previous ones:
No.
Have you received any bans?: No.
How confident are you with GLua? (Rate yourself 1-10 using rating guide): I believe Maxnet is no longer a thing with the death of DarkRP, so I'm a bit unclear on the feature set of it. I'd say 6, possibly 7.
Do you have any experience with Git?:
Yes. I'm a software engineer professionally and use it regularly, along with GitHub and GitLab, and have familiarity with things like CI in both.
Do you have previous experience as a Developer for GMod?:
I have not directly worked on anything for any Gmod server, beyond possibly some minor bug fixes a long time ago if I recall correctly, but I do have a fair bit of experience with GLua, along with enough familiarity with Hammer to look around a map file and find info about bugs/issues.
Some examples of work I have done:
This is a very WIP addon, and my latest version does not work, as it is part-way through a rework based on some previous feedback.
This addon allows admins to spawn a "Radio Configurator" (terrible naming, I know), a SENT that people can interact with to open a menu. This menu allows you to spawn a Radio SWEP, or configure an existing one. When you have a Radio, you can use comms channels similar to how they exist on the server, e.g. /isd, /ets, etc., along with /panic to trigger a panic button.
Unlike on the server, however, you can:
I have a variety of ideas to continue this which I haven't yet implemented, e.g.:
This addon allows admins to spawn a "Radio Configurator" (terrible naming, I know), a SENT that people can interact with to open a menu. This menu allows you to spawn a Radio SWEP, or configure an existing one. When you have a Radio, you can use comms channels similar to how they exist on the server, e.g. /isd, /ets, etc., along with /panic to trigger a panic button.
Unlike on the server, however, you can:
- Use the Radio Configurator to create Radios on the fly, so if one is lost somehow, or you want to give someone one who didn't previously have one (e.g. a D-class, another faction, etc.), you can do that.
- Radios can be dropped. If they are picked up, they can be used by someone else. Anyone using a given Radio will have the same comms access and display names as the original holder. This means, for example, that CI could steal one and spy on comms, or pretend to be whoever they've got the Radio from. This could also be useful for ISD - they could have SA create a radio for them that appears as an Engineer, which they could then use to communicate with FLC breakers undercover.
- A Radio can have different display names and name colours in different channels. This is most useful for if e.g. O5 want to hide their actual names, so they could appear as "Site Inspector Tim" in most channels, but "O5-4" in A-1 comms and "O5-4 'The Hidden'" on O5 comms.
- Channels can also be created and configured on the fly. So if e.g. SA wanted to create a new channel for everyone that might respond to a Code 1, they could add a new channel, give it a name and command like /code1, and then add radios from e.g. all MTFs, DEA, and GSD Officer+.
I have a variety of ideas to continue this which I haven't yet implemented, e.g.:
- Adding a hook system to enable spawning these on a player based on their job. E.g. it could be added as an option in VJE, complete with pre-configured names and channels.
- Supporting faction/group separation, e.g. by having Radio Configurators be assigned to a group, and then only be able to configure radios/channels attached to that group, so e.g. GOC can't edit Foundation channels.
- A proper admin menu for things like above. The configurators already have an admin menu you can open/close, but it doesn't currently do anything.
[DEV] zRadio Setup - Clipped Garry's Mod with Medal.tv
79 Views - Watch [DEV] zRadio Setup by deniz3n and millions of other Garry's Mod videos on Medal. #garrysmod
medal.tv
[DEV] zRadio Multiplayer - Clipped Garry's Mod with Medal.tv
33 Views - Watch [DEV] zRadio Multiplayer by deniz3n and millions of other Garry's Mod videos on Medal. #garrysmod
medal.tv
This is a simple bin SENT, inspired by the recent change log Ethan made with the chemical container bins.
This can be spawned, appears as a bin prop, but interacting with it with a SWEP held will remove that entity. This checks first if what you're holding is something you're allowed to /drop via the associated DarkRP hook, so you can't e.g. delete your Keys SWEP or something by accident.
The idea for this is twofold:
This can be spawned, appears as a bin prop, but interacting with it with a SWEP held will remove that entity. This checks first if what you're holding is something you're allowed to /drop via the associated DarkRP hook, so you can't e.g. delete your Keys SWEP or something by accident.
The idea for this is twofold:
- The server can cut down on entity count by encouraging people to delete SWEPs they would instead leave lying around. For flasks and the like, they may auto-delete, but other items don't and are often left abandoned and linger unnecessarily. If a player has an item they don't want anymore, e.g. a containment beam, or a clipboard, they can just interact with the bin to get rid of it, instead of just abandoning it in some random corner.
- This could actually be useful to players. Roles such as GSD and ISD may come across contraband like keycards from 1162 or weapons that they don't want to keep or leave around for a D-class or whoever to potentially find. With this bin, they can just pick it up, take it to a bin, and get rid of it properly.
- A proper interaction prompt or confirmation dialogue to prevent people from accidentally getting rid of things they want to keep.
- Some way to either retrieve recently disposed of items, or at least see what was disposed of, e.g. so ISD can see that the Tech Expert they were chasing just dropped a CL4 card in the bin.
- A way to dispose of other non-SWEP items, e.g. NVGs.
[DEV] zBin - Clipped Garry's Mod with Medal.tv
Watch [DEV] zBin by deniz3n and millions of other Garry's Mod videos on Medal. #garrysmod
medal.tv
This is a disguise system similar to the existing disguise card system on CN.
Players can use a Disguise Kit SWEP to scan someone by looking at them and clicking on them - with a range limit. This will grab the relevant data, and the user can then right-click to produce a Disguise SWEP.
Left-clicking with a Disguise will replace the user's model, bodygroups, skin and name with the one of the data set. They can change the specific name by right-clicking with the Disguise out, so that e.g. if they want to disguise as a specific person they have the keycard of, they can, or they can just make up a different name to avoid being metagamed based on having the wrong voice or whatever.
When you apply a Disguise, this will give you another Disguise back, which contains all of your previous model's name, looks, etc., so you can swap back to it by pulling that out and left-clicking again.
Disguises can also be dropped, so that e.g.:
Players can use a Disguise Kit SWEP to scan someone by looking at them and clicking on them - with a range limit. This will grab the relevant data, and the user can then right-click to produce a Disguise SWEP.
Left-clicking with a Disguise will replace the user's model, bodygroups, skin and name with the one of the data set. They can change the specific name by right-clicking with the Disguise out, so that e.g. if they want to disguise as a specific person they have the keycard of, they can, or they can just make up a different name to avoid being metagamed based on having the wrong voice or whatever.
When you apply a Disguise, this will give you another Disguise back, which contains all of your previous model's name, looks, etc., so you can swap back to it by pulling that out and left-clicking again.
Disguises can also be dropped, so that e.g.:
- If a DEA Agent grabs a CI disguise, but doesn't currently plan to use it, they can go and drop it off in SOP wing to use later without worrying that if they die, they'll lose it.
- People can give another player a disguise they've produced, so that e.g. ISD can grab a bunch of different disguises, keep them in ISD wing, and use them later, rather than having to go and grab the specific disguise they need right before they need to use it, with no ability to use a different disguise in between without losing the other one.
- A CI DC can grab two disguises and give their fellow DC one of them.
- A DC can leave their own real "clothes" behind at their base, to avoid being caught with them or having SOP steal it from them to go back to their base with.
- Some kind of materials system, so disguises aren't just limited by a cooldown - you'd have limited supplies to make disguises, and would need to restock, so you can't e.g. just stay on surface making infinite disguises and dropping them off at your base.
- Some kind of limit on both who you can make disguises of (similar to the own-team vs other-team disguise card limits), and who can use a Disguise, so e.g. a Tech Expert can't just pick one up and use one.
- Using something other than the DarkRP RP name to set your name - this sticks around after rejoining, and appears on the leaderboard, which isn't ideal.
- Handling name prefixes and enforcing them, which I believe is a VWar thing, and not a base DarkRP thing.
- Better UX, e.g. having disguise name setting be a little GUI box instead of a chat thing, and actually showing the user what the Disguise they're holding (or have just taken) is without having to apply it.
- I haven't been properly able to test whether the bodygroup and skin grabbing parts work correctly - I believe they should, but I'd need to change some things on my test server and test it with another player.
- Avoid having this interact badly with PAC.
[DEV] zRadio Multiplayer - Clipped Garry's Mod with Medal.tv
33 Views - Watch [DEV] zRadio Multiplayer by deniz3n and millions of other Garry's Mod videos on Medal. #garrysmod
medal.tv
I have not provided the code or anything for the addons mentioned here. If anyone in the dev team wants to see that, I can send that upon request via Discord DM - just DM me at deniz3n.
How many hours can you commit to developing per week?: At least the 4 hours per week required on average, likely more some weeks, depending on what work and other commitments I have.
Why do you want to be a Developer? What can you help us with?:
I really like SCP-RP and want to help improve it. I can help anywhere needed, whether on 65 or 9, and on bug fixes, improvements, or full new features. Some things I'd like to work on are:
- Implementing the key features of my comms addon in CN, and merging comms access with the VC radios, so there's not two completely separate comms and comms management systems, but one combined one that has all of those features plus the ability for SA/SC/REGCOM/whatever to configure things, spawn new radios, and people to use disguises and the like.
- Containment Maintenance and associated bits.
- Fixing and improving the Repair Tool and other bits - many areas, it's very finicky.
- Fixing bugs that have been around a while, like 096 being "seen" through doors and map displacements, voice chat distance/audibility mismatches, and various annoyances with the CCTV system.
- Reworking 035 with some ideas I've talked about previously.
- Improving the disguise system, including some features from my own disguise addon.
- Reworking the placer tool and the dispenser system so that they both can be edited by SL on the fly, rather than everything being manually done by devs.