capybara

I understand what you are saying... I have been able to solo in FB, but the trick is to make sure you only aggro one or two (max) at a time, and i'm referring mainly to the minion fish, and perhaps the 61's and 63's (which i've been able to do) provided its a one on one fight. Usually this requires some luck, or a couple of other groups taking on the Bosses, so you can isolate the stragglers. Usually what happens, though, is once one fish goes aggro, a couple of others will follow, but if you back up enough they usually break their pursuit, or you have time to then go after the other once your first target bites it. Hense the problem with the grave link, so you need to be no closer than about 6.5k i've found.. I certainly don't have a problem with this being as difficult as it is in general, i just think the grav link lasting so long basically made it so you couldn't at least turn tail and run when you got in over your head. They would just tag team you, and you could just sit there and watch your ship go 'poof'... If you shorten the grave link duration i think it will improve the game, while still not making it easy to fight in the FB on those days when you can't find a group to fight with.

A little randomization is aways good.. Guess my memory is off, or everyone elses is, but i could swear in live that once an ore was "opened" that it would fairly shortly thereafter go "poof" and then the respawn timer would kick in, and it would respawn... You could then return to a field in 20 or 30 minutes at it would be good as new, provided you had opened every ore. So the question is: Why can't this be done with the hulks too... Once you crack it open with your mining icon, it effectively ends its life after say 5 or 10 minutes or so, in much the same way a mob courpe does (i forget how long it took in live) then it goes on the timer for respawn.. ? There are three or four main reasons people cherry pick... sometimes it comes down to cargo space - though i personally prefer to space stuff when it comes to the hulks, so they will respawn after they are cleaned out... Second is because its in a danger zone, an example of which would be GOBB and Controller area, where decloaking and recloaking can mean life and death. And of course people who are trying to quickly gather particular items, or are just plain greedy... So there are some legitimate reasons, and some not so legitimate... You can't lump everyone together... Anyway, if the hulks explode (or pop) once you crack em, then that pretty much takes care of the main issue with cherry picking... as it comes down to first find first serve.... then its back on the random timer for someone else to find. Cheers,

Well ok... not impossible... but who likes to have to kite everything? Boring..

Hello, Maybe its just me, but it seems things in the fishbowl have gotten a bit more difficult.. which i don't mind so much, but i do feel it is unfair to have such a long 'hull mass' hack on our ship... which doesn't actually "increase the mass" as it shuts off your engine entirely... especially when the wait to gain control usually means another mob will just give you another 'hull mass increase' which means you just sit there and watch three or four lv56's (or larger) eat away your entire shield and reinforced hull in a minute or two... Happened to me a few times, and means soloing in fishbowl is next to impossible, unless several other groups have already thinned out the fish so you can actually find a lone fishy or two. Can someone please turn down the duration of the hull mass increase, and/or make it so you still have half engine speed? Just a "suggestion"...

I have to wonder if these issues are regional in origin.. interference or a bad local relay? I heard the server is in Germany??? Is that right? I think those of us in NA should consider trying to find a way to get another server located here. Assuming there are enough players to warrant one, it may become necessary in the future once a beta shows some reliablity. I also hope more knowledgable techs come forward to work on these issues... This project no doubt started with a small team, so the more the better.

Doesn't seem to matter if the server is up or down.. it's been so unbelievably unstable since the September 15 proxy update that I now have had more ctd's in the last 10 days than my entire time playing (since Feb/10)... Is the server now next to a massive electro magnet? Clearly there has to be tweeks and experiments to get everything working perfectly, but when something is changed and everything goes south, would it not be advisable to go back to the 'last known good' and return to what at least allowed us to play the game... I can live with one or two ctd's a week, but more than a dozen a day means the game is virtually unplayable... Forget all about jobs... Last time i was on i crashed just going to a vendor... then after i managed to relog, i crashed leaving the station.. then i got black holed.. What the hell did you guys do to create so many opcode errors?? PLEASE go back to the previous net-7 proxy client.

K, thanks for the heads up..

Here is a snip of some error log entries... The first was the original, which gave the 'version too old' error before i reinstalled the net7 launcher. LaunchNet7 - Exception Version: 1.9.8.1 Time: Tue, 20 Jul 2010 06:58:54 GMT Message: The operation has timed out System.Net.WebException: The operation has timed out at System.Net.HttpWebRequest.GetResponse() at LaunchNet7.LauncherUtility.DownloadString(String url, Int32 timeoutInMilliseconds) at LaunchNet7.LauncherUtility.DownloadString(String url) at LaunchNet7.Updateing.Updater.CheckForUpdates() LaunchNet7 - Exception Version: 1.8.1.0 Time: Tue, 20 Jul 2010 07:45:59 GMT Message: The operation has timed out System.Net.WebException: The operation has timed out at System.Net.HttpWebRequest.GetResponse() at LaunchNet7.LauncherUtility.DownloadString(String url, Int32 timeoutInMilliseconds) at LaunchNet7.LauncherUtility.DownloadString(String url) at LaunchNet7.Updateing.Updater.CheckForUpdates() LaunchNet7 - Exception Version: 1.8.1.0 Time: Tue, 20 Jul 2010 07:48:37 GMT Message: Could not launch client. System.ApplicationException: Could not launch Net7 Server. Details: The system cannot find the file specified ---> System.ComponentModel.Win32Exception: The system cannot find the file specified at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start() at System.Diagnostics.Process.Start(ProcessStartInfo startInfo) at LaunchNet7.Launcher.LaunchNet7Server() --- End of inner exception stack trace --- at LaunchNet7.Launcher.LaunchNet7Server() at LaunchNet7.Launcher.Launch() at LaunchNet7.FormMain.DoLaunch(LaunchSetting setting)

I haven't been on the server for a couple of weeks... Last night, when i started up the launcher it updated a couple of files (which i was expecting after the long break) but then it said it couldn't logon because the net 7 version was too old (or words to that effect)... So i deleted net 7 and tried again from scratch, with the latest version of net 7, and now it will update a few client files, but says it 'timed out while checking for updates for net 7' I've reloaded net 7 about three times now... even tried disabling virus protection (even though this was never an issue before) and even tried "force update" which appears to do absolutely nothing.. I have run out of ideas.... I thought perhaps the server was down, or the service for net 7 updates was having issues. Anyone know what is going on here? Is the ENB universe pissed at me because it took two weeks off??