-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathChange_Log.json
1759 lines (1759 loc) · 95.3 KB
/
Change_Log.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
{
"content": [
"|Change Log"
],
"Change Log": {
"level": 1,
"url": "https://discord.com/developers/docs/docs/change-log#change-log",
"content": [
"|Add Auto Moderation custom_message Action Metadata Field",
"|Update to Locked Threads",
"|Increase Auto Moderation Keyword Limits",
"|Guild Audit Log Events",
"|Thread Member Details and Pagination",
"|Add Default Layout setting for Forum channels",
"|Add Auto Moderation Allow List for Keyword Rules and Increase Max Keyword Rules Per Guild Limit",
"|Upcoming Application Command Permission Changes",
"|GameSDK Feature Deprecation",
"|Add Auto Moderation Regex Support",
"|Delete Ephemeral Messages",
"|New Select Menu Components",
"|Default Sort Order for Forum Channels",
"|Auto Moderation Spam and Mention Spam Trigger Types",
"|Forum Channels Release",
"|Message Content is a Privileged Intent",
"|Slash Command Mentions",
"|Session-specific Gateway Resume URLs",
"|Upcoming Permissions Change to Webhook Routes",
"|Min and Max Length for Command Options",
"|Add Subcommand Groups and Subcommands to Message Interaction Objects",
"|Changes to Bot Permissions for Interactions and Webhooks",
"|Calculated Permissions in Interaction Payloads",
"|Message Content in Auto Moderation events",
"|Updated Connection Property Field Names",
"|Auto Moderation",
"|Updated Command Permissions",
"|Forum Channels",
"|Guild Bans Pagination",
"|API v10",
"|Interaction Modals and Application Command Attachment Option Type",
"|Guild Member Timeouts",
"|Guild Scheduled Events",
"|Application Command Autocomplete Interactions",
"|Updated Thread Permissions",
"|User and Message Commands",
"|Select Menu Components",
"|Support for Multiple Embeds in Message Routes",
"|Buttons and Message Components",
"|API v9",
"|Application Command Permissions",
"|Large Bot Sharding Lowered to 150,000 Guilds",
"|Changes to Slash Command Response Types and Flags",
"|Slash Commands in DMs",
"|Change to Permission Checking when Creating Channels",
"|Slash Commands and Interactions",
"|Inline Replies",
"|Stickers",
"|Gateway v6 Intent Restrictions",
"|API and Gateway V8",
"|New Permission Fields",
"|Legacy Mention Behavior Deprecation",
"|New Properties on Guild Members Chunk Event",
"|New Allowed Mentions Object",
"|New Invite Events and Reactions Endpoint",
"|Rich Presence Spectate Approval",
"|Gateway Intents",
"|IP Discovery Updates",
"|GameSDK Version 2.5.6",
"|GameSDK Version 2.5.5",
"|Changes to Special Channels",
"|More Precise Rate Limits",
"|Bot Tokens for Achievements",
"|Additional Team Information",
"|Added Info Around Nitro Boosting Experiment",
"|Deprecation of Discord-RPC Rich Presence SDK",
"|New Invite Object Fields",
"|Ask to Join & Rich Presence SDK",
"|Documentation: Dispatch Store Listings",
"|Enhancement: User Object",
"|Documentation Fix: List of Open DMS in Certain Payloads",
"|Deprecation: RPC online member count and members list",
"|Enhancement: New Message Properties",
"|Enhancement: Get Guild Emoji Endpoint",
"|Deprecation: Accept Invite Endpoint",
"|Semi-Breaking Change: Very Large Bot Sharding",
"|New Feature: Rich Presence",
"|Breaking Change: API & Gateway Below v6 Discontinued",
"|New Feature: Channel Categories",
"|New Feature: Emoji Endpoints",
"|Breaking Change: Presence Activity Objects",
"|Breaking Change: Default Channels",
"|New Feature: Audit Logs",
"|Breaking Change: Version 6"
],
"Add Auto Moderation custom_message Action Metadata Field": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#add-auto-moderation-custom_message-action-metadata-field",
"content": [
"|Feb 24, 2023"
],
"Feb 24, 2023": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#add-auto-moderation-custom_message-action-metadata-field-feb-24,-2023",
"content": [
"Add new custom_message action metadata for the BLOCK_MESSAGE action type). You can now specify a custom string for every Auto Moderation rule that will be shown to members whenever the rule blocks their message. This can be used as an additional explanation for why a message was blocked and as a chance to help members understand your server's rules and guidelines."
]
}
},
"Update to Locked Threads": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#update-to-locked-threads",
"content": [
"|Feb 10, 2023",
"|Upcoming Changes",
"|How do I prepare for this change?"
],
"Feb 10, 2023": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#update-to-locked-threads-feb-10,-2023",
"content": []
},
"Upcoming Changes": {
"level": 3,
"url": "https://discord.com/developers/docs/docs/change-log#upcoming-changes",
"content": [
"Currently, threads in Discord (including forum posts) can either be archived or both locked and archived. Starting on March 6, 2023, threads will be able to be locked without being archived, which will slightly change the meaning of the locked field.",
"locked currently indicates that a thread cannot be reopened by a user without the MANAGE_THREADS (1 << 34) permission, but it doesn't restrict user activity within active (meaning non-archived) threads. After this change, users (including bot users) without the MANAGE_THREADS permission will be more restricted in locked threads. Users won't be able to create or update messages in locked threads, or update properties like its title or tags. Additionally, some user activity like deleting messages and adding or removing reactions will only be allowed in locked threads if that thread is also active (or un-archived).",
"If a user or bot user has the MANAGE_THREADS permission, they will still be able to make changes to the thread and messages. The upcoming change does not affect the meaning of the archived field or the behavior of a thread that is both locked and archived."
]
},
"How do I prepare for this change?": {
"level": 3,
"url": "https://discord.com/developers/docs/docs/change-log#how-do-i-prepare-for-this-change?",
"content": [
"If your app is interacting with threads (including forum posts), it should check the state of the locked and/or archived field for the thread to understand which actions it can or cannot perform. It should also be prepared to handle any errors that it may receive when a thread is locked."
]
}
},
"Increase Auto Moderation Keyword Limits": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#increase-auto-moderation-keyword-limits",
"content": [
"|Feb 8, 2023"
],
"Feb 8, 2023": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#increase-auto-moderation-keyword-limits-feb-8,-2023",
"content": [
[
"Increase maximum number of rules with KEYWORD trigger_type per guild from 5 to 6",
"Increase maximum length for each keyword in the keyword_filter and allow_list trigger_metadata fields from 30 to 60."
]
]
}
},
"Guild Audit Log Events": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#guild-audit-log-events",
"content": [
"|Jan 18, 2023"
],
"Jan 18, 2023": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#guild-audit-log-events-jan-18,-2023",
"content": [
"At long last, a new GUILD_AUDIT_LOG_ENTRY_CREATE event has been added to the gateway, allowing your application to react to moderation actions in guilds. The VIEW_AUDIT_LOG permission is required in order to receive these events, and the GUILD_MODERATION intent needs to be set when connecting to the gateway."
]
}
},
"Thread Member Details and Pagination": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#thread-member-details-and-pagination",
"content": [
"> danger\n> This entry includes breaking changes",
"|Jan 09, 2023",
"|Upcoming Changes"
],
"Jan 09, 2023": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#thread-member-details-and-pagination-jan-09,-2023",
"content": [
"A new member field was added to the thread member object. member is a guild member object that will be included within returned thread member objects when the new with_member field is set to true in the List Thread Members (GET /channels/<channel_id>/thread-members) and Get Thread Member (GET /channels/<channel_id>/thread-members/<user_id>) endpoints.",
"Setting with_member to true will also enable pagination for the List Thread Members endpoint. When the results are paginated, you can use the new after and limit fields to fetch additional thread members and limit the number of thread members returned. By default, limit is 100."
]
},
"Upcoming Changes": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#thread-member-details-and-pagination-upcoming-changes",
"content": [
"Starting in API v11, List Thread Members (GET /channels/<channel_id>/thread-members) will always return paginated results, regardless of whether with_member is passed or not."
]
}
},
"Add Default Layout setting for Forum channels": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#add-default-layout-setting-for-forum-channels",
"content": [
"|Dec 13, 2022"
],
"Dec 13, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#add-default-layout-setting-for-forum-channels-dec-13,-2022",
"content": [
"default_forum_layout is an optional field in the channel object that indicates the default layout for posts in a forum channel. A value of 1 (LIST_VIEW) indicates that posts will be displayed as a chronological list, and 2 (GALLERY_VIEW) indicates they will be displayed as a collection of tiles. If default_forum_layout hasn't been set, the value will be 0.",
"Setting default_forum_layout requires the MANAGE_CHANNELS permission."
]
}
},
"Add Auto Moderation Allow List for Keyword Rules and Increase Max Keyword Rules Per Guild Limit": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#add-auto-moderation-allow-list-for-keyword-rules-and-increase-max-keyword-rules-per-guild-limit",
"content": [
"|Nov 22, 2022"
],
"Nov 22, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#add-auto-moderation-allow-list-for-keyword-rules-and-increase-max-keyword-rules-per-guild-limit-nov-22,-2022",
"content": [
[
"Auto Moderation rules with trigger_type KEYWORD now support an allow_list field in its trigger_metadata. Any message content that matches an allow_list keyword will be ignored by the Auto Moderation KEYWORD rule. Each allow_list keyword can be a multi-word phrase and can contain wildcard symbols.",
"Increase maximum number of rules with KEYWORD trigger_type per guild from 3 to 5",
"Increase maximum length for each regex pattern in the regex_patterns trigger_metadata field from 75 to 260."
]
]
}
},
"Upcoming Application Command Permission Changes": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#upcoming-application-command-permission-changes",
"content": [
"|Nov 17, 2022",
"|Types of command permission configurations",
"|What's changing?",
"|Am I affected?",
"|How do I prepare for the changes?"
],
"Nov 17, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#upcoming-application-command-permission-changes-nov-17,-2022",
"content": [
"> danger\n> This entry includes breaking changes",
"Based on feedback, we\u2019re updating permissions for application commands to simplify permission management and to make command permissions more closely resemble other permissions systems in Discord.",
"Server admins can begin to opt-in to the command permission changes outlined here on a per-server basis starting on December 16, 2022. However, changes will not be applied to all servers until late January or early February.",
"> info\n> Current permissions behavior is documented in the application commands documentation and in the changelog for the previous permissions update",
"These changes are focused on how configured permissions are used by Discord clients, so most apps will be unaffected. However, if your app uses the Update Permissions endpoint (PUT /applications/<application_id>/guilds/<guild_id>/commands/<command_id>/permissions), you may need to make updates and should read these changes carefully."
]
},
"Types of command permission configurations": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#upcoming-application-command-permission-changes-types-of-command-permission-configurations",
"content": [
"> info\n> The following information isn\u2019t changing, but it\u2019s helpful context to understand the changes.",
"Discord\u2019s clients determine whether a user can see or invoke a command based on three different permission configurations:",
[
"Command-level permissions are set up by an admin for a specific command in their server. These permissions affect only a specific command.",
"App-level permissions are set up by an admin for a specific app in their server. These permissions affect all commands for an app.",
"default_member_permissions are set up by an app when creating or updating a command. default_member_permissions apply to that command in all servers (unless an override exists). More information about default_member_permissions is in the documentation."
],
"The concepts of these permission configurations are not changing. But then of course, the question becomes\u2026"
]
},
"What's changing?": {
"level": 3,
"url": "https://discord.com/developers/docs/docs/change-log#what's-changing?",
"content": [
"There are two changes around command permissions:",
[
"The logic used to apply permission configurations to a user in a given context within Discord clients",
"New APPLICATION_COMMAND_PERMISSIONS_V2 guild feature flag to indicate whether that guild is using the old permissions logic or the new (upcoming) logic."
],
"Let's go deeper into both of these.",
"|1. How permission configurations are applied in Discord",
"|2. "
],
"1. How permission configurations are applied in Discord": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#what's-changing?-1.-how-permission-configurations-are-applied-in-discord",
"content": [
"|Current behavior:",
"|Upcoming behavior:",
"|Flowchart for command permissions logic"
],
"Current behavior:": {
"level": 5,
"url": "https://discord.com/developers/docs/docs/change-log#1.-how-permission-configurations-are-applied-in-discord-current-behavior:",
"content": [
"Currently, these systems are mutually-exclusive, meaning that only one type of permission configuration is used to determine whether a user can invoke a command.",
"With this current system, there is a clear hierarchy: command-level permission configurations take precedence (if present), then app-level permission configurations (if present), and finally default_member_permissions if neither are present.",
"The implication of the current permissions system means that:",
[
"If any command-level permissions are configured, all app-level permissions and default_member_permissions are ignored for that command.",
"If any app-level permissions are configured, default_member_permissions is ignored for all of that app\u2019s commands."
],
"This system leads to unintentional permission escalations, and can force moderators to manually re-define their app-level configurations to make small tweaks on the command-level."
]
},
"Upcoming behavior:": {
"level": 5,
"url": "https://discord.com/developers/docs/docs/change-log#1.-how-permission-configurations-are-applied-in-discord-upcoming-behavior:",
"content": [
"The new system removes the mutual exclusion aspect, meaning that the different types of permission configurations work together rather than independently\u2014specifically, more than one may be used to determine whether a user can invoke a command.",
"default_member_permissions continues to act as a \u201cdefault\u201d that a developer can set when creating or updating a command.",
"App-level permission configurations now act as the \"base\" configuration.",
"App-level configurations define who is allowed to use the app and where. These will work together with default_member_permissions, meaning if a user is granted access via an app-level permission configuration, they will still be restricted to the default_member_permissions for each command (by default). No more accidentally granting /ban which requires BAN_MEMBERS to @BotMemers just because you gave them access to the app!",
"Command-level permission configurations now act as an \u201coverride\u201d of the app-level.",
"Command-level configurations override what is present at the app-level and any restrictions set by default_member_permissions. This means that an admin can explicitly grant a user access to a specific command even if they are denied access on the app-level or if they don't have permissions that meet that command's default_member_permissions.",
"If a command-level configuration does not exist for the given context, the system will fall back to looking at the app-level configuration."
]
},
"Flowchart for command permissions logic": {
"level": 5,
"url": "https://discord.com/developers/docs/docs/change-log#1.-how-permission-configurations-are-applied-in-discord-flowchart-for-command-permissions-logic",
"content": [
"Below is a simplified flowchart that illustrates how permissions will be applied by the Discord client after the new changes take effect.",
"Flowchart with an overview of the new permissions configurations logic"
]
}
},
"2. ": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#what's-changing?-2.-",
"content": [
"We added a new APPLICATION_COMMAND_PERMISSIONS_V2 feature flag which indicates whether that server is using the current permissions logic.",
[
"If the flag is present, that server is using the old command permissions behavior.",
"If the flag is not present, that server has migrated from the old command permissions behavior to the new behavior."
]
]
}
},
"Am I affected?": {
"level": 3,
"url": "https://discord.com/developers/docs/docs/change-log#am-i-affected?",
"content": [
"Your app will only be affected if it uses the PUT /applications/<application_id>/guilds/<guild_id>/commands/<command_id>/permissions endpoint. This is a pretty restricted endpoint used to manage and update application command permissions on behalf of admins, meaning that it requires the applications.commands.permissions.update scope.",
"If your app doesn\u2019t use this endpoint, there\u2019s nothing you need to prepare for these changes.",
"If your app does use this endpoint, you should read the section on preparing for changes below."
]
},
"How do I prepare for the changes?": {
"level": 3,
"url": "https://discord.com/developers/docs/docs/change-log#how-do-i-prepare-for-the-changes?",
"content": [
"To prepare for these changes, you should take two steps:",
"1. Use the APPLICATION_COMMAND_PERMISSIONS_V2 flag",
"Use this flag to determine which permissions logic that server is using. While the transition from the old behavior to the new behavior is happening, you may need two code paths depending on if the flag is present or not.",
{
"language": "py",
"code": "if 'APPLICATION_COMMAND_PERMISSIONS_V2' in guild.features:\n # Use current behaviors when interacting with endpoint\nelse:\n # Use new permissions behaviors when interacting with endpoint\n"
},
"> info\n> If you don\u2019t have access to guild features already through Gateway events, you can fetch that information using the GET /guilds/<guild_id> endpoint.",
"2. Modify the behavior based on your use case",
"After you know what permissions behavior the server is using, you should update how you handle that server specifically.",
"To understand what changes you need to make, you should look at the assumptions users have when your app updates their server\u2019s commands permissions. Do you have a web dashboard where admins update permissions? If so, analyze the logic of that dashboard and what your permission configurations are trying to do to map them to the new permissions behavior. Do you document what your app is doing in regards to certain command permissions you\u2019re configuring on behalf of the admin? If so, map that documentation to the new behavior.",
"If you are unsure, you can communicate with your admin users to ask if your new logic meets their expectations.",
"|What happens if I don\u2019t update my app?",
"|How long do I have to update my app?"
],
"What happens if I don\u2019t update my app?": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#how-do-i-prepare-for-the-changes?-what-happens-if-i-don\u2019t-update-my-app?",
"content": [
"If your app is affected and you don\u2019t update it, permissions behavior that your app configures may not match what you or the users of your app expect."
]
},
"How long do I have to update my app?": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#how-do-i-prepare-for-the-changes?-how-long-do-i-have-to-update-my-app?",
"content": [
"The new APPLICATION_COMMAND_PERMISSIONS_V2 flag is already live, and you should start seeing it in guilds\u2019 feature flags.",
"The new permissions behavior will roll out on December 16, 2022. On this date, admins will begin to see a banner that allows them to optionally move their server to the new behavior.",
"In late January or early February, all servers will be migrated to the new behavior. We'll post another changelog at this point, at which time you can remove any logic around the old permissions behavior."
]
}
}
},
"GameSDK Feature Deprecation": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#gamesdk-feature-deprecation",
"content": [
"|Nov 9, 2022"
],
"Nov 9, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#gamesdk-feature-deprecation-nov-9,-2022",
"content": [
"> danger\n> This entry includes breaking changes",
"To help keep us focused on the features, improvements, and gaming-related experiences that Discord users love, we are deprecating the following pieces of the GameSDK starting today, and decommissioning them on Tuesday, May 2, 2023:",
[
"Achievements",
"Applications",
"Voice",
"Images",
"Lobbies",
"Networking",
"Storage",
"Store [purchases and discounts]"
],
"This deprecation period will last until Tuesday May 2, 2023, after which these pieces will be decommissioned and no longer work. The other pieces of the GameSDK will continue to be supported.",
"We know that Discord is an important place for people to find belonging, and that using your Discord identity in games is a crucial part of that sense of belonging. You\u2019ll still be able to use the GameSDK to integrate Rich Presence, relationships, entitlements, basic user information, and the overlay."
]
}
},
"Add Auto Moderation Regex Support": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#add-auto-moderation-regex-support",
"content": [
"|Nov 4, 2022"
],
"Nov 4, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#add-auto-moderation-regex-support-nov-4,-2022",
"content": [
"Auto Moderation rules with trigger_type KEYWORD now support\na regex_patterns field in its trigger_metadata.\nRegex patterns are a powerful way to describe many keywords all at once using one expression. Only Rust flavored regex is supported, which can be tested in online editors such as Rustexp."
]
}
},
"Delete Ephemeral Messages": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#delete-ephemeral-messages",
"content": [
"|Oct 20, 2022"
],
"Oct 20, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#delete-ephemeral-messages-oct-20,-2022",
"content": [
"Ephemeral interaction responses and follow-ups can now be deleted with a valid interaction token using the following endpoints:",
[
"DELETE /webhooks/<application_id>/<interaction_token>/messages/@original",
"DELETE /webhooks/<application_id>/<interaction_token>/messages/<message_id>"
],
"As a reminder, interaction tokens stay valid for up to 15 minutes after the interaction occurs. Details can be found in the interaction documentation."
]
}
},
"New Select Menu Components": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#new-select-menu-components",
"content": [
"|Oct 13, 2022"
],
"Oct 13, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#new-select-menu-components-oct-13,-2022",
"content": [
"Four new select menu component types have been added to make it easier to populate selects with common resources in Discord:",
[
"User select (type 5)",
"Role select (type 6)",
"Mentionable (user and role) select (type 7)",
"Channel select (type 8)"
],
"The new select menu components are defined similarly to the existing string select menu\u2014with the exception of not including the options field and, within channel select menus, having the option to include a channel_types field. The select menu interaction apps receive also contain a resolved field for the new components.",
"More details can be found in the updated select menu documentation."
]
}
},
"Default Sort Order for Forum Channels": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#default-sort-order-for-forum-channels",
"content": [
"|Sep 22, 2022"
],
"Sep 22, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#default-sort-order-for-forum-channels-sep-22,-2022",
"content": [
"default_sort_order is an optional field in the channel object that indicates how the threads in a forum channel will be sorted for users by default. Setting default_sort_order requires the MANAGE_CHANNELS permission.",
"If default_sort_order hasn't been set, its value will be null."
]
}
},
"Auto Moderation Spam and Mention Spam Trigger Types": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#auto-moderation-spam-and-mention-spam-trigger-types",
"content": [
"|Sep 21, 2022"
],
"Sep 21, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#auto-moderation-spam-and-mention-spam-trigger-types-sep-21,-2022",
"content": [
"Two new trigger types were added to Auto Moderation:",
[
"MENTION_SPAM blocks messages that mention more than a set number of unique server members or roles. Apps can define the number (up to 50) using the mention_total_limit field in the trigger metadata object when creating or updating an Auto Moderation rule.",
"SPAM blocks links and messages that are identified as spam."
],
"More information can be found in the Auto Moderation documentation."
]
}
},
"Forum Channels Release": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#forum-channels-release",
"content": [
"|Sep 14, 2022"
],
"Sep 14, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#forum-channels-release-sep-14,-2022",
"content": [
"Forum channels (GUILD_FORUM or 15) have been released to all community servers. GUILD_FORUM channels are a new channel type that only supports threads, which display differently than in text (GUILD_TEXT) channels.",
"Check out the forums topic for more information on the relevant APIs and technical details, and the Forums FAQ for more about the feature."
]
}
},
"Message Content is a Privileged Intent": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#message-content-is-a-privileged-intent",
"content": [
"|Sep 1, 2022",
"|If your app is verified",
"|If your app is unverified"
],
"Sep 1, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#message-content-is-a-privileged-intent-sep-1,-2022",
"content": [
"> danger\n> This entry includes breaking changes",
"As of today, message content is a privileged intent for all verified apps and apps eligible for verification. More details about why it's becoming a privileged intent and how to apply for it is in the Help Center FAQ.",
"Any app that does not have the message content intent configured in its app's settings within the Developer Portal wiIl receive empty values in fields that expose message content across Discord's APIs (including the content, embeds, attachments, and components fields). These restrictions do not apply for messages that a bot or app sends, in DMs that it receives, or in messages in which it is mentioned."
]
},
"If your app is verified": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#message-content-is-a-privileged-intent-if-your-app-is-verified",
"content": [
"Verified apps and verification-eligible apps must be approved for the message content intent to receive message content. If your verified app isn\u2019t approved, or doesn\u2019t account for the new message content restrictions, it will break for users.",
"|Temporary Message Content Intent"
],
"Temporary Message Content Intent": {
"level": 5,
"url": "https://discord.com/developers/docs/docs/change-log#if-your-app-is-verified-temporary-message-content-intent",
"content": [
"Verified apps or apps that have submitted for verification can temporarily opt-in to a grace period which will allow your app to continue receiving message content until October 1. However, if you opt-in to the grace period, your app will be prevented from joining any additional servers until you opt-out. More details are in the Help Center article."
]
}
},
"If your app is unverified": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#message-content-is-a-privileged-intent-if-your-app-is-unverified",
"content": [
"Unverified apps must still must enable the intent in your app\u2019s settings within the Developer Portal.",
"Existing unverified apps will automatically have the message content intent toggled on in their settings. New unverified apps will have to manually toggle the intent in the Developer Portal."
]
}
},
"Slash Command Mentions": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#slash-command-mentions",
"content": [
"|Aug 22, 2022"
],
"Aug 22, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#slash-command-mentions-aug-22,-2022",
"content": [
"This week, Slash Command mentions are rolling out across all Discord clients (for Android, mentions are limited to the React Native client). Clicking a Slash Command mention will auto-populate the command in the user's message input.",
"Slash Command mentions use the following format: </NAME:COMMAND_ID>. You can also use </NAME SUBCOMMAND:ID> and </NAME SUBCOMMAND_GROUP SUBCOMMAND:ID> for subcommands and subcommand groups."
]
}
},
"Session-specific Gateway Resume URLs": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#session-specific-gateway-resume-urls",
"content": [
"|Aug 9, 2022"
],
"Aug 9, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#session-specific-gateway-resume-urls-aug-9,-2022",
"content": [
"> warn\n> Starting on September 12, 2022, apps that aren\u2019t using the new resume_gateway_url field to resume gateway sessions will be disconnected significantly faster than normal.",
"A new resume_gateway_url field has been added to the Ready gateway event to support session-specific gateway connections. The value of resume_gateway_url is a session-specific URL that should be used when resuming the gateway session after a disconnect. Previously, wss://gateway.discord.gg was used to connect and resume sessions, but should now only be used during the connection.",
"At the moment, the value of resume_gateway_url will always be wss://gateway.discord.gg to give developers more time to adopt the new field. In the near future, the value will change to the session-specific URLs."
]
}
},
"Upcoming Permissions Change to Webhook Routes": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#upcoming-permissions-change-to-webhook-routes",
"content": [
"|July 13, 2022"
],
"July 13, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#upcoming-permissions-change-to-webhook-routes-july-13,-2022",
"content": [
"On August 8th, 2022 we will begin requiring the VIEW_CHANNEL (1 << 10) permission for webhook routes which require MANAGE_WEBHOOKS (1 << 29), to align with our documented behavior. We don't expect that many applications will be affected by this, but in case you are, please ensure you have updated permissions needed for accessing the following routes:",
[
"GET /webhooks/{webhook.id}",
"DELETE /webhooks/{webhook.id}",
"PATCH /webhooks/{webhook.id}",
"GET /channels/{channel.id}/webhooks",
"POST /channels/{channel.id}/webhooks"
]
]
}
},
"Min and Max Length for Command Options": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#min-and-max-length-for-command-options",
"content": [
"|July 1, 2022"
],
"July 1, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#min-and-max-length-for-command-options-july-1,-2022",
"content": [
"Application command options of type STRING now includes optional min_length and max_length fields to control the length of text a user can input.",
"The value of min_length must be greater or equal to 0, and the value of max_length must be greater or equal to 1."
]
}
},
"Add Subcommand Groups and Subcommands to Message Interaction Objects": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#add-subcommand-groups-and-subcommands-to-message-interaction-objects",
"content": [
"> danger\n> This entry includes breaking changes",
"|July 1, 2022",
"|Upcoming Changes",
"|Updating your app"
],
"July 1, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#add-subcommand-groups-and-subcommands-to-message-interaction-objects-july-1,-2022",
"content": [
"While this is a breaking change, most apps only rely on interaction responses (INTERACTION_CREATE), not message interaction objects (MESSAGE_CREATE). Interaction responses are unaffected by this change."
]
},
"Upcoming Changes": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#add-subcommand-groups-and-subcommands-to-message-interaction-objects-upcoming-changes",
"content": [
"Starting July 18, 2022, the name field for message interaction objects will now include subcommands and subcommand groups in the value (along with the existing top-level command). In the future, we recommend not relying on this message interaction field.",
"The format of the value will be the different command levels (if they exist), separated by spaces:\n<command name> <subcommand group name> <subcommand name>",
"The name field is only seen on messages that are a response to an interaction without an existing message, so interaction objects for message components don\u2019t include this field."
]
},
"Updating your app": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#add-subcommand-groups-and-subcommands-to-message-interaction-objects-updating-your-app",
"content": [
"Most apps only rely on interaction responses, not message interaction objects.",
"We don't recommend that your app relies on the name field for message interactions objects, but if it does you should update your app to handle subcommands and subcommand groups that your app may encounter.",
"As an example of the change, pretend your app had a command /role with subcommands add and remove. Currently, the name field in the original interaction payload would contain role. If you responded to that interaction with a message then fetched its contents, the name field for that message interaction object would contain role as well.",
"After this change, the name field for the original interaction payload will still contain role. However, now if you responded to that interaction with a message then fetched its contents, the name field for that message interaction object would contain role add or role remove."
]
}
},
"Changes to Bot Permissions for Interactions and Webhooks": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#changes-to-bot-permissions-for-interactions-and-webhooks",
"content": [
"> danger\n> This entry includes breaking changes",
"|Jun 29, 2022",
"|Upcoming Changes",
"|Updating Your App"
],
"Jun 29, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#changes-to-bot-permissions-for-interactions-and-webhooks-jun-29,-2022",
"content": []
},
"Upcoming Changes": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#changes-to-bot-permissions-for-interactions-and-webhooks-upcoming-changes",
"content": [
"> warn\n> MENTION_EVERYONE, SEND_TTS_MESSAGES and USE_EXTERNAL_EMOJIS are the only permissions that will be affected by this change. In a previous version of this changelog, it was indicated that ATTACH_FILES and EMBED_LINKS would be affected but this is no longer the case.",
"Starting August 3, 2022, the way some of a bot's MENTION_EVERYONE, SEND_TTS_MESSAGES and USE_EXTERNAL_EMOJIS permissions are calculated is changing in two cases:",
[
"When responding to an interaction (like application commands or message components)",
"When executing a webhook that the bot created"
],
"Going forward, in the above cases, a bot\u2019s MENTION_EVERYONE, SEND_TTS_MESSAGES and USE_EXTERNAL_EMOJIS permissions will be calculated based on the permissions its granted, including any overwrites. Previously, a bot\u2019s permissions in these cases relied only on those granted to @everyone.",
"This change only applies to bots. The permissions for an app without a bot user (or without the bot scope) will still depend on @everyone."
]
},
"Updating Your App": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#changes-to-bot-permissions-for-interactions-and-webhooks-updating-your-app",
"content": [
"If your bot wants to use the MENTION_EVERYONE, SEND_TTS_MESSAGES or USE_EXTERNAL_EMOJIS permissions when responding to interactions or executing a webhook, ensure that the bot was installed (or explicitly granted) with them.",
"Note that even if your bot is installed with certain permissions, they can be changed using overwrites. For interactions, you can use the app_permissions field to determine your app or bot's contextual permissions before replying."
]
}
},
"Calculated Permissions in Interaction Payloads": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#calculated-permissions-in-interaction-payloads",
"content": [
"|Jun 29, 2022"
],
"Jun 29, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#calculated-permissions-in-interaction-payloads-jun-29,-2022",
"content": [
"Interaction payloads now contain an app_permissions field whose value is the computed permissions for a bot or app in the context of a specific interaction (including any channel overwrites). Similar to other permission fields, the value of app_permissions is a bitwise OR-ed set of permissions expressed as a string. Read details in the interactions documentation.",
"For apps without a bot user (or without the bot scope), the value of app_permissions will be the same as the permissions for @everyone, but limited to the permissions that can be used in interaction responses (currently ATTACH_FILES, EMBED_LINKS, MENTION_EVERYONE, and USE_EXTERNAL_EMOJIS)."
]
}
},
"Message Content in Auto Moderation events": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#message-content-in-auto-moderation-events",
"content": [
"|Jun 21, 2022",
"|Breaking Changes"
],
"Jun 21, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#message-content-in-auto-moderation-events-jun-21,-2022",
"content": []
},
"Breaking Changes": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#message-content-in-auto-moderation-events-breaking-changes",
"content": [
"In API v10, the MESSAGE_CONTENT (1 << 15) intent is now required to receive non-empty values for the content and matched_content fields in AUTO_MODERATION_ACTION_EXECUTION gateway events. This matches the intended behavior for message content across the API."
]
}
},
"Updated Connection Property Field Names": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#updated-connection-property-field-names",
"content": [
"|Jun 17, 2022"
],
"Jun 17, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#updated-connection-property-field-names-jun-17,-2022",
"content": [
"The $ prefix in identify connection properties are deprecated. The new field names are os, browser, and device. When passed, the $-prefixed names will resolve to the new ones.",
"In API v11, support for the previous field names ($os, $browser, and $device) will be removed."
]
}
},
"Auto Moderation": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#auto-moderation",
"content": [
"|Jun 16, 2022"
],
"Jun 16, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#auto-moderation-jun-16,-2022",
"content": [
"Add new Auto Moderation feature which enables guilds to moderate message content based on keywords, harmful links, and unwanted spam. This change includes:",
[
"New endpoints for creating, updating, and deleting Auto Moderation rules",
"New gateway events emitted when Auto Moderation rules are created (AUTO_MODERATION_RULE_CREATE), updated (AUTO_MODERATION_RULE_UPDATE), and deleted (AUTO_MODERATION_RULE_DELETE). Requires the AUTO_MODERATION_CONFIGURATION (1 << 20) intent",
"New gateway event emitted when an action is executed (AUTO_MODERATION_ACTION_EXECUTION). Requires the AUTO_MODERATION_EXECUTION (1 << 21) intent",
"New audit log entries when rules are created (AUTO_MODERATION_RULE_CREATE), updated (AUTO_MODERATION_RULE_UPDATE), or deleted (AUTO_MODERATION_RULE_DELETE), or when Auto Moderation performs an action (AUTO_MODERATION_BLOCK_MESSAGE)"
]
]
}
},
"Updated Command Permissions": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#updated-command-permissions",
"content": [
"|Apr 27, 2022",
"|Breaking changes",
"|Other changes"
],
"Apr 27, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#updated-command-permissions-apr-27,-2022",
"content": [
"Application command permissions have been updated to add more granular control and access to commands in Discord. You can read the major changes below, and the updated documentation for details."
]
},
"Breaking changes": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#updated-command-permissions-breaking-changes",
"content": [
[
"Bearer tokens are now required to edit command permissions. Bearer tokens are tokens tied to an authenticating user's permissions, and can be retrieved using OAuth. The user must have permission to manage the guild and roles.",
"applications.commands.permissions.update scope was added as a requirement to edit command permissions.",
"Disabled the batch editing endpoint (PUT /applications/{application.id}/guilds/{guild.id}/commands/permissions)."
]
]
},
"Other changes": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#updated-command-permissions-other-changes",
"content": [
[
"Created a CHANNEL command permission type",
"Increase permission limit from 10 to 100",
"constant (guild_id - 1) to represent all channels in command permissions",
"Added default_member_permissions field, which is a bitwise OR-ed set of permissions, expressed as a string. This replaces the default_permission field, which will soon be deprecated.",
"Added dm_permission, which is a boolean flag used to indicate whether a command is available in DMs (only for global application commands). If no value is passed, the global command will be visible in DMs.",
"Added APPLICATION_COMMAND_PERMISSIONS_UPDATE gateway event and APPLICATION_COMMAND_PERMISSION_UPDATE audit log event."
]
]
}
},
"Forum Channels": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#forum-channels",
"content": [
"|Apr 06, 2022"
],
"Apr 06, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#forum-channels-apr-06,-2022",
"content": [
"Added new channel type, GUILD_FORUM (15). A GUILD_FORUM channel is an unreleased feature that is very similar (from an API perspective) to a GUILD_TEXT channel, except only threads can be created in that channel; messages cannot be sent directly in that channel. Check out the forums topic for more information."
]
}
},
"Guild Bans Pagination": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#guild-bans-pagination",
"content": [
"|Mar 31, 2022"
],
"Mar 31, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#guild-bans-pagination-mar-31,-2022",
"content": [
"The GET /guilds/{guild.id}/bans endpoint has been migrated to require pagination to improve reliability and stability. Check out the endpoint docs for more information."
]
}
},
"API v10": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#api-v10",
"content": [
"|Feb 14, 2022",
"|Upcoming changes"
],
"Feb 14, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#api-v10-feb-14,-2022",
"content": [
[
"API v8 is now deprecated.",
"GET /channels/{channel.id}/threads/active is decommissioned in favor of GET /guilds/{guild.id}/threads/active.",
"Starting in v10, you must specify the message content intent (1 << 15) to receive content-related fields in message dispatches. Read more in the Gateway Intents documentation.",
"To specify a reason for an administrative action in audit logs, apps must now pass the X-Audit-Log-Reason header rather than the reason parameter for all endpoints. Read more in the Audit Logs documentation.",
"Message routes (like POST /channels/{channel.id}/messages) now use the embeds field (an array of embed objects) instead of embed.",
"The summary field for applications now returns an empty string for all API versions.",
"The name and description fields for Achievements are now strings, and localization info is now passed in new name_localizations and description_localizations dictionaries. This change standardizes localization to match Application Commands. Read details in the Achievements documentation.",
"Existing attachments must be specified when PATCHing messages with new attachments. Any attachments not specified will be removed and replaced with the specified list",
"Requests to v10 and higher will no longer be supported on discordapp.com (this does not affect cdn.discordapp.com)"
]
]
},
"Upcoming changes": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#api-v10-upcoming-changes",
"content": [
[
"API v6 and v7 will be decommissioned in early 2023",
"MESSAGE_CONTENT is becoming a privileged intent for verified bots in 75+ servers on August 31, 2022. Read details in the FAQ or follow the guide on updating your app.",
"The summary field for applications will be removed in the next API version (v11)"
]
]
}
},
"Interaction Modals and Application Command Attachment Option Type": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#interaction-modals-and-application-command-attachment-option-type",
"content": [
"|Feb 8, 2022"
],
"Feb 8, 2022": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#interaction-modals-and-application-command-attachment-option-type-feb-8,-2022",
"content": [
"Interaction modals are now available, allowing applications to prompt users for further detailed input. Check out the modal docs for more information.",
"Application Commands can now add an attachment option type. See the option type table for more information."
]
}
},
"Guild Member Timeouts": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#guild-member-timeouts",
"content": [
"|Dec 20, 2021"
],
"Dec 20, 2021": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#guild-member-timeouts-dec-20,-2021",
"content": [
"Add new documentation for the recently released guild member timeout feature."
]
}
},
"Guild Scheduled Events": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#guild-scheduled-events",
"content": [
"|Nov 23, 2021",
"|Nov 18, 2021",
"|Nov 15, 2021"
],
"Nov 23, 2021": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#guild-scheduled-events-nov-23,-2021",
"content": [
[
"Add official support for guild_scheduled_events field on Guild resource sent with GUILD_CREATE event"
]
]
},
"Nov 18, 2021": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#guild-scheduled-events-nov-18,-2021",
"content": [
[
"Breaking change for return type for GET /guilds/{guild.id}/scheduled-events/{guild_scheduled_event.id}/users",
"Add with_user_count query param for GET /guilds/{guild.id}/scheduled-events/{guild_scheduled_event.id}",
"Return additional creator field by default in response for GET /guilds/{guild.id}/scheduled-events/{guild_scheduled_event.id}",
"More details and clarification for the guild scheduled events feature.",
"Document support for before and after query params for GET /guilds/{guild.id}/scheduled-events/{guild_scheduled_event.id}/users"
]
]
},
"Nov 15, 2021": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#guild-scheduled-events-nov-15,-2021",
"content": [
"Add new documentation for the recently released Guild Scheduled Events feature."
]
}
},
"Application Command Autocomplete Interactions": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#application-command-autocomplete-interactions",
"content": [
"|October 27, 2021"
],
"October 27, 2021": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#application-command-autocomplete-interactions-october-27,-2021",
"content": [
"Autocomplete interactions are now available, allowing application commands to provide server completed options. Check out the autocomplete interaction docs for more information."
]
}
},
"Updated Thread Permissions": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#updated-thread-permissions",
"content": [
"|September 16, 2021"
],
"September 16, 2021": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#updated-thread-permissions-september-16,-2021",
"content": [
"Thread permissions have been updated and simplified:",
[
"\"Use Public Threads\" is now \"Create Public Threads\", which allows users to create public threads and announcement threads in a channel, even if they cannot send messages in that channel.",
"\"Use Private Threads\" is now \"Create Private Threads\", which allows users to create private threads in a channel, even if they cannot send messages in that channel."
],
"A new permission has also been added:",
[
"\"Send Messages in Threads\", which allows users to send a message in a thread. The \"Send Messages\" permission has no effect in threads: users must have \"Send Messages in Threads\" to send a message in a thread. This allows for setups where a user can participate in a thread but cannot send a message in the parent channel (like a thread on an announcement post)."
]
]
}
},
"User and Message Commands": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#user-and-message-commands",
"content": [
"|August 10, 2021"
],
"August 10, 2021": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#user-and-message-commands-august-10,-2021",
"content": [
"User commands and message commands are now live! These commands appear on context menus for users and messages, with more to come in the future.",
"Context menu commands are a type of application command. The \"Slash Commands\" documentation page has been renamed to \"Application Commands\" and split out by type to show this."
]
}
},
"Select Menu Components": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#select-menu-components",
"content": [
"|June 30, 2021"
],
"June 30, 2021": {
"level": 4,
"url": "https://discord.com/developers/docs/docs/change-log#select-menu-components-june-30,-2021",
"content": [
"Select Menus are now part of the components API! They're the greatest thing since the invention of buttons yesterday. Select menus allow you to offer users a choice of one or many options in a friendly UI-based way.",
"Select menus can be used like other message components. Learn all the specifics in the documentation."
]
}
},
"Support for Multiple Embeds in Message Routes": {
"level": 2,
"url": "https://discord.com/developers/docs/docs/change-log#support-for-multiple-embeds-in-message-routes",
"content": [
"|June 10, 2021"