Pivity

Dev blog 04/05/2018 - Tickets, addon teams and knowledge bases

Last read Never
#1

Dev blog 04/05/2018

In this dev blog I will be going over changes to the support ticket system, the addon knowledge bases, the new addon teams and a little bit about the new addon submission system.


Addon teams

The first thing content creators will notice when the new update comes out is that addons are no longer owned by a single user. They're owned by a team. This is a change we've made for several reasons, one is because it's easier from a legal document standpoint to refer to a single entity (i.e a team) instead of several authors.

The addon teams are automatically generated by us as we switch to the next version of GmodStore. They are based on the current authors of an addon and their cut %. If they have the same across multiple addons and the authors are the same, then they will share a single team all the way. The team owner is the primary author of the addon.

Another reason is so that addons can actually be transferrable. That's right! You can transfer addons between teams you are a member of. The commission rate is based on the team owner's total revenue. This also means that not only can you transfer addons, but you can also transfer teams.

When submitting an addon you are also greeted with a dropdown to select a team to assign the addon to. You also have the option to "Create new team" upon addon submission if you don't fancy creating a team beforehand. This is also because as I mentioned in the previous dev blog, regular users will not have access to the dashboard area at all. When you submit an addon now it does not automatically submit itself for review, you can now change other settings regarding addons and upload media and more before submitting it up for review. Addon reviewing is now done in a submission ticket instead of the creator discussion area on an addon.


Addon specific knowledge bases

Some much requested features for addons include their own knowledge base that works like a small wiki that you or another team member with sufficient access can manage. There's also a feature to display a message to all customers before they submit a ticket. This is in addition to the knowledge base being forced upon the user at least twice before they submit a ticket.

In your addon's knowledge base users get the ability to search, a list of popular topics and a list of categories that you can sort as you wish. As I mentioned in the previous dev blog, just ignore the header image as it isn't final. You can create help categories and choose their colour and font awesome icon. Help topics use our new editor that allows for embedding of youtube videos, vimeo videos, spotify songs as well as twitter tweets automatically.


Support ticket submission

When submitting a support ticket as a user now you get two options. Either addon support or site support. When you click on an addon you are brought to this screen:

Here you can see the message you specified earlier as well as a link to the addon knowledge base, and if that isn't enough you also get this popup when trying to submit the ticket:

This should hopefully make you think twice before submitting a ticket. Most of the time your issue can be solved by a quick glance at the knowledge base.


Support tickets for creators

The ticket view for addon creators now has a bunch of new options including filtering by subject, addon, tags, closed, open or all tickets. The more interesting stuff however happen in the ticket view itself:

On the right hand side you can see that you now have new options including labels and quick replies. A quick reply is a pre defined reply that you can define for each addon. This helps you use even less time replying to tickets if the response is really generic.

Labels are also pretty cool:

As you can see you can create labels on the fly in the ticket view itself, and assign them without any hassle. If you have ever used Github you are already familiar with how these labels work.

To edit a label you click the edit label button and you get brought to a page listing all the labels for this addon, where you can easily edit, delete or create a new label

A familiar interface for anyone who has ever used Github.

There's one more new thing about tickets that you might have noticed from the customer ticket creation screenshot, you can now upload attachments.

After uploading a file it's listed on the right hand side along with quick replies and labels:

Another enhancement we've made that isn't particularly a huge new feature is code highlighting,

This is super helpful to quickly spot an issue in a mess of a paragraph that someone might send you, provided they actually use the code block feature.


This is the second dev blog of a few more to come, even though this dev blog is big there is a lot more to share regarding addons and the marketplace itself. In the next dev blog I might share more about the new jobs system and how it works.


Keep replies civil. Questions and feedback is okay, but flaming or spamming is not.

Winner x 14Friendly x 2Agree x 1
#2

first

Dumb x 6
#3

wowza cool site, bout time we saw more of the ticket system

#4

What would be really great is to allow us to make predefined answers, not sure how it's exactly called in english, but every single tech support company got this.

Dumb x 1
#5
ByLapinat 4th of May 2018 15:38:05
What would be really great is to allow us to make predefined answers, not sure how it's exactly called in english, but every single tech support company got this.

And the difference between this and quick replies would be that they automatically reply based on the content of the ticket?

#6

I'm just curious, how much work will it take on our end to prepare our scripts for the update? Should we prepare anything before hand, and also what is the estimated time until release?

Also, will there be any beta tests offered to content creators?

Agree x 2
#7
By<CODE BLUE>at 4th of May 2018 17:32:44
I'm just curious, how much work will it take on our end to prepare our scripts for the update? Should we prepare anything before hand, and also what is the estimated time until release?Also, will there be any beta tests offered to content creators?

The one thing that you can to to prepare is create two new addon banners with the dimensions:

280px x 120px 900px x 415px

In addition to your already existing 920px x 260px banner.

You could also make a background image with the dimensions 1920px x 670px if you wish, but this is not required.

Other than that there is nothing you need to do to prepare your addons. You don't even need to do the above things, but it is required to be added as a featured addon in the front page carousel.

There's no release date set yet, but there is not that much left to do. I might notify content creators about a beta test once we've gone over some basic tests when we're nearing completion. The eventual beta test will not take place with a live database and rather a test database.

Winner x 2
#8
ByMarcuzat 4th of May 2018 18:08:11
The one thing that you can to to prepare is create two new addon banners with the dimensions:280px x 120px900px x 415pxIn addition to your already existing 920px x 260px banner.You could also make a background image with the dimensions 1920px x 670px if you wish, but this is not required.Other than that there is nothing you need to do to prepare your addons. You don't even need to do the above things, but it is required to be added as a featured addon in the front page carousel.There's no release date set yet, but there is not that much left to do. I might notify content creators about a beta test once we've gone over some basic tests when we're nearing completion. The eventual beta test will not take place with a live database and rather a test database.

Thanks! Looking forward to it, would be awesome if you could show some templates of how each one of the banner sizes are used on the script page. Cheers!

Friendly x 2
#9
By<CODE BLUE>at 4th of May 2018 18:19:40
Thanks! Looking forward to it, would be awesome if you could show some templates of how each one of the banner sizes are used on the script page. Cheers!

and

they will be used in different areas depending on the size we need.

Winner x 1
#10

Yeah but does it work in french though

Dumb x 3
#11
Byidiotat 4th of May 2018 19:02:42
Yeah but does it work in french though

we have support for it, but not all strings are localized

Disagree x 1Optimistic x 1
#12

don't translate the website in french, every single french guy will write messages in french

wait, you can do it i don't care

Funny x 2
#13
ByLapinat 4th of May 2018 21:25:12
don't translate the website in french, every single french guy will write messages in frenchwait, you can do it i don't care

It's not really far up on my priorities list. There's too many strings we haven't added to localization files right now for it to even be worth doing until after release. Even then the only purpose is for people to actually understand what the hell our ToS/rules are etc

#14

Looking good.

Agree x 1
#15

The hype continues to build. And regarding beta testing, that's for sure something that myself and many other devs would be interested in doing. So if you guys do end up creating a list of beta testers, add me to it please <3

Agree x 2Winner x 1
#16

You should cover reporting features next, stuff like easier review removals

Agree x 1
#17

maybe if u dont add french itll drive the frenchies away

Dumb x 4Funny x 1
#19
ByBillyat 5th of May 2018 10:08:37
No quick/predefined ticket replies?

Why do you guys think there are no quick replies... I literally had an entire section covering this :s

https://marcuz.eu/files/0lyp.png

#20
ByMarcuzat 5th of May 2018 10:36:38
Why do you guys think there are no quick replies... I literally had an entire section covering this :s

Sorry was just skimming.

Users viewing this thread
Nobody