Bug: FAdmin breaks "Inherits from..."

[feldma]

The bug is that FAdmin will break the "Inherits from" option, so whenever you change it to anything other then user, it will just default back to user.

I've tried making jobs while FAdmin is disabled, and it works. However, when I turn FAdmin back on, it resets everything to user again.
I would prefer to leave FAdmin enabled, so I guess I'm going to be configuring every rank I have manually.

If anyone has a solution (other then to disable FAdmin, that would be appreciated.)

My ULib/ULX versions (run "ulx version" in console):
ULib v.. 2.52d
ULX v.. 3.62d

Game mode(s) I am having this problem on:
DarkRP

Lua errors shown in console, if any:
No errors are being shown in console.

Thank you,
Feldma.

[Bytewave]

FAdmin and ULX/ULib do not play nice together, as has been the case before. It's an issue with overrides implemented by FAdmin, I believe.
I don't think you can get them to play nice together. It's just one or the other.

[Megiddo]

We've fixed this bug at least twice now -- FPtje keeps re-introducing it. Are you sure you're using the latest ULX and DarkRP? Because the latest ULX pretty much ignores much of what DarkRP tells it since DarkRP has so many problems with user/group management.

[feldma]

Assuming that these are the most up to date versions of ULX / ULib...

ULib v.. 2.52d
ULX v.. 3.62d

Then yes, I believe I have the most up-to-date version of DarkRP. I'll check tomorrow though.

[Megiddo]

Are you really copying the entire output from "ulx version"?

EDIT: I just tested the latest DarkRP + ULX on my server and am having no issues with inheritance.

[roastchicken]

I think it might be useful to specify if that's the latest release version, or the latest version from GitHub.

[JamminR]

roastchicken, per some new version info we're using, he's using release.
Which in and of itself usually isn't latest.

[roastchicken]

roastchicken, per some new version info we're using, he's using release.
Which in and of itself usually isn't latest.

If you're talking about feldma, isn't he using a non-release version? If I'm interpreting the ULib.pluginVersionStr() function correctly, doesn't the d at the end of the number denote a non-release, non-workshop version?

I was talking about Megiddo, who said they had testing it with the latest version of ULX. I've heard "latest" be used interchangeably for the latest release and the latest 'build'.

[Megiddo]

Yes, he's using a non-release version but he should have received a date with that too. It's clear he's not copying the version regardless, based on the formatting.

[JamminR]

Now that I re-read what I read from our Team chat section regarding versions, I'm confused as to how we version our betas, but yes, he does have some type of beta but difficult to tell which one.

[Megiddo]

'd' is for development. It will normally print the date, unless for some reason that information was removed.
'w' is for workshop.
No suffix means release version.

"ULib v.. 2.52d" is not what would be output from ULX, meaning this is not the correct version.

[feldma]

Sorry for not getting back to you guys. Haven't had time recently.

*Sigh*, stupidly, I wasn't copying the entire output of 'ulx version', just the actual version. Not sure why I didn't do that.

Here:

ULib v2.52d (01/03/16)
ULX v3.62d (01/01/16)

Again, sorry about the delay / stupidness from me.

EDIT: Well, apparently, without me doing anything, this issue has resolved itself.
Uhm. I'm not exactly sure what fixed the issue. Hmm...

[never2nv]

This happened to me before however after I set immunity levels within Fadmin > Server Settings > Edit Groups to the correct immunity levels/chain-of-command this bug seemed to stop.

However before doing the immunity levels I just ended up manually editing the groups.txt within /garrysmod/data/ulib WHILE THE SERVER WAS SHUTDOWN and it worked like a charm <3