Client enums Bit flags
UserFlags
Bits in user.flags and public_flags. Values are bit positions; copy gives the decimal value.
| Status | ||
|---|---|---|
| 0x1 · 1 | In docs | |
| 0x2 · 2 | In docs | |
| 0x4 · 4 | In docs | |
| 0x8 · 8 | In docs | |
| 0x10 · 16 | Not in docs | |
| 0x20 · 32 | Not in docs | |
| 0x40 · 64 | In docs | |
| 0x80 · 128 | In docs | |
| 0x100 · 256 | In docs | |
| 0x200 · 512 | In docs | |
| 0x2000 · 8192 | Not in docs | |
| 0x4000 · 16384 | In docs | |
| 0x10000 · 65536 | In docs | |
| 0x20000 · 131072 | In docs | |
| 0x40000 · 262144 | In docs | |
| 0x80000 · 524288 | In docs | |
| 0x100000 · 1048576 | Not in docs | |
| 0x200000 · 2097152 | Not in docs | |
| 0x800000 · 8388608 | Not in docs | |
| 0x100000000000 · 17592186044416 | Not in docs | |
| 0x4000000000000 · 1125899906842624 | Not in docs | |
| 0x8000000000000 · 2251799813685248 | Not in docs |
No members match that. Try part of the name, or a value.
Read from the client entry bundle (current.js in Discord-Datamining) at build 669021. Member names and values are exactly what the client ships; the enum name is ours.
"Not in docs" means the value is missing from the reference table, which follows the official API docs; a member listed there under another name still counts as documented. Read Nov 9, 16:51 UTC.