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:

      Add LG support for Runelite


      Fix NPCChat issues


      Fix a bug where the camera angle setter would just hold down a key for 5 seconds (the timeout)


      Slightly adjust the rotation via keys to be more accurate


      Add the ability for asynchronous camera movement via keys


      Make Camera rotation via mouse more fluid, with more antiban, and work much better in resizable mode


      Add a "Camera#setCamera" method, allowing the rotation and angle to be set in parallel


      Increase the likelihood of using the mouse for camera movements


      Add support for adjusting the camera to positionable entities (Positionable#adjustCameraTo)



      Upcoming updates:

      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Haha
      • 44 replies
    • This update will:

      Allow for clicking through the chat box when possible (Thanks @Todd)


      Fix Combat#selectIndex (Thanks @Encoded)


      Ensure worlds stay sorted and added a check to avoid misclicks in the in-game world hopper (Thanks @erickho123)


      Fix out-dated Options API interface indices (Thanks @Todd)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 12 replies
    • This release will:

      Fix login bot after today's game update (Thanks @JoeDezzy1)


      Fix latest in-game world hopping issues (Thanks @erickho123)


      Compact Settings UI and set location relative to TRiBot (Thanks @JoeDezzy1)


      Fix an older implementation of GrandExchange#getWindowState (Thanks @JoeDezzy1)


      Improve the preformance of NPCChat by only searching in certain interface parents (Thanks @JoeDezzy1)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      LG support for RuneLite


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 16 replies
    • This release will:

      Fix bytecode manipulation in order to prevent the modification of parameters within the Filter and Condition classes themselves (thanks @wastedbro)


      Fix NPE caused by non-null value in GE API (thanks @erickho123)


      Add and fix equals methods for api2007.types (thanks @JoeDezzy1)


      Modify Mouse#leaveGame to make the mouse leave the game from top, left, right, or bottom (thanks @erickho123)


      Add Entrana area to Ships API (thanks @erickho123)


      Fix raid prayers index/settings in Prayer API (thanks @erickho123)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 29 replies
    • This update will:

      Implement better canvas locking/synchronization mechanism


      Fix small Login API bug


      Remove the requirement for xbooting Java classes


      Use ExecutorService to perform canvas work in parallel


      Add "Account Management" game tab to GameTab API (thanks @Encoded)


      Fix NPCChat#getMessage (thanks @Encoded )


      Fix NPCChat#selectOption (thanks @Encoded )


      Fix Banking API after today's update (thanks @Encoded )


      Fix in-game world hopper after today's update (thanks @Encoded )



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 38 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×