CapsAdmin
PAC3 Utilities Settings Menu has lost nearly all of its options
It was removed here: [Commit: 80925072db392d97600649fd272d3bf5c0b1e2a9] (https://github.com/CapsAdmin/pac3/commit/80925072db392d97600649fd272d3bf5c0b1e2a9)
It was merged into the workshop branch here: Commit: 80925072db392d97600649fd272d3bf5c0b1e2a9
I tested this in single player with the latest version of PAC3 on the workshop to double-check this.
I think they were moved into the pac3 editor settings menu. Not the highest quality video, but I went through the menu. It is not there. https://www.youtube.com/watch?v=EyonqIqNZaM
I'll take a look tomorrow. I'm not sure if the changes were moved to another file or if they were somehow lost after merging master to develop.
I think they were just straight up removed, the blacklist/friend related ones are in options > settings.
Enabling parts is pretty much useless and just causes confusion if people disable them by accident. It also only appeared after you used the given part so you could never really see all the settings anyway. You can still disable them through console commands although you probably shouldn't.
PAC Volume was removed over a year ago and 'volume' is used since then.
The rendering ones got replaced with options > rendering > no reflections.
Reveal on +use, you can still enable that with pac_onuse_only 1
Hide disturbing, can be enabled with pac_hide_disturbing 1
Reveal on +use, you can still enable that with pac_onuse_only 1, although it doesn't really work especially with whitelists etc. It's super scuffed in general and not reliable.
I use it since i've implemented it and never hit a bug with it, what is unreliable about it?
@CapsAdmin could you delete https://github.com/CapsAdmin/pac3/commit/80925072db392d97600649fd272d3bf5c0b1e2a9 from master?
I wanted it deleted a while ago because it botched the commit history. Seems like it might've caused some other unintended issues.
As for why it happened, I accidentally 'Squash and Merge' develop into master instead of a normal merge.
I use it since i've implemented it and never hit a bug with it, what is unreliable about it?
Actually forget it, it seems to work fine now. I've tried in the past and it just didn't work that well but maybe it was the time where requests didn't work at all.
@CapsAdmin could you delete 8092507 from master?
I wanted it deleted a while ago because it botched the commit history. Seems like it might've caused some other unintended issues.
As for why it happened, I accidentally 'Squash and Merge' develop into master instead of a normal merge.
Isn't it too late now? I think it's going to cause more problems than it's worth.
As mentioned further up, they have been mostly moved.
What features specifically do you miss and why? I assume you meant those you underlined, but can you explain further?
Pardon the delay, I have a guest visiting from overseas. @CapsAdmin "Hide outfits that some folks can find disturbing" and "Reveal outfits only on +use" would be great. The wear filter and outfit filter in the PAC3 settings menu would also be nice to have copied there. Adding them inside of the editor itself makes an extra step for many people who possibly have never used PAC3 before. I'm not requesting these features for my personal use, but for ease of players filtering out stuff they don't care to see. I have been using PAC3 on +use only for a very long time now; I originally requested it in #594 "Hide outfits that some folks can find disturbing" was also something I'm sure I in part requested but I can't find any discussion for it right now