Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

Sell OSRS Gold
Naton

nwSlayer by Naton and WastedBro - Development Thread

Recommended Posts

I am no longer working on this project. Wastedbro may continue to develop the script.

 

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

unknown.png?width=828&height=631

unknown.png

 

Progress Reports:

image.png.b1162c0396006ee17cafd5030d4952e1.pngd2d4b6757b0ba83180994a76a3782e69.pngc95da2fda9155e977a59892862c8089b.png

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 2
  • thonking 1

Share this post


Link to post
Share on other sites
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
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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.
        • Like
      • 31 replies
    • Come give us feedback on the next version of TRiBot!
        • Thanks
        • Like
      • 74 replies
    • TRiBot is looking to improve a lot of its customer relationship management, customer on boarding process, customer experience, design elements, community engagement and pretty much everything else you can imagine when it comes to marketing.

      Our goal: To ensure that the marketing done TRULY reflects the experience and does not shine an inaccurate light on what TRiBot is lacking in.

      So I ask, what do you love about TRiBot and what do you hate about TRiBot? What does O S Bot, Rune M8, PowR Bot and Dre amBot do better? (yes I purposely didn't spell it right 😂).

      Love, 

      RileyZ
        • Like
      • 23 replies
    • Over the last three weeks, I've been working on upgrading our server infrastructure. It's finally ready and is now live!

      Why?

      Increased reliability - less server errors


      Increased availability - less downtime


      Increased security - keeping us and you secure


      Increased capacity - ability to serve you better


      Increased speed - less waiting for things to load


      Faster development - server and service updates will come faster


      What are the changes?

      Move from a single AWS EC2 instance to AWS ECS (Elastic Container Service)


      Distributed computing


      Load balancing


      Git management of server files and filesystem


      Redis caching


      How?

      AWS ECS (with 10 EC2 instances)


      AWS ElastiCache (Redis)


      AWS Load Balancing


      AWS EFS (Elastic file system)


      Please bare with us as I continue to tune the server for maximum performance. Slow loading speeds may occur temporarily. I thank everyone for their patience.

      Please post on this thread if you experience any issues other than slow loading times.
        • Like
      • 51 replies
    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)


      Improve banking API (Thanks @Encoded)


      Adds methods for returning and using Java Lists, rather than arrays


      Slightly randomizes some hardcoded behaviour


      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable


      Other back-end improvements





      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Sad
        • Haha
        • Thanks
        • Like
      • 90 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...