Chat is bugged - Kind of urgent

Hello I'm working on the last few things before our play session this afternoon (we will start in 3 hours) when something this important breaks. We don't need it for communicating with one another, we use another form of voice over IP that works better for us. But the problem is that we use some macros and would like to be able to roll. None of this works now in my game. I have tried to go in to another game I have and there the chat works.  I don't know what is going on and my panic levels are rising fast. Please send help as soon as you can. Thank you

On my phone so will be brief, clear the chat archive (game details page rather than in app). Might want to back it up first (copy paste into a word program etc)

Ziechael said: On my phone so will be brief, clear the chat archive (game details page rather than in app). Might want to back it up first (copy paste into a word program etc) Is there some other way to clear it than going in to My settings->Clear Current Chat Log? Because I have already tried that. But I will try it again now to see if maybe does the trick.

That's the in app version, if you go to the details page for your game clear chat archive is in the game settings drop down (I think)... Again I'm on my phone at the moment sorry lol

I just updated to Plus btw, maybe that has something to do with it. I noticed the problem when I tried to start a macro ( &{template:default} {{name=@{selected|token_name}, Bett}} {{Område= [[1d100]]}} {{Skada= [[1d8+@{selected|SB}]]}} ). Can this have caused some problem? I have been using the &{template:default} one quite a few macros. Could this cause the problem?

Ziechael said: That's the in app version, if you go to the details page for your game clear chat archive is in the game settings drop down (I think)... Again I'm on my phone at the moment sorry lol Thanks! It did the trick! Thanks again for the help, you're a lifesaver! If someone wants to lock this post or change it to "Chat is bugged - Kind of urgent (solved)" or something like that it would be nice.

This issue usually occurs when a template has incorrect formatting, not sure it has been pinned down what the exact cause is though... Generally though you should be fine with templates :)