Thank you for the feedback and bringing these issues forward. I did a short test run today to see if I could replicate the issues you're having.
1) This was caused by the simple
player fishing giving false negatives. For lure fishing, 2 things are checked to determine if your player is fishing: the fishing spot you clicked is still active and has your player gained XP via the XP bar. Enabling debug mode showed that the script still (somewhat) accurately tracked the fishing spot so the issue must lie with XP being detected. Unfortunately I cannot rely alone on tracking a fishing spot because whereas MM2MS is wonderfully accurate, it's not 100%. So what you can do the remedy this is adjusting the timeout limit for lure-based fishing to something higher, such as 10000 (10 seconds) as opposed to its default 5 seconds. In the script I believe this is line 1423:
Simba Code:
'Trout':
begin
Self.Timeout := 5000;
It was set to 5 because I developed the script with an already very high fishing level, so most fish were caught very quickly. I'll make the adjustment on the script itself and shall push it through with the next update, whenever that may be.
2) I'm unsure why that may be happening.
Login.AddPlayer is called directly with what's in the player settings input boxes, so as long as those are correct I don't foresee any problems. I've had this same setup log in my account several times. If you don't already, I would recommend having your client remember your username and see if that doesn't address the issue.
3/4) I haven't had this issue myself. I enabled & disabled breaks, same with on-screen reporting and the XP gained counter seem to function correctly. I also tried banking mode, no issues there. The XP gained is completely based off of your XP bar, whether it's set to total or fishing only. I suppose I'll have to test it further to replicate that particular issue.
Again thanks for bringing these issues up. Give those suggestions a try and see if that doesn't remedy your script.