-# Megathread: Suggestions and Updates
Make a tool for people who post jobs to check the code they were given.
So the tool would basically run against every addon that was posted on here and make sure non of that code was copied. Don't know how hard that will be but it will be a good tool to prevent people giving leaks as code for the jobs on this site.
ByNo Originalityat 17th of July 2016 16:47:06
Make a tool for people who post jobs to check the code they were given.So the tool would basically run against every addon that was posted on here and make sure non of that code was copied. Don't know how hard that will be but it will be a good tool to prevent people giving leaks as code for the jobs on this site.
yes because the leading case of job fraud on SF is copied code from paid addons
just do your fucking research before making a job/doing one seriously, if you do research you're less likely to get scammed or fruad'd.
and if people decline to, that's their choice you can't stop them from being ignorant.
Example: http://i.satanseye.com/postalmemes.png
it happens everywhere warnings or not.
ByLunaversity ღat 19th of July 2016 07:07:32
just do your fucking research before making a job/doing one seriously, if you do research you're less likely to get scammed or fruad'd.and if people decline to, that's their choice you can't stop them from being ignorant.Example: http://i.satanseye.com/postalmemes.pngit happens everywhere warnings or not.
When people post a job here it is because they can't code, what makes you think they can check for fraud?
Checking for fraud is common sense. It's not really something you have to learn, unlike coding.
Can we get some api for support tickets?
Get all open tickets and their content, respond to a ticket and close a ticket. I would like to be able to make some initial automatic responses with some solutions to common problems.
Edit: 90% of tickets could be answered with same response.
Just gonna port this: https://scriptfodder.com/community/threads/612-script-support-stuff over here so it'll be more noticed I guess.
I just wanna see the support center become easier to manage.
Anyways:
#Departments
Can we have departments that allow users to go to a certain part of the tickets that the Content Creator/Support Agents make? (e.g. Installation Errors, Broken Addon, etc...)
#Priority and forwarding
Priority that is set by the Support Agent/Content creator to place maybe a lable saying the priority and from like, low to high and by default when the ticket is submitted "No Priority" in grey until set.
Forwarding being if the support agent wants to forward it and notify the original content creator (cause I didn't make their scripts) it'll notify them that it's being forwarded to them to handle.
#Anti-Spam
Have there be like a 10 second delay cause if you double click no-matter what on accident it'll reply twice so it's kinda annoying with a laptop when you accidentally tap twice.
#Black listed users
Users that are complete cancer/not at all thankful yet hostile for the support they got have some sort of label/background color on their ticket saying "Toxic User" or something like that.
#A set of guidelines before submitting (editable by content creator)
This'll be a complete guide (markdown friendly) that a developer can set and it'll bring up kinda like a ToS and if the user doesn't find their issue in the guide they can click on like "Create ticket" or people that found out their issue click like "Issue fixed" or something like that. I think this would deplete a shit ton of "how do i install dis bby?", I seriously have a whole notepad for all the scripts I do support for to just copy and paste on how to install.
That's all I can really think of.
Also noting what rabbit replied: Priority would be set by the script agent/content creator to show that the ticket is actually important instead of an installation ticket.
ByJacobat 22nd of July 2016 18:37:14
Get all open tickets and their content, respond to a ticket and close a ticket. I would like to be able to make some initial automatic responses with some solutions to common problems.Edit: 90% of tickets could be answered with same response.
why not code your own support ticket system and have the support button on the script page link to it?
Reminder that you guys should use the issue tracker now
ByLunaversity ღat 29th of July 2016 21:01:19
that's what he's doing u homosexual
Not really. I like Scriptfodders system, and I think most customers would prefer it to stay on SF as well. Would just make it so much easier to have API.
ByLunaversity ღat 29th of July 2016 21:01:19
that's what he's doing u homosexual
no he wants an API to do whatever he wants with his tickets.
I still think having an automatic message you can send to anyone who purchases your script is a neat thing.
Essentially just...
Thank you %user for purchasing %script! Please do not add me on Steam, and instead use the ScriptFodder ticket system to request any new features, or report any bugs! Please make sure to review my script, as every little bit helps me continue making these great scripts!
ByNookyavaat 2nd of August 2016 13:45:31
I still think having an automatic message you can send to anyone who purchases your script is a neat thing.Essentially just...
You could do this yourself if a messages API was implemented:
simple {{ web_hook }} that returns nothing in your script -> your webserver checks database to see if they've sent the message before -> if not, send the message
"Hello, [user], thanks for downloading [script], please do not add me on Steam if you have any issues and instead create a support ticket. Thanks!" and etc
Still requires that something is added, whether it's a feature or an API.
ByNookyavaat 2nd of August 2016 13:45:31
I still think having an automatic message you can send to anyone who purchases your script is a neat thing.Essentially just...
The type of people who make the support tickets that can be solved by a generic response, are the type of people who will ignore and / or forget about that initial message though.
ajax tabs on our dashboards? c: