Kyp

Run the configuration utility for your machine.

Also, delete your old installers and get the new ones. We've fixed the legal path error a while back for 64 bit machines.

It's a quote from our code of conduct, and it means no excessive gathering / protest to attempt to cause performance problems for other players. Because of the way it's worded, it's also to cover excessive camping of an area. In other words if someone gets their entire guild together to kill every mob at a spawn and refuses to allow other players to come in, then it becomes a problem. Though its going to have to be an obvious situation in the latter case I imagine for a GM to intervene. There's no reason not to share, but like Tienbau said we'll have a lot more mobs in the future so this should be a lot more of a non-issue.

What many of the people fail to look at who are pro-macro is that you gain all of the reward with none of the effort. This is unfair to the players who DO play the game as intended. This is one of the main reasons why macros are frowned upon in so many games. Another big reason (in the commercial world) is that you're using up bandwidth an actual player might enjoy. That and it leads to people farming the currency of the game. This is why we're not going to support it if you're not present.

David was actually looking for you. He made those changes to make it work without all the flags (for everyone) but he noted that it should fix yours and wanted to know if it worked. lol.

Install Client apply enb_up.exe patch run launcher, allow to patch to current versions (1.9.1 / 246, proxy 1.70) click play!

In addition to this, the TS3 Official server has a way to post a complaint on another user. If you have a problem like this right click their name and select the complaint option. Fill it out as completely as you can, and someone will eventually see it and review it. There are many ways to ban but it depends on what the user did and whether that's corroborated by others. In any case, though I'd throw this in here.

Definitely for chat logs and any packet data that may still exist, we've got a lot, but you never know.

As long as your character and starship creator utility is installed in your main game client directory as it should be, and there's no character occupying the slot on our server where you make it on the creator, it will appear as "Character #x" where x = the slot number. Click it, name it, and you're on!

www.net-7.org/stresstest

I'd recommend screenshots of the Launcher before you're clicking play. I have a suspicion you're not on the right version.

Post about your problems under Player Support and not in general discussion, you'll get an answer on it faster. Simply put this is INV300, it has possibly failed to install the new certificate or changed it to point at our servers. Run the Launcher as an administrator (right click and use Run as Admin EVEN if your account is already the computer admin), click Launcher in the upper left, then reset updates, then check for updates. In admin mode it should take care of this.

It's in beta simply because it's an early release. If you look at the old teamspeak client it was TECHNICALLY in beta for as long as we used it. The "RC2" stands for release candidate 2. In any case, it's not file hippo, I'm aware of the site. I'm going to go the way I always go with this one... Searing, buy a new PC! ;P

Yeah, your new account carries that status until you click the link in your e-mail.

Doesn't need to be extracted from anything, it is the file E&BSizzle.bik, I think it's in the common folder. Just search the client folders and sub directories for the word "Sizzle" that should show up.

Try clicking "Launcher" and then "Reset Updates" and then "Check Updates". If it still comes up with the same error you're going to have to edit one of the files and/or uninstall the existing N7 installation and download our most current installer. The current version of Net-7 is 1.8.9 unless it's been updated in the last couple of days. It's aiming at the incorrect location to download from (unless there was a DNS problem earlier today, which is certainly possible we were working on the server) Also, hi again Hibiki