Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Naton

nwSlayer by Naton and WastedBro - Development Thread

Recommended Posts

Posted (edited)

Development Information:

nwSlayer is being developed by Naton, a premium scripter, and WastedBro, a TRiBot developer and premium scripter

 

The script is currently in the beginning stages of development, and this thread will be updated as we progress. With two developers working on the script, nwSlayer will be developed as efficiently and swiftly as possible, and will be unrivaled in the Slayer botting scene.

 

nwSlayer will be a next-level slayer script, containing support for almost anything you could desire when slaying.

 

Current Plans:

We will continue to update this thread as we progress, and we are expecting a public, open beta at some point in the near future.

Expected Features:

  • Task camping - fight any of the supported monsters without actually being assigned the slayer task!
  • Turael, Nieve, Mazchna, and Vannaka support are currently planned. Turael and Nieve are the initial focus.
  • Customizable loot lists for each task
  • Customizable gear setups for each task
  • Customizable inventory setups for each task
  • Cannon support
  • Any gear support, including barrows
  • Trident + blowpipe support
  • Most magic spells
  • Some safespotting
  • Task skipping via turael or slayer points
  • NPC contact for obtaining new tasks
  • All slayer item support
  • We have a goal to support as many slayer tasks as we possibly can for each slayer master we add!
  • And much, much more as we progress on the script!

Pictures:

image.png.3356eb9f41129627ab5af55542c1e102.png

CKfaaCguSym4zWgPZRBq8A.png

image.png.deabb29f5c2cb228de6bef3f488ebdaa.png

unknown.png?width=828&height=631

unknown.png

 

Progress Reports:

TBA when we have a working beta (Soon!)

Suggestions:

Feel free to offer any suggestions you would like to see in a slayer script! This is the perfect time to ask as we are in development. We are very open to hearing what you have to say. Leave a comment below.

Edited by Naton
  • Like 7
  • Thanks 1
  • thonking 1

Share this post


Link to post
Share on other sites
Posted (edited)
35 minutes ago, zdogg said:

What purchase options will be available?

We haven't discussed specific prices but I'm thinking we will only have monthly options as I'm not a fan of the others

 

Edit: We may offer three/six month auths

Edited by Naton
  • Like 1

Share this post


Link to post
Share on other sites

Things I would like to see in this script:

I think I speak for a good part of the community that is about account creation and building an account that I can be proud of when I finally reach my goals, myself, I like to make pking accounts so this here opens a great door to achieving the goal of someday getting a heavy ballista without the superior grind getting the slay up. What I'd like to see is safety and randomness. What I mean is when the script gets a slayer task not only is it doing its built in anti-ban activities such as different pathings, eating, checking the exp, or whatever it may be, but I would like to see the script HAVE OPTIONS to its location when it gets a task such as lets take goblins as an example, I would love to see it have different options to where the bot would slay them and not ALWAYS going to lumbridge/al-kharid gate. There are several popular goblin (or whatever slayer monster) locations to slay at and going to the same super popular location is not ideal. Now I'm not saying we should find the 2 spawn of goblins on the 3rd lower level of a dungeon, but maybe have the bot have 3 options at random to either slay at  1) Al-kharid  2) Goblin village  3) dwarf cannon goblin cave. I feel this would add great anti-ban and a load of incosistent actions that a player may take just to "switch it up". 

Would love to have reflection from @Naton & @wastedbro

Share this post


Link to post
Share on other sites
48 minutes ago, ace_001 said:

Things I would like to see in this script:

I think I speak for a good part of the community that is about account creation and building an account that I can be proud of when I finally reach my goals, myself, I like to make pking accounts so this here opens a great door to achieving the goal of someday getting a heavy ballista without the superior grind getting the slay up. What I'd like to see is safety and randomness. What I mean is when the script gets a slayer task not only is it doing its built in anti-ban activities such as different pathings, eating, checking the exp, or whatever it may be, but I would like to see the script HAVE OPTIONS to its location when it gets a task such as lets take goblins as an example, I would love to see it have different options to where the bot would slay them and not ALWAYS going to lumbridge/al-kharid gate. There are several popular goblin (or whatever slayer monster) locations to slay at and going to the same super popular location is not ideal. Now I'm not saying we should find the 2 spawn of goblins on the 3rd lower level of a dungeon, but maybe have the bot have 3 options at random to either slay at  1) Al-kharid  2) Goblin village  3) dwarf cannon goblin cave. I feel this would add great anti-ban and a load of incosistent actions that a player may take just to "switch it up". 

Would love to have reflection from @Naton & @wastedbro

The problem with multiple locations is that it's only useful for really low level tasks. 

 

The vast majority of tasks have exactly 1 optimal spot. So much so that in fact not going to that spot is exactly what a human would not do. 

 

However, in some scenarios, if you have certain stats or quests, you can get access to better locations for some tasks. We would like to support this eventually. It would happen automatically. If your account has the requirements, it will detect it and automatically use the better spot. 

 

As for other tasks with many locations such as goblins, perhaps we could make the bot randomly choose between different locations. I will have to get back to you on that. 

Share this post


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

The problem with multiple locations is that it's only useful for really low level tasks. 

 

The vast majority of tasks have exactly 1 optimal spot. So much so that in fact not going to that spot is exactly what a human would not do. 

 

However, in some scenarios, if you have certain stats or quests, you can get access to better locations for some tasks. We would like to support this eventually. It would happen automatically. If your account has the requirements, it will detect it and automatically use the better spot. 

 

As for other tasks with many locations such as goblins, perhaps we could make the bot randomly choose between different locations. I will have to get back to you on that. 

Well obviously the time spent isn't worth supporting low level mobsters in that, but supporting higher slayer areas would be great.looking forward to this

 

Share this post


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

I'm hyped. I'd like to see Chaeldar support, convenient for zerkers and pures.

We can definitely look to add this later on after we finish the core slayer masters, but it won't be an initial priority

  • Thanks 1

Share this post


Link to post
Share on other sites
9 hours ago, ace_001 said:

Things I would like to see in this script:

I think I speak for a good part of the community that is about account creation and building an account that I can be proud of when I finally reach my goals, myself, I like to make pking accounts so this here opens a great door to achieving the goal of someday getting a heavy ballista without the superior grind getting the slay up. What I'd like to see is safety and randomness. What I mean is when the script gets a slayer task not only is it doing its built in anti-ban activities such as different pathings, eating, checking the exp, or whatever it may be, but I would like to see the script HAVE OPTIONS to its location when it gets a task such as lets take goblins as an example, I would love to see it have different options to where the bot would slay them and not ALWAYS going to lumbridge/al-kharid gate. There are several popular goblin (or whatever slayer monster) locations to slay at and going to the same super popular location is not ideal. Now I'm not saying we should find the 2 spawn of goblins on the 3rd lower level of a dungeon, but maybe have the bot have 3 options at random to either slay at  1) Al-kharid  2) Goblin village  3) dwarf cannon goblin cave. I feel this would add great anti-ban and a load of incosistent actions that a player may take just to "switch it up". 

Would love to have reflection from @Naton & @wastedbro

We would want to pick the best location for the task, however if there exists tasks such that multiple locations would have the same efficiency level then I think as long as the location is easy to navigate to then we can.

1 hour ago, sevant said:

How are you guys looking on test accounts? Been looking for a good slayer script for years 

I’ve got one account and can probably buy some accounts/bot them up with my crab killer, but if anyone has spare accounts they wouldn’t mind us using for testing when we complete more of the script, that’d be great.

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

  • Our picks

    • This release will:

      Fix LG for both OSBuddy and RuneLite


      Fix issue where the resizable client isn't able to be made smaller (Thanks @JoeDezzy1)


      Fix detection of the logout game tab when resizable mode and side panels are enabled (Thanks @JoeDezzy1)


      Add initial support for Sentry to allow us to identify and easily debug exceptions happening with all TRiBot users


      Add methods to determine if the bank is actually loaded, and not just the overarching interface (Thanks @wastedbro)



      Upcoming updates:

      Improved CLI support


      Full Sentry support


      Much more
        • Like
      • 50 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)


      Update deposit box interface ids (Thanks @Encoded)


      Add various bank methods (Thanks @wastedbro)


      Banking#getWithdrawXQuantity


      Banking#getDefaultWithdrawQuantity


      Banking#arePlaceholdersOn




      Fix resizeable minimap bug (Thanks @wastedbro)


      Remove Java 8 requirement


      Please note: TRiBot is not yet fully compatible with Java 10+




      Fix the break handler issues by ensuring the break handler thread never gets paused


      Fix broken settings hooks



      Upcoming updates:

      Improved CLI support


      Much more



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

      Add support for using custom F key bindings to switch between game tabs (Thanks @erickho123)


      Fix tab opening for "Skills" and "Kourend Tasks" (Thanks @erickho123)



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

      Fix an issue where breaks would stop firing


      Fix Combat#getWildernessLevel, use dynamic search for text and cache ID for later calls


      Fix an NPE in the Combat API


      Fix Mouse#leaveGame bug where the mouse wouldn't actually leave the game screen
        • Like
      • 21 replies
    • 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
        • Thanks
        • Like
      • 59 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×