Token

Authed

They were all functional when written, I cannot guarantee the quests are working after every client/rs update but if they are not, they are updated

Authed Authed I decided not to rush as there is no point in extending content unless it's perfectly stable Authed

Should be fixed on next SDN update

It doesn't work like that

Authed

It actually dropped just a few hours ago to be precise

Thanks, I'll check the code

Was it sitting in the spot where it drops the frog or like 10 tiles away?

Did it have a bloated frog in inventory or it already dropped it? They are posted on the first page

Check the logger contents, the reason should be printed there

Authed

What I just said is there is no logical reason for the method to return null after a trade is completed and you should not write your code around that. If that was the case then the naming of the method would be wrong. But if you still don't believe me when I explained what the method should do, here is this code But there is additional code in getRequests() which removes these after exactly 15 seconds have passed. The fact that requests are removed after 15 seconds does not matter because "GET LAST REQUESTING PLAYER" doesn't contain anything related to whether a trade was done with that player, that is done either by using chat messages or caching the trade status and checking the progress. The implementation of getRequests() is entirely based on a MessageListener which adds chat messages to a linked list and removes them after 15 seconds have passed (this is for the sake of memory management and you should not rely on it).

I have no idea what that is supposed to return but by the name of it, the result should be last player who sent you a trade offer (maybe what you need is getLastRequestingPlayerNotAccepted()). My logic may be flawed but I don't see any reason for that to return null if you completed a trade with that player, unless he logs out or leaves the local region (or you leave it) because if I were to implement that, it would be just a filter on players.getAll() which would return null if the player can't be located.

I'm not exactly sure what it has to do with the title of the thread, but the notion of "listener" generally denotes something whose whole purpose is to signal a thread group when something happens (achieved in java through the notify method and thread interruption if required). If you manage to write a sound implementation of a trade request listener then this sends a signal every time you receive a trade and is consumed by everyone who receives it, same as an input listener, you will not be able to respond more than once to the same event.

The bot is not down, all you have to do is download the new version from the website (use the "Download" button on top of the page) as the button is not working on the boot interface

You've had too much LSD

Whenever they are ready No, that's in your gear preset

Yes, but that's not a quest

Authed

Check the logger contents, the reason should be printed there

You can always use the 2nd tab to create your own quest list

Yes it will skip as soon as it reaches that quest and it realises it doesn't have the stats for it

Authed

vitamin c