Uploaded April 2020 | Updated September 2026, 2 weeks ago

---

Over the past several years, I've had a weird & frankly pretty bad way of handling Requests. To put it simply: I handled Requests like they were Suggestions where I would pick & choose which ones to do based off if I liked the idea and/or was already going to do the same idea.
That said, I've only done a few Requests in general and even then some barely count because they were ideas I was already going to do.

The main reason I handled these like Suggestions (without actually realizing it at the time) was because I am very inconsistent with working on my own projects. I have a short attention span and I'm a perfectionist so I always put in a ton of effort to the things I make but will take multiple breaks of varying lengths because of my interest & motivation jumping around.
When I start to lose interest in a project, I begin to fall into the "just get it done" mindset where I will ignore mistakes/issues as well as cut corners. Not only does that lower the quality of final product but I get annoyed & frustrated looking back at product. It makes me want to go back & fix things & in some cases completely redo stuff if it was rushed.
Since this usually happens much later, I've found it better to just take a break from a project when I stop putting in 100 or more % effort to avoid having to redo things later. As previously mentioned though, there can be several breaks causing a project to take a while to complete. I, and probably a lot of my subscribers, can think of multiple instances like this. I am not trying to sound proud of any of this, just stating facts.

Obviously this is not a good thing to do when handling Requests because it forces the person who asked for it to wait longer than expected. Although I have had the foresight to just ignore & deny multiple requests, there has been one request I took where the person was very patient with me and another where the person wasn't so patient.

Those two were the main motivators for me finally getting around to making an official video regarding Requests as well as helping me decide what to actually do since I've had a flimsy way of going about this:

I am not taking any more Requests from this point on, and by extension I am never taking a Commission.

Commissions are basically Requests that also involve money which unlike other people, would not motivate me to get stuff done faster...or well it would motivate me but the quality would certainly decrease over time. There's also the issue of calculating payment based off time to complete the thing which with the whole thing about my motivation would run into issues. Also in general everything is more complicated when money is involved.

It's just better if I never accept a Commission, on the plus side that means nothing I make is ever motivated by money. Everything I make & release has some level of passion put into it, if not full of passion because that's what my stuff is: Passion Projects

Nobody paid me to make something I didn't want to do, the few Requests I have done over the past several years were because I really liked those ideas so there was always something about the idea that I enjoyed.

Now since I've been comparing my bad method of handling Requests to what Suggestions are, might as well say my new stance on that:

You can suggest me things but most of the time I'm going to ignore them.

If I do the suggestion it's either because I already had the idea or I added it as a part of a project I was already working on which then I'll give credit. Occasionally I get suggested things that are simply too good to ignore & it wouldn't be fair for me to act like I came up with the idea on my own.

I should've done this years ago but at least now I have the hindsight, foresight & frankly just enough experience to know that THIS is how I'm going to handle things from now on.