Closed Gregor7008 closed 2 years ago
Implemented, except for a index number system: I still have no idea how I can detect whether one index number isn't used and use the lowest one possible. I marked the necessary lines for changing the channel name as comments, actually updating them is a lot harder though than, as suggested in the comments, just adding +1 to the total size of keys in the JSONObject "createdchannels"... Problem for future-me!
Implemented the {number} variable for now, BUT: I don't like it. First of all: Everything is right in the EventListener class "Processor.class", and in addition to that everything looks pretty messy. And then there's also the problem of the bot having to randomly replace the index number in the channel name if present. Now imagine the channel being named (by default): "Gregor7008's channel 7" where 7 is the index number. Currently it would just replace the 7 in my name with a 6 which is... mildly unoptimal. A pattern search would make more sense, in which the bot would count the words until reaching the {number} variable in the Join2Create data object, and then count them in the channel name as well. If the correct index number is at the correct spot it should replace it. It's an edge case, but something I don't want to experience hoestly. Yes I'm picky :D Join2Create Channel Rework coming up, maybe?!
Settings like user limit, bit rate, visibility to @everyone etc.