Player Features and Ideas Discussion

Pretty easy

CollisionCnt = 0

On Collision

If ship1.LastCollision - Timer = 0 then ship1.CollisionCnt = 0

IF ship1.speed > SpeedLimit AND ship2.speed < SpeedLimit AND Ship1.MwdActive = TRUE THEN Ship1.CollisionCnt = Ship1.CollisionCnt + 1

If CollisionCnt > MaxCollisionsAllowed then Ship1.SuspectFlag = TRUE


How many times have you ever collided repeatedly with a ship at speed while your microwarpdrive was active??

To answer your question, while undocking I have done it plenty of times. You ever been to Jita? Seen the traffic in that station during peak times? I could rack up a killboard so green you could see it from space if bumping could flag someone.

Secondly, oh, wonderful, I see that EVE runs on basic IF>THEN statements!. Praise be to Infinity Ziona, who has saved us all from the vagaries of 3D representative modeling code and fluidic physics engines!

You really are an idiot, you know that, right? Did you expect me to believe that tripe?

Honestly, when I saw that I almost swallowed my tongue laughing at you. You have just proved, beyond a shadow of a doubt, that you have no idea what you are talking about.

Not sure what your problem is.
All I said is that you CAN code a method to detect bumping if you want that. I didn't say it would be easy nor did I say that it should be done. And while we're at it, there are already ideas in this thread that might work. All I say is that it's POSSIBLE if you really want such a method.

You seem to be the guy who said "they will never get it up" when the Wright brothers tried to launch their plane. And after it's launch your only comment would have been "they will never bring it down".

There's usually more than one approach to accomplish something. The question is usually not "can it be done?" but "how much does it cost?" ... and immediatly after that "is it worth it?". And as time goes by the answers to these questions can change.
As long as the devs think bumping is fine as it is, they won't change it (that's obvious). But there are examples that the devs changed their minds about certain things. And if someone in charge comes to the conclusion that bumping needs to be changed, it will be changed (there should be no doubt about that).

Firstly you are saying that you have accidentally and repeatedly collided with the same ship at MWD speed over and over again while undocking? I say you haven't.

Secondly, that is not BASIC code lol, that's psudocode, I program in C, C++, Visual C, Visual Basic and BASIC. I was actually a teacher for 10 years at TAFE here in Australia and taught it. The code above is more OOP C like code than BASIC though.

:)

Its not the physics engine at all. The physics don't need to change. Its a detection method for bumping which has nothing to do with the EvE physics.

No. My pseudo-code has a variable that counts the number of times you have bumped the same person while moving at MWD speeds. It also has a timer which resets the variable to 0 after an unspecified time. And it has a mechinism for flagging a person as suspect after the variable reaches an unspecified number of bumps.

Where did you get you'll be flagged bumping someone once at undock from when that doesn't meet any of the requirements for flagging, even if you bumped them 500,000 times it still wouldn't?

You're unfortunately making a fool of yourself and you fail to realise it :)

Plates and overdrives won't work like a MWD'ing Mach.

Its not like there will be more thousands of people bumping lol. I'm sure the cluster can handle a few checks when ships collide. They already do. Even at peak hour there's probably 50 people bumping at undock in Jita. If you consider 50 people bumping, that's 100 tasks for the server.

If you consider one person entering system, that's (lets say there are 2000 people in local) the server has to do 2000 tasks just to update everyone with the new person. Every message in local 2000 tasks and so on. Every time a person undocks, everyone on grid needs to see them, all overviews need to see them and so on. Its miniscule in comparison.

Its not anything to do with the physics model. Its collision detection. I don't how EvE does it and you don't either but I doubt the collision detection is intertwined with the physics code itself.

It would be more likely that when a collision detection function detects a collision, the function generates a call to the physics engine to update it so that it changes velocity, applies whatever friction it needs, changes the angle of the ships travel.

Programming is modular. Its all divided into functions. The functions usually are as independent of each other as possible which is called loose coupling. Its like that so you can change a function, say collision detection, and you get as little carry over to other functions as possible.

Edit: as to the deactivating MWD, it would be extremely difficult to calculate a point to start mwd and deactivate it before a) you hit the ship and b) before it turns off and you decelerate. MWD don't just switch off instantly.

Step one, it isn't the cluster handling the bumps, it's that single shard running the system. Jits is on it's own speshul system, so using that as a comparison is right out.

Collision detection *IS* the physics model. I mean, that's the PRIME job of a physics engine, is to work out collisions.

Also, again IIRC, there is no friction in EVE collision. Someone worked out the math long ago, but the rebound is simply done via a percent comparison based off of mass and velocity. This is why MWD works so well for bumping, it adds both.

Yes, programming is modular in a perfect world, in brand new code straight off the CVS. Now add ten years of patches, hacks hooks, and "just make it works".

You've still danced around exactly what I proposed. Rather than a simple DB call and compare at the (as you put it yourself) the rare instance of intentional collision, you want to install an overarching real-time module to physics engine check that does not currently exist. We're also doing this when the vast majority of the EVE playerbase, and CCP itself is happy with the current system of human evaluation of intent, if-when needed.



Anyway, lets say we install your system. After X MWD in Y timeframe, CONCORD shows up and kills the bumpers. No problem. I'll only bump in Y+1 time, and bring enough buddies to fill in the time. Make 5 minutes your timeframe, sure. I'll bring 25 buddies to bump (not hard at all). That's a bump per 15 seconds.

Any code fix you try to employ, is a fix I can work around. The only way to stop bumping is to ban it, and...CCP likes bumping. They've coined it as the "poor man's point" and toss it up as an example of unplanned emergent gameplay.