[Release] SeaBot 3.1

02/07/2017 00:17 TitanicVSEisberg#1981
Guys i recommend u shut down ur bot for a week or two until this shit cools down
02/09/2017 11:42 Username is valid.#1982
i waiting for update xD
02/09/2017 20:39 iNSiDER_#1983
New update v. 3.0.205

Changelog:
  • Codes updated



[Only registered and activated users can see links. Click Here To Register...]
02/09/2017 22:51 AlfaWR123#1984
why not licence permanent ... ?
02/10/2017 09:59 24seven#1985
Are you also working for free for the rest of your life? Your boss will be happy.
02/10/2017 15:23 iNSiDER_#1986
New update v. 3.0.206

Changelog:
  • Codes updated

Notice
Premium licenses have been extended by one day
Expired licenses have been reset



[Only registered and activated users can see links. Click Here To Register...]
02/11/2017 19:12 Ɖanger#1987
Bot doesn't go back into behemoth when I get sunk. Is this only for me or does anybody else have this problem?
02/11/2017 23:22 Aaylexu#1988
mee too
02/13/2017 11:55 alino78#1989
yo,

it crashes everytime
02/13/2017 19:44 Red_John#1990
Wait till the next update...
02/15/2017 21:35 iNSiDER_#1991
New update v. 3.0.208

Changelog:
  • Codes updated

Notice
Premium licenses have been extended by one day
Expired licenses have been reset


[Only registered and activated users can see links. Click Here To Register...]
02/16/2017 22:26 FregattePfalz#1992
Jungs der ist nicht sicher mehr Seafight hat ihn geknackt sperre droht:rtfm:
02/17/2017 10:01 alfredogabber#1993
Der Bot war noch nie sicher. Das ist kein Geheimnis. Meine Seabot Schiffe wurde alle gesperrt andere nicht.
02/17/2017 13:13 Aaylexu#1994
can t log in
02/17/2017 13:20 levlevliva#1995
Quote:
Originally Posted by Aaylexu View Post
can t log in
"SF_JohnRackham - Today at 12:06 PM
We are currently facing problems with our network In the Nuremberg Datacenter.
All EU servers are affected.

SF_Trissilein - Today at 1:17 PM
still no newwws :frowning:
and i have been for food already! -.-
IT expects 50 minutes"

Man the game sucks you can't load seafight.com, so the problem is not with the bot... :rolleyes: