Skip to content
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

Positions for text, announcement, and store channels are all separate #3963

Closed
1 task done
advaith1 opened this issue Mar 18, 2020 · 0 comments · Fixed by #4070
Closed
1 task done

Positions for text, announcement, and store channels are all separate #3963

advaith1 opened this issue Mar 18, 2020 · 0 comments · Fixed by #4070

Comments

@advaith1
Copy link
Contributor

advaith1 commented Mar 18, 2020

Please describe the problem you are having in as much detail as possible:
When there are channels of more than one of those 3 types in one category, they will all be separate: the first text channel will be position 0, the first announcement channel will be position 0, the second text channel will be position 1, etc.
Discord lets you mix these types and put them in any order, unlike voice channels, which must all remain at the bottom of the category.

Include a reproducible code sample here, if possible:

client.channels.cache.get('499345401766346752').position // 0
client.channels.cache.get('374925969099587584').position // 0

of course, you'll need to test with channels in a server the bot is in.

Further details:

  • discord.js version: 12.0.0
  • Node.js version: v12.14.1
  • Operating system: Ubuntu 16.04.6
  • Priority this issue should have – please be realistic and elaborate if possible: Low, not a bot-breaking issue
  • I have also tested the issue on latest master, commit hash: 5b9cdc5
@advaith1 advaith1 changed the title Positions for text, announcement, and store channels are all seperate Positions for text, announcement, and store channels are all separate Mar 19, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants