Jump to content

NeuroGenix

Registered
  • Content Count

    156
  • Joined

  • Last visited

  • Days Won

    1
  • Feedback

    100%

NeuroGenix last won the day on September 13

NeuroGenix had the most liked content!

Community Reputation

23 Excellent

1 Follower

About NeuroGenix

  • Rank
    Experienced Botter

Recent Profile Visitors

1,363 profile views
  1. NeuroGenix

    [SNIPPETS] Neuro's GE API

    Thank you, I'm glad you like it Lemme know if theres anything else in there that you'd like commenting on.
  2. NeuroGenix

    Grand Exchange API - Help

    Can you give me an example from the code I've written where this is the case? So I understand what you mean better.
  3. NeuroGenix

    [SNIPPETS] Neuro's GE API

    Thanks man, I'm glad it's appreciated Lemme if there's anything you'd add or change, I plan on adding a method int Exchange#getMargin(int itemID) tomorrow, and also the ability to start offers from the history screen which I envision happening after the getMargin method is called; if the margin returned meets our criteria for adding the item to our toBuy list (or toMerch list).
  4. NeuroGenix

    [SNIPPETS] Neuro's GE API

    After originally posting this in the Scripting Help section I have decided it would be better suited here where there might be a larger audience to get feedback from to improve my own API and learn a thing or two in the process. What calling the method Exchange#offer(int itemID, int price, int quantity, boolean buy) will do: If the GE is closed it will open it and continue. Search for the item to buy 1-3 chars at a time, checking each time whether or not the first 9 results contains the item, clicking it if it does. If the price is set to -1 it will use the +/-5% buttons to increase/decrease the price until it is at a price that will buy/sell instantly, otherwise it will use the custom amount interface to set the price. It will set the quantity using the 1/10/100/1000 buttons, using the custom amount interface if it accidently goes over by more than 10, otherwise it will use the -1 button to get to the correct amount if it is within 10. If it gets onto the history screen, or the wrong offer type screen, it will return to the selection screen and continue. It doesn't collect items after it has made the offer, returning true when the offer has been made. This is so that in my scripts I can be selling 9+ items, from toBuy and toSell HashMaps, in one go; only collecting when there are no more empty slots. This, in my mind, is more human-like than collecting the item straight away after each offer is made, thoughts? It will prioritise buy offers over sell overs. So if it is buying something and there are no empty slots, or offers to collect, then it will cancel a sell offer, collect it and continue now it has an empty slot. If it is a sell offer and there are no slots available it will return true. This is so that in my scripts the item is removed from the toSell HashMap so it can be put back into to bank to sell later as my script has the items it needs to continue botting. If it has a buy offer and there are no empty slots, offers to collect or sell offers to cancel it will wait until an offer had completed, collect it and continue. I should add a time-out function here, and I'm also thinking of implementing some sort of priority feature whereby it will cancel a buy offer if this new buy offer has a higher priority, should be simple enough. It currently doesn't implement any antiban, I am hoping some of you can suggest the best way to implement that. Below is an example of the implementation. In this example, starting with the ge closed but near it, the bot will open the ge, buy 276 impling jars instantly, wait a few seconds before collecting them and then sell them all again instantly. All of the classes required to run this are below. I hope this can be helpful to somebody and I'm sure someone reading this can be helpful to me, thanks for reading, lemme know what you think. Zoo Class - Example of the code working Exchange Class - The main class GEInterfaces Class GEConditions Class InfoHelper Class
  5. NeuroGenix

    Grand Exchange API - Help

    Updated again, it will now use the +/-5% buttons to increase/decrease the price accordingly until it has reached a price in which it will instantly buy/sell if you set the price to -1 in Exchange#offer(int itemID, int price, int quantity, boolean buy). I'm really chuffed with how it's turned out so far, the only thing I really need to add to it is antiban. I'm not familiar with implementing abc, could someone tell me whether or not I could use the human reaction times for something like this or not? Because if I remember correctly its not to be used in situations where the reaction time is low, and I'm thinking the GE is one of those situations?
  6. NeuroGenix

    Grand Exchange API - Help

    Having an issue with the waitconditions return true too quickly, putting in an additional sleep before it recalled the offer method seems to fix it, but looks more bot like, suggestions?
  7. NeuroGenix

    Grand Exchange API - Help

    Rewritten, I am much happier with it now, flows smoothly and is much more scripter friendly now. Will make updating it in the future and customising it really easy. Let me know what you think, how can I make it better? What potential issues do you see? Thanks @JoeDezzy1, @IceKontroI
  8. NeuroGenix

    Grand Exchange API - Help

    Thank you, I'll keep you suggestion in mind if I run into any problems with detecting when items are collectable, right now it seems to be working well - Unless it remove sleeps and it changes states before the interface has loaded, I imagine that would be an issue with your suggestion as well though? That is a good idea about making my script more flexible, I am actually rewritting it all right now and had already began implementing a similar idea (I think). I'll edit my post in an hour or so when it's finished and tested and it'd be helpful to know if it's what you mean. I wanted my own class so I could update it and not have to rely on the Tribot API being up to date. I also feel like it gives me more flexibility, it's really easy to null check and click using that GEInterface class I made, I'm not sure if it is that simple when using the Tribot API? I have updated that in the new version, I think I have done it correct but if I haven't can you let me know when I edit this post later please Thats good to hear. Thank you man, I'm sure it'll turn out to be a good thing for me too
  9. NeuroGenix

    Grand Exchange API - Help

    I just realised I should probably null check the getNameFromItemDefinition method in the beginning of the GE#Offer method. - Also there is a lot of over lapping code between the Buy and Sell Screen - Setting the price, quantity and confirming the offer. This could probably be trimmed down a lot, as the interface ID's are identical in both scenarios; I haven't gotten around to neatening it all up yet but that will be a goal.
  10. NeuroGenix

    Grand Exchange API - Help

    Post rewritten after rewritting and updating the code multiple times. So I decided to give writing my own GE API a go and this is what I've come up with so far, using Exchange#offer(name, price, quantity, buy) will do the following: If the GE is closed, it will open it and continue making the offer. If the price is set to -1 then it will use the buttons to increase or decrease the price, depending on whether it is a buy or sell offer, until it is at a price that will buy/sell instantly. Otherwise it will use the custom input button to set the price. It will set the quantity using the 1/10/100/1000 buttons. I plan on updating this to randomise between using them and the custom input method shortly. Edit* I hadn't even remembered implementing this until I saw it do it whilst testing the method, and it was beautiful, but if it goes over the buy quantity accidently, in the example I saw it was clicking +100 and clicked it again too fast so instead of stopping before its target of 875 it got to 900, it will then use the custom amount interface to input 875, beautiful. It will prioritise buy offers over sell offers so that if there isn't an empty slot available, or any items to collect, then it will cancel a sell offer, collect it and continue now it has a free slot. If there isn't a free slot available and we are trying to sell something it will return true, this is so that in my scripts it will remove the item from a toSell HashMap and put it back into the bank to sell later because it has bought the items it needs to continue botting. If it is instead trying to buy something and there are no empty slots or sell offers to cancel then it will wait for something to buy and continue once it can collect something and therefore has an empty slot. Update* It will now search for the item 1-3 words at a time checking the first 9 results each time and will choose the item as soon as it is visible as a human would. I might update this so that it randomises more, sometimes entering the whole first word of an items name straight away, because I sometimes do that, most of the time though I enter as few characters as I need to, I think, thoughts? Let me know what you think, the code is probably disgusting to look at for some of you but for others just starting out like me it could be a valuable learning tool, for how not to code All feedback and constructive criticism appreciated. Exchange Class GEInterfaces Class GEConditions Class InfoHelper Class Thank you to everyone that has read this far, it is appreciated Rewritten, if you have read again, even more appreciation!
  11. NeuroGenix

    TRiBot Release 9.401_0

    ... GrandExchange#Offer is still broken, after the second time it's been "Fixed" on the issues page... Are you actually checking it prior to confirming it is fixed?
  12. NeuroGenix

    TRiBot Release 9.401_0

    Done
  13. NeuroGenix

    TRiBot Release 9.401_0

    Can confirm this is still broken. Won't buy items from the GE because it doesn't recognise the interface is open for it to search for an item to buy, if however I pause the script and choose the item myself it will proceed to purchase it. So, the issue should be a simple one to fix, I believe Jagex has changed the ID's of some interfaces and we simply need to change them on our end too. @TRiLeZ
  14. NeuroGenix

    TRiBot Release 9.401_0

    The Grand Exchange interface, for searching for an item, still doesn't work - It can get the interface up, but the won't search for any items because it doesn't recognise it has the interface, it just keeps clicking on the buy item box. This is when using, GrandExchange#offer. @TRiLeZ
  15. NeuroGenix

    TRiBot Release 9.401_0

    Thank you!
×