[fontkodo]

As you can see the timestamps don't line up:

I'm using the following code:

System.out.println(Chatbox.getMessages().get(Chatbox.getMessages().size() - 1).getMessage().toString());

to get the latest message in the chatbox.

Steps to reproduce:
Get the latest message and print out the contents

Problem: It only works for a while, then it stops working, only solution is to relog.
Proof that it works at first using the same code:

It seems to happen when a 'News' message is displayed, where it stops working thereafter, though this could just be a coincidence, it could be due to the messages reaching the end of the chat, I don't know.

 
@Cloud

Edit: Same behavior regardless of if timestamps are enabled or not

 

[baddest man on earth]

Did you try ChatBoxListener? Works fine for me.

@Override
public void onMessageReceived(MessageEvent e) {
    System.out.println(e.getMessage());
}

(05:12:34) You can access Treasure Hunter from the side panel, and you can show the button again by logging out and back in.
(05:13:00) A tasty fish.<br>GE guide price: 364 gp each
(05:13:10) An enchanted ring.<br>GE guide price: 1,835 gp each

 

[fontkodo]

Did you try ChatBoxListener? Works fine for me.

@Override
public void onMessageReceived(MessageEvent e) {
    System.out.println(e.getMessage());
}

(05:12:34) You can access Treasure Hunter from the side panel, and you can show the button again by logging out and back in.
(05:13:00) A tasty fish.<br>GE guide price: 364 gp each
(05:13:10) An enchanted ring.<br>GE guide price: 1,835 gp each

I'm using that but I need to delay until another message is sent and hence need getMessages to work.

 

[slashnhax]

I'm using that but I need to delay until another message is sent and hence need getMessages to work.

You could use a boolean as a switch?

 

[fontkodo]

You could use a boolean as a switch?

I ended up doing that and it should work, but getMessages is still broken.

 

[cloud]

getMessages isn't broken. It does not guarantee any order.

 

[fontkodo]

getMessages isn't broken. It does not guarantee any order.

Could we get a way to sort them easily, or was this restriction put in place so people used ChatboxListener instead?

 

[cloud]

Could we get a way to sort them easily, or was this restriction put in place so people used ChatboxListener instead?

It would be annoying to try and force the original order because the data comes in multiple "streams" that we then merge into a single list.

 

[baddest man on earth]

Just make a concurrent list and and every time a message is received, add it to the list.

 

[arbiter]

Just make a concurrent list and and every time a message is received, add it to the list.

Should be done in a bot specific context as this would be wasted usage for 99% of bots. May have been what you were suggesting, but just clarifying.

 

[baddest man on earth]

Should be done in a bot specific context as this would be wasted usage for 99% of bots. May have been what you were suggesting, but just clarifying.

It was a suggestion for @Furor