EVE General Discussion

That's what they have been working on for some time now, sadly 'on the fly' active node remapping (the brain in a box project) is something still a few years off.

I tried a big TiDi nullsec fight once. Once.

Here's how to fix all of this in the first place:

Step 1, limit all corporations to maximum 50 members.

Step 2, limit all alliances to a maximum of 5x 50 member corps.

Step 3, limit fleet size to a maximum of 50 players

Step 4, during a 'fleet fight', a system is limited to no more than 6 total fleets for a reinforced node fight.

Step 5, lots of bitching and whining by 1000+ power block alliances/corporations who come on the forums ***** and whining about TiDi and and why shouldn't CCP spend 10mil USD on a Quantum Computer etc etc etc to let them have it their way.

CCP needs to take a stand on this, you want your cake and eat it too? Go play something else. Otherwise STFU and be happy you can cram 2000+ people in a system that isn't Jita and actually do something or let CCP find a way to prevent you from ruining the server and the game for everyone else *Snip* Please refrain from personal attacks. ISD Ezwal

Any chance of a post/blog on what you did with some nice bar graphs, pie charts and possibly a flow chart?

There are a couple issues.

Its not hardware. CCP has very very top shelf servers the X4000 series they use for the Jita node is up there with the best enterprise level servers on the market.

The issue is the Python, Python is single thread, and since newer server architecture uses more cores to spread a hyperthreaded application and get more done at once, this isn't possible on Eve because Python is single thread, you really can't multi-thread. The other thing would be dynamic load balancing i.e. auto reinforcement, the problem there is that in a real time (computer real time) environment that is VERY VERY difficult, my company was working on it for like 4-5 years and basically gave up, again, a single thread application real times.

Since porting Eve to a multi-threaded program would basically mean re-writing the entire game from the bottom up this is a non-trival task and would best be dubbed "Eve Onine 2" so they are working with things like brain in a box and inifiniband to try to reduce the overall load.

Still there is no simple "fix" everytime they increase cluster perfomance we just jam more people in system.

Have been thinking a bit more and came up with a Q & A format.

Q: What if players start bringing in 20 x 100-ship fleets to avoid stacking penalties to 2,000 ships fleets?
A: add stacking penalties for FCs on grid
Q: what if a side brings x-1 FC, being x the amount needed to apply penalties?
A: the stacking penalties for FCs would be general and everyone would be affected by them
Q: but what if a side adapts its strategy to the penalties?
A: make the penalties impossible to adapt to -FAI, the penalties start by unlogging a random pilot from each fleet each n-ticks. After a set threshold, the penalties will start unlogging FCs.
Q: but wouldn't that favor a strategy of just dumping ships without FC, so the other fleet lost its FCs to the penalty and then the disorganized fleet could activate its FC and sweep the now disorganized second fleet?
A: ships without a FC are logged off at a constant pace of (% of total) per tick -and that targets preferably pilots with FC skills
Q: so first you're penalized, then you're logged off, then your FC is logged off, then you are logged off at an accelerated pace and your FCs are logged off too even if they're not acting as FC... where's the limit?
A: don't bloody bring in so many ships. Just keep calm and love the hamsters, and you'll be OK.
Q: but then there will not be a way to field enough firepower to down the bigger ships!
A: the stacking penalties would hit first and harder precisely those ships, which anyway, and probably, should be easier to kill (maybe)

Any questions?

I have removed some rule breaking posts and those quoting them. As always I let some edge cases stay.
Please people, keep it on topic and above all civil!

The rules:
2. Be respectful toward others at all times.

The purpose of the EVE Online forums is to provide a platform for exchange of ideas, and a venue for the discussion of EVE Online. Occasionally there will be conflicts that arise when people voice opinions. Forum users are expected to be courteous when disagreeing with others.

3. Ranting is prohibited.

A rant is a post that is often filled with angry and counterproductive comments. A free exchange of ideas is essential to building a strong sense of community and is helpful in development of the game and community. Rants are disruptive, and incite flaming and trolling. Please post your thoughts in a concise and clear manner while avoiding going off on rambling tangents.

4. Personal attacks are prohibited.

Commonly known as flaming, personal attacks are posts that are designed to personally berate or insult another forum user. Posts of this nature are not beneficial to the community spirit that CCP promote and as such they will not be tolerated.

5. Trolling is prohibited.

Trolling is a defined as a post that is deliberately designed for the purpose of angering and insulting other players in an attempt to incite retaliation or an emotional response. Posts of this nature are disruptive, often abusive and do not contribute to the sense of community that CCP promote.

12. Spamming is prohibited.

Spam is defined as the repetitive posting of the same topic or nonsensical post that has no substance and is often designed to annoy other forum users. This can include the words “first”, “go back to (insert other game name)” and other such posts that contribute no value to forum discussion. Spamming also includes the posting of ASCII art within a forum post.

22. Post constructively.

Negative feedback can be very useful to further improve EVE Online provided that it is presented in a civil and factual manner. All users are encouraged to honestly express their feelings regarding EVE Online and how it can be improved. Posts that are non-constructive, insulting or in breach of the rules will be deleted regardless of how valid the ideas behind them may be. Users are also reminded that posting with a lack of content also constitutes non-constructive posting.

26. Off-topic posting is prohibited.

Off-topic posting is permitted within reason, as sometimes a single comment may color or lighten the tone of discussion. However, excessive posting of off-topic remarks in an attempt to derail a thread may result in the thread being locked, or a forum warning being issued.

30. Abuse of CCP employees and ISD volunteers is prohibited.

CCP operate a zero tolerance policy on abuse of CCP employees and ISD volunteers. This includes but is not limited to personal attacks, trolling, “outing” of CCP employee or ISD volunteer player identities, and the use of any former player identities when referring to the aforementioned parties.
Our forums are designed to be a place where players and developers can exchange ideas in a polite and friendly manner for the betterment of EVE Online. Players who attack or abuse employees of CCP, or ISD volunteers, will be permanently banned from the EVE Online forums across all their accounts with no recourse, and may also be subject to action against their game accounts.

31. Rumor mongering is prohibited.

Rumor threads and posts which are based off no actual solid information and are designed to either troll or annoy other users will be locked and removed. These kinds of threads and posts are detrimental to the well being and spirit of the EVE Online Community, and can create undue panic among forum users, as well as adding to the workload of our moderators.

It's a bit tough with the going gets tough,eh?

Fact: Since Asakai - several major battles have been aborted by node crashes, one of which has been blamed on a manual hand off stumble, but the rest have just turned turtle due to code issues

Fact: Since Rubicon release I have personally experienced multiple client crashes on two different accounts, seen several comments in local about same as I have traveled about, and heard on VOIP people's clients crashing out during fleet ops at a rate much higher than pre-Rubicon. Either CCP's network connections or the client is unstable.

Fact: new code is always buggy

Fact: CCP is responsible for the new code

Fact: CCP can't replicate the issues without having the problem in hand

Fact: The only way this massive fight crash problem is going to be in hand is to get the cooperation of the large alliances engaging in these battles to get on the test server and put it out there into CCP's hands.

Fact: 9 times out to 10, including this post right now, for the few times that I post the forums have crashed on the first attempt to post. The forums are broken, again.

So you freely acknowledge that you lack the background to have an educated opinion on the subject, but then you go ahead and post your "solution" anyway, despite the fact that people who have the background to have an educated opinion on the subject have repeatedly pointed out that your recommended solution isn't really viable?

My bad - forgot to include, 9 of 10 since the recent forum updates over the past two weeks. Before then I had about the same failure rate, one out of 50. Not rarely, but certainly much more reasonable.