Home Creators Posts Import Register Favorites Logout

Content

Hey! I’ve been working on some communication and request handling tasks, and I’ve already managed to post a few previews—hope they look decent :D

I’ve also updated the request queue spreadsheet: https://docs.google.com/spreadsheets/d/16mB8KbHLEE9R7FrWVfs5LdxgEdsQARwZMfzMBtt4quo/edit?usp=sharing

I made a few changes to its layout. The main change is probably the addition of "statuses", which I’ve explained in more detail directly in the spreadsheet.

Here are a few notes about things that might be important:

  • This spreadsheet primarily exists for my own convenience, so some of the things in it might not make much sense to others (that’s intentional :D). However, it’s also accessible for anyone to view for the following reasons:

    • If you’ve made a request, you can check its status and details (specs may vary since some members use forms while others don’t). If needed, you can clarify anything (Preferably in DMs).

    • You can get a rough idea of what’s coming up and when it’ll be published.

    • It might be interesting for some people to compare the request specs with the final results.

  • The schedule for set releases and the queue itself are now working a bit differently than before—let’s call it a bit more "chaotic" :D This is mostly due to the addition of previews and more "parallel" workflow.

  • You might notice there are more requests in the spreadsheet than there were slots available in the new tier. That’s because I also tested selling a few slots to DeviantArt users. Since DeviantArt doesn’t have a Max+ tier, this was done via the local shop, which was an interesting experiment. (And not the most successful one, by the way :D)

P.S. The first full sets for the requests (as well as the Yoruichi x Rukia set for [Max]) will be released this weekend. I’m aiming to get the content schedule back to something more regular starting this weekend, meaning full sets should be coming out more or less daily.

Comments

No comments found for this post.