Discord Client Modding Wiki - User contributions [en]

Powercord

2024-06-23T08:35:11Z

Katlyn: formatting fixes

{{Infobox mod
| name = Powercord
| logo = Powercord Logo.png
| logoCaption = Powercord Logo
| yearsActive = November 2018 - July 2022
| platforms = Desktop
| developers = [[aetheryx]]
| licenses = MIT
| repo = [https://github.com/powercord-org/Powercord powercord-org/Powercord]
| languages = [https://en.wikipedia.org/wiki/Node.js Node.js]
}}
Powercord was a client mod created by [[aetheryx]]. It was declared end of life in 2019, and a maintained version was forked to later become [[Replugged]].

==History==
[[aetheryx]] created the first commit on April 11, 2018<ref>GitHub commit "Initial commit": https://github.com/powercord-org/powercord/commit/603f2bbf3112efd2365b3f3bcd439b838a8cadcd</ref>. It was intended to be a personal client mod and was hosted at [https://github.com/aetheryx/aethcord aetheryx/aethcord]. The v1 branch was discontinued on January 5, 2019<ref>GitHub commit "Update README.md": https://github.com/powercord-org/powercord/commit/7fa4d989668b7cd504577891c84e9473c5f58283</ref>. The v2 branch became the main branch until Powercord was declared end of life in 2022. Powercord v3 was announced but did not come to fruition.

=== Initial Previews ===
[[File:Atheryx's original Spotify-Discord integration.png|thumb|The first screenshot of what would later become Powercord.]]
On November 25, 2018 [[aetheryx]] posted an initial screenshot of a Spotify integration for Discord in the [[DTinker]] client modding community's #showcase channel<ref>Discord message from aetheryx in DTinker #showcase. https://discord.com/channels/257299803397029899/257343240120827904/516396560549150730</ref>. This was the very first version of what is now implemented in modern plugins Such as Vencord's [https://vencord.dev/plugins/SpotifyControls SpotifyControls] or [[DevilBro]]'s [[BetterDiscord]] [https://github.com/mwittrien/BetterDiscordAddons/tree/master/Plugins/SpotifyControls plugin by the same name]. This garnered interest from several users and over the course of the next few days, aetheryx shared more information, including a link to the GitHub repository. At that time, the repository was located at [https://github.com/aetheryx/aethcord aetheryx/aethcord]. aetheryx expressed views early-on about how he wasn't a fan of the initial name, stating "[...] things are in extremely early stages right now and i need to think of a better name than <code>aethcord</code>"<ref>Discord message from aetheryx in DTinker #showcase. https://discord.com/channels/257299803397029899/257343240120827904/517121645173932037</ref> and "it just feels a little too dorky/awkward tbh. like i literally just merged my username with <code>discord</code>"<ref>Discord message from aetheryx in DTinker #showcase. https://discord.com/channels/257299803397029899/257343240120827904/517360125162291201</ref>.

Development of aethcord continued in aetheryx's own personal Discord guild.

=== Rename to Powercord ===
aetheryx stated an intention to rename the project to "Powercord" on November 30, 2018 , with the following reasoning<ref>Discord message from aetheryx in not aeth's server #powercord. https://discord.com/channels/299979631715549184/517348857219383308/518224615013613569</ref>:<blockquote>the name i'm currently intending on picking is <code>powercord</code>

because

# aethcords end goal is to appeal to power users
# it's a pun
# it ends in <code>-cord</code> which i think is pretty important for a client mod
and for those of you who want to know, we're dropping <code>aethcord</code> because i think it's cringe to have my own name on the project like that and it's not fair to other contributors who work on the project</blockquote>Several users stated their distaste with the proposed name, with messages such as "powercord is a bad name"<ref>Discord message from mrlar in not aeth's server #powercord. https://discord.com/channels/299979631715549184/517348857219383308/519560153951895552</ref> and "im starting to think you're really bad with names."<ref>Discord message from pwa in not aeth's server #cool-people. https://discord.com/channels/299979631715549184/518976704887390218/519253344150224916</ref> Despite the mixed reception, Powercord became the official name of the project on December 7, 2018<ref>GitHub commit "rename project to powercord". https://github.com/powercord-org/powercord/commit/9c64db367054f945023e08f845be4d55f2cff8bf</ref>.
[[Category:Client Mods]]

Powercord

2024-06-23T08:32:39Z

Katlyn: Add information about Powercord's rename from aethcord.

{{Infobox mod
| name = Powercord
| logo = Powercord Logo.png
| logoCaption = Powercord Logo
| yearsActive = November 2018 - July 2022
| platforms = Desktop
| developers = [[aetheryx]]
| licenses = MIT
| repo = [https://github.com/powercord-org/Powercord powercord-org/Powercord]
| languages = [https://en.wikipedia.org/wiki/Node.js Node.js]
}}
Powercord was a client mod created by [[aetheryx]]. It was declared end of life in 2019, and a maintained version was forked to later become [[Replugged]].

==History==
[[aetheryx]] created the first commit on April 11, 2018<ref>GitHub commit "Initial commit": https://github.com/powercord-org/powercord/commit/603f2bbf3112efd2365b3f3bcd439b838a8cadcd</ref>. It was intended to be a personal client mod and was hosted at [https://github.com/aetheryx/aethcord aetheryx/aethcord]. The v1 branch was discontinued on January 5, 2019<ref>GitHub commit "Update README.md": https://github.com/powercord-org/powercord/commit/7fa4d989668b7cd504577891c84e9473c5f58283</ref>. The v2 branch became the main branch until Powercord was declared end of life in 2022. Powercord v3 was announced but did not come to fruition.

=== Initial Previews ===
[[File:Atheryx's original Spotify-Discord integration.png|thumb|The first screenshot of what would later become Powercord.]]
On November 25, 2018 [[aetheryx]] posted an initial screenshot of a Spotify integration for Discord in the [[DTinker]] client modding community's #showcase channel<ref>Discord message from aetheryx in DTinker #showcase. https://discord.com/channels/257299803397029899/257343240120827904/516396560549150730</ref>. This was the very first version of what is now implemented in modern plugins Such as Vencord's [https://vencord.dev/plugins/SpotifyControls SpotifyControls] or [[DevilBro]]'s [[BetterDiscord]] [https://github.com/mwittrien/BetterDiscordAddons/tree/master/Plugins/SpotifyControls plugin by the same name]. This garnered interest from several users and over the course of the next few days, aetheryx shared more information, including a link to the GitHub repository. At that time, the repository was located at [https://github.com/aetheryx/aethcord aetheryx/aethcord]. aetheryx expressed views early-on about how he wasn't a fan of the initial name, stating "[...] things are in extremely early stages right now and i need to think of a better name than <code>aethcord</code>"<ref>Discord message from aetheryx in DTinker #showcase. https://discord.com/channels/257299803397029899/257343240120827904/517121645173932037</ref> and "it just feels a little too dorky/awkward tbh. like i literally just merged my username with <code>discord</code>"<ref>Discord message from aetheryx in DTinker #showcase. https://discord.com/channels/257299803397029899/257343240120827904/517360125162291201</ref>.

Development of aethcord continued in aetheryx's own personal Discord guild.

=== Rename to Powercord ===
aetheryx stated an intention to rename the project to "Powercord" on November 30, 2018 , with the following reasoning<ref>Discord message from aetheryx in not aeth's server #powercord. https://discord.com/channels/299979631715549184/517348857219383308/518224615013613569</ref>:<blockquote>the name i'm currently intending on picking is <code>powercord</code>

because

# aethcords end goal is to appeal to power users
# it's a pun
# it ends in <code>-cord</code> which i think is pretty important for a client modand for those of you who want to know, we're dropping <code>aethcord</code> because i think it's cringe to have my own name on the project like that and it's not fair to other contributors who work on the project</blockquote>Several users stated their distaste with the proposed name, with messages such as "powercord is a bad name"<ref>Discord message from mrlar in not aeth's server #powercord. https://discord.com/channels/299979631715549184/517348857219383308/519560153951895552</ref> and "im starting to think you're really bad with names."<ref>Discord message from pwa in not aeth's server #cool-people. https://discord.com/channels/299979631715549184/518976704887390218/519253344150224916</ref> Despite the mixed reception, Powercord became the official name of the project on December 7, 2018<ref>GitHub commit "rename project to powercord". https://github.com/powercord-org/powercord/commit/9c64db367054f945023e08f845be4d55f2cff8bf</ref>.
[[Category:Client Mods]]

File:Wing's mismanagement of company funds..png

2024-04-03T02:40:04Z

Katlyn: Katlyn moved page File:Wing's mismanagement of company funds..png to File:Wing's mismanagement of company funds.png: Misspelled title

#REDIRECT [[File:Wing's mismanagement of company funds.png]]

File:Wing's mismanagement of company funds.png

2024-04-03T02:40:04Z

Katlyn: Katlyn moved page File:Wing's mismanagement of company funds..png to File:Wing's mismanagement of company funds.png: Misspelled title

Wing's mismanagement of company funds.

Bundler Updates

2024-03-23T22:17:49Z

Katlyn:

Discord uses a bundler to compress individual files into bigger, singular files known as chunks. This article documents major and minor changes to the bundler or its config over the years that have caused client mods to break.

== Unique CSS class names ==
Starting on June 1, 2017, Discord introduced a bundler plugin that made CSS class names unique by adding a 6-character hash string at the end of the class. The change was gradual and impacted only the guild channels wrapper at first, but over a short period of time hashed class names became used throughout the entire client.

== 1000 character line splitting ==
On July 29, 2021, Discord added a [https://babeljs.io/ Babel] rule to split every line of code into 1000 characters within the limits of syntax. At the time, no public client mods broke because none searched modules by code or used module patching.

== Webpack 5 ==
On October 21, 2021, Discord updated from [https://webpack.js.org/ Webpack] 4 to 5. This introduced lazy-loaded chunks and WebAssembly support.

The Webpack global was renamed from <code>webpackJsonp</code> to <code>webpackChunkdiscord_app</code>.
Entrypoint modules were changed from an array of module IDs to a function with Webpack's <code>require</code> function as the only argument.

== SWC ==
On September 26, 2022, Discord switched from Babel to [https://swc.rs/ SWC]. This is considered the great cataclysmic event that killed off almost every client mod.

React component display names were removed, making it harder for mods to find components. There were plans for Discord to find a way to keep display names for debugging purposes<ref>{{cite web|title=Ability to add displayName to all React components to prevent names from getting mangled|url=https://github.com/swc-project/swc/issues/5958}}</ref>, but they opted not to bother<ref>{{cite web|title="We might just stick with not having displayNames"|url=https://github.com/swc-project/swc/issues/5958#issuecomment-1258764673}}</ref>.

Module export names were mangled. Finding specific functions without searching for the function's code was even harder. There were specific patterns, such as <code>default</code> becoming <code>Z</code> or <code>ZP</code>.

== Rspack ==
On October 26, 2023, Discord switched from Webpack to [https://www.rspack.dev/ Rspack]. While not as cataclysmic, it wasn't without issues.

Module export names return. This caused parts of mods broken by SWC to work in some capacity, excluding React component display names.

Every theme was now broken as Rspack's unique class name plugin uses <code>_</code> or <code>__</code> as the separator between the name and the random string. In addition, every stylesheet was loaded in the body instead of the head, forcing client mods to put their stylesheets in <code>document.documentElement</code> for the highest priority.

More than 100 chunk files are initially loaded instead of 4.

[https://sentry.io Sentry]'s chunk would overwrite the module storage, causing two instances of modules to exist but only one to be accessible.


The chunk loader chunk loads later than expected, forcing mods that use module patching to disregard further calls to binding <code>webpackChunkdiscord_app.push</code>.

== Accidental Early Rspack testing on production ==
On September 29, 2023, a build on Canary was released that broke everything. It was not known at the time this was Rspack. It was using a non-production-ready config.

Chunk names were not transformed into numbers, which leaked some file names. An example name would be <code>defaultVendors~node_modules_lodash_lodash_js~_36ba</code>.

Script tags had the <code>defer</code> property set, causing loading race conditions in some mods.

== Config Issues ==
'''Config issues''' refer to minor changes to the config as opposed to entire bundler updates.

=== iOS CI ===
[[File:iOS_Revert_Times.png|thumb|A message of a (Discord?) moderator (in the TestFlight server?) confirming that iOS CI builds being pushed to Canary weren't intentional and had to be reverted. Also confirming Discord's build times at the time]]
At the beginning of August 2021, Discord had an older CI for iOS builds that would push builds to Canary that would have to be reverted.

=== ES version indecisiveness ===
'''[[wikipedia:ECMAScript|ECMAScript]]''' is a standard for scripting languages, namely JavaScript. It was formerly numerically versioned but is now versioned by year.
Targeting a specific version tells the bundler what modern features need to be transpiled to compatible features supported by that version.

Changing this version breaks mods that use module patching.

==== December 21, 2023 ====
The targeted version was downgraded to what it was set to pre-Rspack (ES5?). It was reverted and unreverted several times within a 3-hour window.

[[Vendicated|Vee]] messaged Discord developer Brandon (aweary) about it, and it was confirmed as unintentional.

==== February 28, 2024 ====
The targeted version was bumped to ES 2020 or newer. It was reverted within 24 hours.

[[Category:Drama & Incidents]]

Bundler Updates

2024-03-23T19:03:46Z

Katlyn:

__NOTOC__
Discord uses a bundler to compress individual files into bigger, singular files known as chunks. This article documents major and minor changes to the bundler or its config over the years that have caused client mods to break.

== Unique CSS class names ==
Starting on June 1, 2017, Discord introduced a bundler plugin that made CSS class names unique by adding a 6-character hash string at the end of the class. The change was gradual and impacted only the guild channels wrapper at first, but over a short period of time hashed class names became used throughout the entire client.

== 1000 character line splitting ==
On July 29, 2021, Discord added a [https://babeljs.io/ Babel] rule to split every line of code into 1000 characters within the limits of syntax. At the time, no public client mods broke because none searched modules by code or used module patching.

== Webpack 5 ==
On October 21, 2021, Discord updated from [https://webpack.js.org/ Webpack] 4 to 5. This introduced lazy-loaded chunks and WebAssembly support.

The Webpack global was renamed from <code>webpackJsonp</code> to <code>webpackChunkdiscord_app</code>.
Entrypoint modules were changed from an array of module IDs to a function with Webpack's <code>require</code> function as the only argument.

== SWC ==
On September 26, 2022, Discord switched from Babel to [https://swc.rs/ SWC]. This is considered the great cataclysmic event that killed off almost every client mod.

React component display names were removed, making it harder for mods to find components.
There were plans for Discord to find a way to keep display names for debugging purposes<ref>{{cite web|title=Ability to add displayName to all React components to prevent names from getting mangled|url=https://github.com/swc-project/swc/issues/5958}}</ref>, but they opted not to bother<ref>{{cite web|title="We might just stick with not having displayNames"|url=https://github.com/swc-project/swc/issues/5958#issuecomment-1258764673}}</ref>.

Module export names were mangled. Finding specific functions without searching for the function's code was even harder. There were specific patterns, such as <code>default</code> becoming <code>Z</code> or <code>ZP</code>.

== Rspack ==
On October 26, 2023, Discord switched from Webpack to [https://www.rspack.dev/ Rspack]. While not as cataclysmic, it wasn't without issues.

Module export names return. This caused parts of mods broken by SWC to work in some capacity, excluding React component display names.

Every theme was now broken as Rspack's unique class name plugin uses <code>_</code> or <code>__</code> as the separator between the name and the random string.
In addition, every stylesheet was loaded in the body instead of the head, forcing client mods to put their stylesheets in <code>document.documentElement</code> for the highest priority.

More than 100 chunk files are initially loaded instead of 4.

[https://sentry.io Sentry]'s chunk would overwrite the module storage, causing two instances of modules to exist but only one to be accessible.


The chunk loader chunk loads later than expected, forcing mods that use module patching to disregard further calls to binding <code>webpackChunkdiscord_app.push</code>.

== Accidental Early Rspack testing on production ==
On September 29, 2023, a build on Canary was released that broke everything. It was not known at the time this was Rspack. It was using a non-production-ready config.

Chunk names were not transformed into numbers, which leaked some file names. An example name would be <code>defaultVendors~node_modules_lodash_lodash_js~_36ba</code>.

Script tags had the <code>defer</code> property set, causing loading race conditions in some mods.

== Config Issues ==
'''Config issues''' refer to minor changes to the config as opposed to entire bundler updates.

=== iOS CI ===
[[File:iOS_Revert_Times.png|thumb|A message of a (Discord?) moderator (in the TestFlight server?) confirming that iOS CI builds being pushed to Canary weren't intentional and had to be reverted. Also confirming Discord's build times at the time]]
At the beginning of August 2021, Discord had an older CI for iOS builds that would push builds to Canary that would have to be reverted.

=== ES version indecisiveness ===
'''[[wikipedia:ECMAScript|ECMAScript]]''' is a standard for scripting languages, namely JavaScript. It was formerly numerically versioned but is now versioned by year.
Targeting a specific version tells the bundler what modern features need to be transpiled to compatible features supported by that version.

Changing this version breaks mods that use module patching.

==== December 21, 2023 ====
The targeted version was downgraded to what it was set to pre-Rspack (ES5?). It was reverted and unreverted several times within a 3-hour window.

[[Vendicated|Vee]] messaged Discord developer Brandon (aweary) about it, and it was confirmed as unintentional.

==== February 28, 2024 ====
The targeted version was bumped to ES 2020 or newer. It was reverted within 24 hours.

[[Category:Drama & Incidents]]

Bundler Updates

2024-03-23T19:02:42Z

Katlyn:

__NOTOC__
Discord uses a bundler to compress individual files into bigger, singular files known as chunks. This article documents major and minor changes to the bundler or its config over the years that have caused client mods to break.

== Unique CSS class names ==
Starting on June 1, 2017, Discord introduced a bundler plugin that made CSS class names unique by adding a 6-character hash string at the end of the class. The change was gradual an impacted only the guild channels wrapper at first, but over time hashed class names became used throughout the entire client.

== 1000 character line splitting ==
On July 29, 2021, Discord added a [https://babeljs.io/ Babel] rule to split every line of code into 1000 characters within the limits of syntax. At the time, no public client mods broke because none searched modules by code or used module patching.

== Webpack 5 ==
On October 21, 2021, Discord updated from [https://webpack.js.org/ Webpack] 4 to 5. This introduced lazy-loaded chunks and WebAssembly support.

The Webpack global was renamed from <code>webpackJsonp</code> to <code>webpackChunkdiscord_app</code>.
Entrypoint modules were changed from an array of module IDs to a function with Webpack's <code>require</code> function as the only argument.

== SWC ==
On September 26, 2022, Discord switched from Babel to [https://swc.rs/ SWC]. This is considered the great cataclysmic event that killed off almost every client mod.

React component display names were removed, making it harder for mods to find components.
There were plans for Discord to find a way to keep display names for debugging purposes<ref>{{cite web|title=Ability to add displayName to all React components to prevent names from getting mangled|url=https://github.com/swc-project/swc/issues/5958}}</ref>, but they opted not to bother<ref>{{cite web|title="We might just stick with not having displayNames"|url=https://github.com/swc-project/swc/issues/5958#issuecomment-1258764673}}</ref>.

Module export names were mangled. Finding specific functions without searching for the function's code was even harder. There were specific patterns, such as <code>default</code> becoming <code>Z</code> or <code>ZP</code>.

== Rspack ==
On October 26, 2023, Discord switched from Webpack to [https://www.rspack.dev/ Rspack]. While not as cataclysmic, it wasn't without issues.

Module export names return. This caused parts of mods broken by SWC to work in some capacity, excluding React component display names.

Every theme was now broken as Rspack's unique class name plugin uses <code>_</code> or <code>__</code> as the separator between the name and the random string.
In addition, every stylesheet was loaded in the body instead of the head, forcing client mods to put their stylesheets in <code>document.documentElement</code> for the highest priority.

More than 100 chunk files are initially loaded instead of 4.

[https://sentry.io Sentry]'s chunk would overwrite the module storage, causing two instances of modules to exist but only one to be accessible.


The chunk loader chunk loads later than expected, forcing mods that use module patching to disregard further calls to binding <code>webpackChunkdiscord_app.push</code>.

== Accidental Early Rspack testing on production ==
On September 29, 2023, a build on Canary was released that broke everything. It was not known at the time this was Rspack. It was using a non-production-ready config.

Chunk names were not transformed into numbers, which leaked some file names. An example name would be <code>defaultVendors~node_modules_lodash_lodash_js~_36ba</code>.

Script tags had the <code>defer</code> property set, causing loading race conditions in some mods.

== Config Issues ==
'''Config issues''' refer to minor changes to the config as opposed to entire bundler updates.

=== iOS CI ===
[[File:iOS_Revert_Times.png|thumb|A message of a (Discord?) moderator (in the TestFlight server?) confirming that iOS CI builds being pushed to Canary weren't intentional and had to be reverted. Also confirming Discord's build times at the time]]
At the beginning of August 2021, Discord had an older CI for iOS builds that would push builds to Canary that would have to be reverted.

=== ES version indecisiveness ===
'''[[wikipedia:ECMAScript|ECMAScript]]''' is a standard for scripting languages, namely JavaScript. It was formerly numerically versioned but is now versioned by year.
Targeting a specific version tells the bundler what modern features need to be transpiled to compatible features supported by that version.

Changing this version breaks mods that use module patching.

==== December 21, 2023 ====
The targeted version was downgraded to what it was set to pre-Rspack (ES5?). It was reverted and unreverted several times within a 3-hour window.

[[Vendicated|Vee]] messaged Discord developer Brandon (aweary) about it, and it was confirmed as unintentional.

==== February 28, 2024 ====
The targeted version was bumped to ES 2020 or newer. It was reverted within 24 hours.

[[Category:Drama & Incidents]]

Powercord

2024-03-23T18:43:29Z

Katlyn: Correct typos of aeth's name

File:Powercord Logo.png

2024-03-23T08:26:47Z

Katlyn: Credit logo creation.

File:Powercord Logo.png

2024-03-23T08:23:04Z

Katlyn: Katlyn uploaded a new version of File:Powercord Logo.png

Powercord Logo

Powercord

2024-03-23T08:01:55Z

Katlyn: Add additional information to the early days of Powercord.

File:Atheryx's original Spotify-Discord integration.png

2024-03-23T06:49:28Z

Katlyn:

A screenshot of the first iteration of [[aetheryx]]'s Spotify integration for Discord, posted November 25, 2018. See: https://discord.com/channels/257299803397029899/257343240120827904/516396560549150730

Client Mod Drama Generator

2024-03-23T06:06:07Z

Katlyn: Update GitHub link to point to Archive.org

Program by [[ Ruthenic ]] to generate Discord drama. Originally [https://web.archive.org/web/20220724083936/https://github.com/Ruthenic/dramaGenerator hosted on GitHub], but later deleted. Still accessible and privately maintained in [[Biscord]]'s /drama command.

==Examples==
* Aspy sees Astra as a massive improvement over OpenCord, and Samm-Cheese goes crazy.
* Void gets banned by Discord. The CutTheCord community is in shambles.
* A user rewrites Bluecord in Python, causing massive outrage from Fiery.

[[Category:Drama & Incidents]]

User:Katlyn

2024-03-21T00:20:53Z

Katlyn: Created page with "foxes neat"

foxes neat