Leveling & VoiceXP not working with InfiniTea Voice Forge
I've built a "Temp Voice" style system for creating voice channels, however I have some users reporting that when they use these channels, created by InfiniTea, their users are not receiving XP while in them. Is there any requirement for the voice channel such that Kiai can pick up the channels and distribute XP?
Solution:Jump to solution
We can try to get some reproduction steps in the next week or so. We’re launching the feature that directly caused this so hopefully that will generate some feedback to use.
30 Replies
Hey @xTwisteDx! Our team will answer your post soon.
If this is an issue in your server, make sure you've included your server's ID (This can be found on the
/ping
command), as well as which users are having this issue.
Once your question has been answered, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution
to help others find the solution via Answer OverflowReceived word that it might be related to this issue. https://discord.com/channels/744282929684938844/1364717284068687963
Hi there! The only permissions required for Voice XP are View Channel and Connect. If you’ve already granted these permissions and are still having issues, please send the server id, channel ids, and the user ids of those affected.
@Jaqqour inviting you into here to provide the details.
Heya Kiai team - last time we had this issue using Tempvoice i belive shadow had to add a specific check for that temp VC channel bot - this part of the thread has the details and action taken https://discord.com/channels/744282929684938844/1364717284068687963/1366181349068640307
we are now looking to use the infinitea temp VC channel maker as its got a few features that we prefer over tempvoice
however as with tempvoice (initially before the above check for temp voice shadow added) the XP award for voice seems to be very intermittent.
Alright! I'll be sure to forward this to the developers. Could you give me a channel id and user id so I can see if the bot even tried logging the voice session?
one example is
User ID - 284447837683449856
Channel ID - 1375235803256586342

he was in it for about 10ish minutes, with 2 people so should have quallified for XP
Hm yeah seems a voice session wasn't even created for that user
With this new bot, Kiai gets the required permission, correct?
Yes unless the channel is private
Do you mind giving me the link for your new bot?
Sure, but do bear in mind it's still in closed alpha.
You'll need to log in, and enable "Create VC" on the feature-flags. After that, give me a channel ID and guild id and I'll manually add the channel on the backend.
@Finny one moment. I see an issue you're having w/ feature flags not being generated.
Okay it's there now, in theory xD. Found a bug doing that
Still doesn't seem to be working
You need to give me the guild id and channel id
We don't have the new website up yet to configure it, so I have to add to the backend
Oh, sorry! Guildid: 1041045270659604701
Channel id: 1075622012799696948
Are you sure that's correct? I do not see a guild config for that id. Which usually means it was deleted.
Err bot removed that is.
Er wrong id 1041045270659604701
There you go, it should work whenever you connect to the channel now
[VoiceEvent] Voice Forge disabled for guild Buape Testing
I'm enabling it for you.
alright
Don't forget to set priority for the bot as well. I seen a missing permissions error pop up
I gave it priority, anything else?
No that should be it
Obviously it'll need manage channel perms, manage member perms (To move you) the norm for that type of feature.
I can't reproduce this, but have went ahead and reported it to the devs, hopefully a fix can be found!
fingers crossed its the same ez fix that was used for Tempvoice bot
@xTwisteDx Hey, apologies for the radio silence from our end. Finny among other team members tried to reproduce this issue to no avail. Are you still experiencing this behaviour?
Solution
We can try to get some reproduction steps in the next week or so. We’re launching the feature that directly caused this so hopefully that will generate some feedback to use.
Appreciate it! Let me know 🙏
Hey there @xTwisteDx, is all well?
I think you can close this for now. We will revisit if it comes up again.
No worries, cheers.