#Just bring back the old Kohl's Admin.
74 messages · Page 1 of 1 (latest)
The subscription is made to give Kohl and his contributors some money
VIP sub isn't even on sale rn 💀
I am not an admin or a dev
it isnt removed..?
Brudda there's a whole community wanting back
Who
Allow me to show ya
Ask them to share what they'd like to see changed with the new admin here, saying something sucks for a made up reason isn't how you get change.
nvm ig.
No it doesn't (I have the OLD OLD VIP and can't use it with the new admin)
T shirt VIP? 💀
Yup
I'll add it for ya, was waiting for someone to call me out on that 😉
Still works all these years later
Also, you deleted all the commands, I think chaining?
Idk?
Someone mentioned it was broke
what?
so all this “remove the new admin” was just to get old vip commands back?
😭
Deleted all the commands? Could you help me find the specific issue and report it here or ask them to.
Also, you shouldn't be waiting for someone to call you out on that
Just saying
Honestly it just slipped my mind
ffs
HOW?
dude calm down
I don't recall if the regular worked btw
it aint a big of a deal
I took em off sale like 6 years ago and haven't thought of them since
tape it's ok
he's not mad
okay
Wait, did the cheaper one give VIP commands too, or...?
VIp donation and above did yes
I see
I'll be giving legacy donors benefits in the new one, mind you it's not 1.0 yet
I still have a lot of work to do
So please share any concerns or considerations, I'm a person who makes lots of mistakes too 🙂
I need the help seeing this stuff
Could you look into this and let me know what you find? If there any serious issues I'd like to address them ASAP.
I can't really test chaining rn, because VIP ain't working
But crm and crmhat don't exist
Right, batch commands should work properly now if they have the latest version, and CRM and crmhat will be coming soon 😉
Commands weren't deleted, it's a brand new command system, I'm recreating a lot of the behavior from old commands to use R15 and account for things they never did before to improve the general experience
Found a weird one
Occasioanlly, I think the letter "n" causes an invalid command prefix notification?
Like, typing it does?
Idk
Ah because :n is the notify command, do you have any letters before it?
If it's just "n" by itself that's an issue for sure
Sometimes it happens, sometimes it doesn;t
If it's like .n though it will tell you the correct prefix because it assumes you are trying to use that command
Maybe a space before it triggers? I'll take a look
Thanks for the heads up
Just got it without the letter "n"
(For context, MOST of the messages I got this on started with brackets, idk if that factors in)