Jump to content
Sign in to follow this  
ung1v3npur3

Require premium scripters to have own accounts?

Recommended Posts

I've seen alot of times when a script is broken and needs updating scripters ask for an account to borrow to fix it.

Isn't this pretty ridiculous? In my opinion if you own a premium script you should have accounts yourself to test your script if your updating or fixing it?

Edited by ung1v3npur3
  • Like 2

Share this post


Link to post
Share on other sites

This thread is a little ridiculous really. Like if you're afraid of a scripter stealing your account then you overvalue your account. Scripter status is worth a lot more than a RS account. 

But for more practical reasons, chances are if you're using the account to try and bot using there script you'll have everything set up. All they'd have to do is log in and test, this means a lot quicker bug fixes for you. Especially if they don't own a main acc that can run it. 

Another reason would be that sometimes individuals may experience bugs specific to them which the scripter can't replicate without the use of the users account. Say the have a very specific skill or something. 

Share this post


Link to post
Share on other sites
29 minutes ago, Starfox said:

And if their account gets banned? It's very time consuming to create new accounts every time one gets banned just to be able to run a script for 10 minutes to fix a bug. It is much more worth it to borrow an account to solve the problem.

IMO, not having a basic RS account to fix most issues of your script is unreasonable.

Perhaps if it is for a very high level requirement / addition borrowing is a solution.

 

But, it shouldn't be the customer's problem to help you fix a a basic issue. It's not that hard to buy an account on sythe or PlayerAuctions in a day or so, on the off chance that the account does get banned. (A scripter should also use his account carefully if it is expensive to avoid this).

  • Like 6

Share this post


Link to post
Share on other sites
Just now, Worthy said:

IMO, not having a basic RS account to fix most issues of your script is unreasonable.

Perhaps if it is for a very high level requirement / addition borrowing is a solution.

 

But, it shouldn't be the customer's problem to help you fix a a basic issue. It's not that hard to buy an account on sythe or PlayerAuctions in a day or so, on the off chance that the account does get banned. (A scripter should also use his account carefully if it is expensive to avoid this).

If it's a basic issue, you shouldn't even need an account to fix it. You only need to look at the code, and the report from the user.

Share this post


Link to post
Share on other sites
2 minutes ago, Starfox said:

If it's a basic issue, you shouldn't even need an account to fix it. You only need to look at the code, and the report from the user.

My point still stands; you should have an account for at least 90% of your problems.

  • Like 2

Share this post


Link to post
Share on other sites
1 minute ago, Worthy said:

My point still stands; you should have an account for at least 90% of your problems.

This is true, we're all guilty of it though and sometimes one account used to modify multiple scripts gets removed and can make things problematic. I usually like to train up accounts while I have a solid one and then leave the backups until I need them but having a good relationship with your users is definitely helpful.

  • Like 3

Share this post


Link to post
Share on other sites
59 minutes ago, Worthy said:

My point still stands; you should have an account for at least 90% of your problems.

You should try to have an account, but if you don't have one it should not be mandatory to get one as soon as you possibly can; it's just not feasible. The scripter either needs to spend a ton of time to train one for their specific script, or spend money buying one which comes with problems other than just forking over money for it.

Share this post


Link to post
Share on other sites
11 hours ago, Starfox said:

You should try to have an account, but if you don't have one it should not be mandatory to get one as soon as you possibly can; it's just not feasible. The scripter either needs to spend a ton of time to train one for their specific script, or spend money buying one which comes with problems other than just forking over money for it.

u should pay  to lend  acounts  to  make updates and you would have   NO  PROBLEMS to get acounts   its realy eazy djstarfox

Share this post


Link to post
Share on other sites
On ‎18‎-‎10‎-‎2016 at 11:54 PM, Starfox said:

And if their account gets banned? It's very time consuming to create new accounts every time one gets banned just to be able to run a script for 10 minutes to fix a bug. It is much more worth it to borrow an account to solve the problem.

So actually your saying people that use your premium script should let their account that they borrow to you get banned to get your premium script updated that you make a lot of money of?

 

 

Share this post


Link to post
Share on other sites
1 hour ago, ung1v3npur3 said:

So actually your saying people that use your premium script should let their account that they borrow to you get banned to get your premium script updated that you make a lot of money of?

 

 

That is not what I said at all. Borrowing someones account to run a script for 5-10 will not get them banned.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Our picks

    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
        • Like
      • 8 replies
    • This release will:

      Fix Settings UI placement bug


      Fix game object location bug


      Fix small layout bug making the client shift up and down


      Fix client crashing bug where loading the client with a small display area will cause the client to crash


      Fix annoying Linux bug relating to painting events and peers


      Fix settings saving bug where settings are saved to disk more often than they should


      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people


      Drop Java 1.7 bytecode version for 1.8


      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).


      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Like
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening


      Fix the incorrect object positions bug


      Fix and re-enable the LG Objects API Accelerator


      Fix the RSObject#getAllTiles bug
        • Like
      • 22 replies
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client


      Slightly improved login bot


      Removed final access modifiers from API classes


      Added RSServer hook wrapper to get the client's cached list of server/world info


      [NEW] Bug fix for intelligent banking


      [NEW] Improvement to the stability of LG over time


      [NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client


      [NEW] Fix LG login problems


      [NEW] Fixed re-sizable mode container bug


      [NEW] Fixed re-sizable mode mouse bug


      [NEW] Use of public constants in the Banking API


      [NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Thanks
        • Like
      • 12 replies
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client


      Slightly improved login bot


      Removed final access modifiers from API classes


      Added RSServer hook wrapper to get the client's cached list of server/world info


      Bug fix for intelligent banking


      Improvement to the stability of LG over time



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Thanks
        • Like
      • 10 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×