fuulishone

Max SD in live was also used to farm RD/Bogeril rep when DT was launched. I used to group with a PW that would hang out in Freya and just use SD on cooldown. It was a convenient little group. I was a JE and our little group also had a TT in it (as well as another JE and a PS). The PW would simply aggro the Chavez, SD to nuke them all and then we'd get to recharging his shield and reactor. Rinse repeat. This was before they nerfed the effectiveness of SD AoE damage. Afterwards this was still doable, but you had to train fewer mobs so that the leftovers could be picked off by the rest of the group. Do folks not remember the massive lag in Freya from all the PWs huddled around a single nav blowing off their SDs? BTW, this was on Orion.

Do you get the perpetual "Connecting to server..." message after a force update?

What exactly are your settings when you launch in order to get the INV-300 error?

-1 for being a fanboi and accepting that TS is the proper way to disseminate information to the masses (not to mention your rather arrogant response as well). Also, if spamming check server was filling up the server login queues, then I submit that the Net7 Launcher was poorly coded as there should be absolutely zero reason for a simple server check to take away a login queue spot. A simple out of process checker can tell you if the process is running, if it's properly bound to the correct tcp ports/ip address, and there should always be some kind of out of process log file that can be checked for status messages without affecting the proper function of the server itself.

Getting all upset over a print you have don't even know about yet is rather silly. Once the print becomes known and it's details get published, THEN you can argue about it. As of now, whether you get an actual mappable item (such as the CFB or some weapon) or not doesn't matter. You weren't going to map it anyway, so you'd end up selling it, or giving it away to a builder (say a nasty Terran). You didn't miss out. In the future, it just means you need to find a friendly Progen to build it for you and not some money grubbing Terran. Now... if it turns out that this item is no-trade, and therefore requires you to have a build skill in order to take advantage of it, then that's the time to complain about it. To put it into some perspective... Be happy that you have a content developer that's putting in such an interesting level 100 HU mission line. As a Jenq, there's no such mission line at all, and basically there's nothing new to obtain except for the level 30 reactor. We don't have some uber level 8 shield to get (since our good drops aren't in the game yet) so we get to use Barrier of Slime until such time as we can obtain a Bastion or Skull shield (yeah right....) We don't get some grand reactor at OL100 either (which would at least make sense in the racial lines) and instead we need to continue using drop reactors that have been around since before time began. Be happy that you have an active content developer that makes interesting and challenging missions.

Just gathering a list of missions that were previously not working/advancing properly, and that have now been shown to work as of last night's (Feb 28) server restart. I'll start off with ones I personally verified. Terran Enforcer Rally mission - previously, Lt. Baird wouldn't recognize that the Doctor on Jagerstadt sent you to her. That's now fixed and working and you can get Rally. You first need to go back to Jagerstadt and do his critical targeting mission one more time (even if you already have the critical targeting skill) so the mission advancement gets saved properly. After that Lt. Baird will give you the Rally mission.Progen Privateer Intro mission from Crones - This is the very first mission given to a fresh Privateer. You deliver radioactive waste and it unlocks the rest of the npc's. This now advances and unlocks the other npc's correctly. General Nitrous Oxide Mission from Paramis - Need to redo and double check. Chavez Mission from Paramis - Need to redo and double check.

It's a lvl 100 hull bonus mission, why would you be getting a print for a lvl 9 proj when PP/PS get a lvl 8 shield? Silly progen. Seriously tho, WTB this type of mission writing for Jenqs and Terrans.

It might be okay to allow say, Terran Scouts to build reactors. However in order to maintain balance amongst the races/classes for the rest of the server that care about the differences, the rather lax implementation of racial restrictions on items would need to be a lot more restrictive, as well as comparable changes would need to happen to the other races. For example: Terran Scouts could pick up build reactors, Jenquai Warriors or Seekers get build shields, Progen Privateers get build engines. On top of that, I would think it'd be necessary to be more strict with the racial restrictions on current and future items, as well as a necessity to convert some currently neutral items to become racial restrictive. Some more examples of what I mean: Halley DDO/Trifid engines would become Jenquai only. Built by and usable only by Jenquai. No change for Progens, but Terrans would lose the ability to use low sig engines from their Jenq friends and would be stuck with either looted race neutral items or stay with their own high-sig engines. Warrior's Heart reactors (which were never buildable in live) would become Progen only. Again, built by and usable only by Progen. Once again, no change for Jenquai, but Terrans would lose what has become a VERY popular reactor choice and be reduced to using only things like Unicorn II (for speed), Supernova (for recharge, missile buff) or wait for a Black Power VIII. I'm sure there's more that could be listed, the above are just two (admittedly contrived) examples of the downstream repercussions of the balancing effort needed, simply to allow Terrans to have a reactor builder in their ranks. So in a nutshell, no it wouldn't destroy the game, but it would change the game dramatically.

To the best of my understanding while mining along side someone not grouped with me, it kinda works like this: Miner A comes in a picks out the ores s/he wants and doesn't empty the roid. Miner B comes in a empties the roid, gets the roid clear bonus. Miner B empties the field and gets the field clear bonus (minus however many roids Miner A actually cleared).

Okay, not sure which is correct then, but in game right now my JT is showing as device 8, engine 9 as max levels. Are you saying it's supposed to be device 9 and engine 8?

"Connecting to server" = login server problems. 1) In Net7 launcher, check the box "Local cert" 2) Connecting to server now goes away, so you can at least type in your password. 9 out of 10 this will fail. Just keep trying til you get in. Good luck.

It's an ongoing problem with the login server the past week or so. The best you can do is to try and turn on local cert on the Net7 launcher and just keep trying. Lots of folks are dealing w/ the exact same thing right now.

Start the VirtualBox VM (assuming Windows of some flavor) in SAFE mode. Then install the client additions and reboot it.

My JT is maxed at level 8 devices, no level 9 for me.

It's off again, on again. Seems intermittent. Must be the cross-atlantic internet connection =P

Just checked on my TL50 JE. The spices gave 1080 - 798 = 282 credits profit, but zero xp. The Weapons Crates gave 734 - 468 = 266 credits profit and 31 trade xp. Remember this is with a TL50 toon. Gonna try again with a lowbie and see what I get.

Can't log in to double check right now, but the Somerled-Prasad should also have an alternative good... Buy lvl 5 Weapons Crates at Somerled, sell those at Prasad. I'm not sure if it's better/worse than Spices, perhaps someone could double check that at varying levels of negotiate?

Changed to local cert, the first time you try it doesn't work. The game looks like it locks up, but let it finish. Then try again and see if that works. Worked on one of my accounts but not the other, so not sure what's up.

No INV-300 error here, but just get a non-changing "Connecting to server" message at the Megan screen. Perplexing...

Lol, I logged in just as that message was sent out by a [DEV] on broadcast. Was there a warning message that I had missed?

Title says it all. Just kinda curious if anyone has actually seen a Tatsu's Pride drop during ST4. I know they existed in ST3, but it seems the mob is buggy this time around. He currently spawns 15k outside of a player's ability to access (i.e., past the edge of player space) and seems to only drop Dragontooth Projectiles or Mutilating Dragontooth Guns. Anecdotally thru Market, General and Guild chats no one has seen any yet, so I'm asking a larger audience to see if this is perhaps a loot bug? Along similar lines, it seems that the drops associated with mobs in enb-database seem to be wrong for certain drops/mobs. The Chavez in Paramis are an example of such discrepancy.

Does anyone happen to know if there's a scan cap on Seekers? No matter what I do, I can't seem to get above 10k scan range on my Seeker, and that's with max scan skill, Lvl 7 Roc (+3392 scan range), and Lvl 6 Grand Baka buff (+25% scan).

From what I can tell, bad opcode is actually an incorrect error message and not really indicative of the problem. It's more likely a network timeout occurred while waiting for a server response (such as opening a vendor after docking, or looking at build lists) and the thread that handles the listening wasn't coded properly and returns bad opcode. I notice my bad opcodes almost always happens when my network gets knocked out for some reason. I run wireless so someone turning on the microwave can knock me offline and lose connectivity. The Net7 proxy however has very poor connectivity detection and won't notice this for quite some time. If you happen to be pulling up a large list of something (via vendor or manu term) when the network goes, then I get a bad opcode. If I'm warping tho and lose connectivity, I get no error message at all. There may be more than one kind of bad opcode out there, so folks probably need to list what their specific situation was when it happened.

So recently I've started getting the error shown below whenever I quit the game. Doesn't matter if I quit to desktop or character/login and then quit from there, I still get the error. By "recently" it seems to have started within the last week or so. Any thoughts?

Auto-restart scripts can sometimes be an admin's worst nightmare. You don't normally want auto-restart scripts because they tend to remove the ability to diagnose/fix a real problem and can make things worse, especially when there's a database involved.