-
-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tag Overhaul Sorting #1373
Tag Overhaul Sorting #1373
Conversation
build failed :ten_uhh: |
oh also idk how to build anything im just an idiot who likes doing things sometimes and then isnt surprised they fail |
I did it I'm a genius |
Why is this so hardcoded |
that's what I was trying to prevent |
how so? is it not the same system but sorted into specific folders? the current ones good but can get flooded |
I am failing to see how this is hardcoded if you could just move the friendcode.txt to a seperate folder to change their permission level, the variables/access lines inside the txt file should stay the same unless i messed that up |
Okay so now it should use the new system (margs new one, not the one utilizing folders for perms), and read the |
Margs Tag Overhaul is epic but can get messy, so this PR should make it so friendCode#1234.txt file can be read in a folder (Example like Friends folder, Staff folder, ABCDEF folder, etc), as long as its under the Tags directory. The only folders it shouldn't read are MOD_TAGS, VIP_TAGS, & SPONSOR_TAGS.