If you go to the fishing spot and start fishing, you are asked if you want to do this and that it takes up 10 of your turns to cast your line. If you accept, the turns counter won't update though.

If you have subsequent "no bite" and "the fish escaped" events and you wish to keep trying, you won't be taken to the game interface and you won't see for real how many turns you have left.

Well, there is some good news.

I do NOT wish for the attack results to show the exp gain/loss before the results are displayed.

So, I thought about giving each stat box an ID and using innerHTML to update it with javascript if I want something specific changed.

Which means, attack results will not reveal until end whether your exp changed, and fishing can deduct turns from the value without refreshing the page.

Ouch. It will get so much harder to attack this way. However, I can only imagine you want to decrease the server load so I understand the correctness of this decision from the techinical standpoint, but I bet the user base will not be too happy about it.

Mainly, I feel like it's ruining the point of the results, since you KNOW whats happened.

OK, won't argue your decision.

yeah, but some people won't even pay attention to what the results are; they'll just keep attacking anyways