Open thebadman4662 opened 5 months ago
I mean outside of cap and HoP, the rest just involve extra leadership and space law tacked onto existing job experience
I mean maybe, but I do agree a user shouldn't be surprised by being in a role they don't feel ready for. As an example: say I am playing a security cadet. If I am still struggling with the guns, chases, and batons, it really doesn't matter how many hours I put into the role, being put in a more senior position isn't gonna feel good.
Command roles just bump the problem up from potentially having a bad round to your bad round possibly having longer lasting consequences.
freshly unlocked roles should default to "off" imo, would really just rectify all the related complaints.
Also nukies should be higher time requirments in my opinion, but that's a seperate issue.
When you unlock a job it defaults to medium priority
Are you sure that this is actually how it currently works on the servers? As far as I can tell from testing locally and looking at the code, it defaults to "Never" for jobs and antags are disabled
When you unlock a job it defaults to medium priority
Are you sure that this is actually how it currently works on the servers? As far as I can tell from testing locally and looking at the code, it defaults to "Never" for jobs and antags are disabled
Unless it was changed and not on changelog in past few months, yes, it should still put people on medium priority... Only job on wizden I could test it with left for me is CE if I wanted to confirm...
When you unlock a job it defaults to medium priority
Are you sure that this is actually how it currently works on the servers? As far as I can tell from testing locally and looking at the code, it defaults to "Never" for jobs and antags are disabled
Just unlocked CE and now im quitillion % sure.
Can confirm happened with cap a few months ago and with ward recently :mistake:
What priorities do your job slots default to when creating a new character slot? Because AFAIK a new player/character should get the same thing. All I can say Is that I don't see where it would default to anything other than "Never" in the code, and when testing locally with a new database It always seems to be "Never"
Is there any chance you've played before role timers were added, or are importing loadouts with the priority already set to medium, even if the job is currently locked due to timers?
I guess its also possible that it previously did default to medium at some earlier point, and that any characters older than that have profiles saved with them set to medium? In which case the fix might be to just bulldoze any saved settings for currently locked roles when saving a profile? But I'm not sure if that's even the issue.
Description
When you unlock a job it defaults to medium priority, with recent rules change it can be outright batshit malicious to new players when they unlock command, bonus points for command being picked before every single thing but nukies AND being higher than low so even if there are players that are willingly playing command if nobody else wants to, they are still picked after newbies that unlock the slot.
Reproduction
Screenshots