From 3fa53f5e1dd410231eb9f8f2f2d142e8b4b6961c Mon Sep 17 00:00:00 2001 From: Shadow Date: Wed, 18 Sep 2024 18:26:52 -0500 Subject: [PATCH] docs: forgot the number lol --- website/content/carbon/even-more/why-classes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/carbon/even-more/why-classes.mdx b/website/content/carbon/even-more/why-classes.mdx index ad13e17a..b04954eb 100644 --- a/website/content/carbon/even-more/why-classes.mdx +++ b/website/content/carbon/even-more/why-classes.mdx @@ -89,7 +89,7 @@ As you can see, this setup is very similar to how Carbon works today, and this c ### Carbon -Now we get to Carbon. I spent about ??? months designing and building the initial version of Carbon, bouncing feedback and ideas off of Codeize, and it was a lot different than building out our internal bot's methods, but used the same concepts and ideas. Whenever I added a new feature, extendability and modularity were always a priority, and I wanted to make sure that Carbon was as easy to use as possible. +Now we get to Carbon. I spent about 5 months (off and on) designing and building the initial version of Carbon, bouncing feedback and ideas off of Codeize, and it was a lot different than building out our internal bot's methods, but used the same concepts and ideas. Whenever I added a new feature, extendability and modularity were always a priority, and I wanted to make sure that Carbon was as easy to use as possible. Every part of Carbon is built to be extendable. Want to add something to the client yourself? Just extend the client with your own properties and methods! Want to add extra properties to commands? Just extend them and add a custom constructor!