Not really. No ship begins to regen core in EK directly after cruise, unless there is a tap of thruster or strafe is in between, the ship will keep drifting with lowered powercore. As battleships lack a thruster it's obviously a tap of strafe in this case. That is the full trick.
I just learned something new. Thank you.
Yeah, it starts recharging once your speed gets to around 200m/s.
I've used this as long as I've been playing. I'm really shocked this is being called a bug/exploit. It makes sense as when you kill your engines, of course, your power core will recharge.
I honesty thought this was part of tactical gameplay. Shocked and disappointed to see a warning being issued for it when it is (A) part of the game mechanics and (B) a report filed by a disgruntled player who is simply lashing out SanctionLancer style.
Not really. No ship begins to regen core in EK directly after cruise, unless there is a tap of thruster or strafe is in between, the ship will keep drifting with lowered powercore. As battleships lack a thruster it's obviously a tap of strafe in this case. That is the full trick.
I just learned something new. Thank you.
Yeah, it starts recharging once your speed gets to around 200m/s.
I've used this as long as I've been playing. I'm really shocked this is being called a bug/exploit. It makes sense as when you kill your engines, of course, your power core will recharge.
(09-24-2016, 04:53 PM)Implosion Wrote: This "outrageous cheat" or "harmful exploit" has been around for as long as the cruise drain thing.
Warning Wesker about that means you should warn more than half of the active player base...
If it's such a big problem, I'm sure a FL Hook plugin can be made which would easily disable energy regen above a given speed...
It's been around forever yes and always a source of debate whenever it popped up. I'm not surprised one bit to see this topic once again.
I've literally never once seen this debated or declared to be an exploit by anyone including staff members. Maybe that debate happened in the admin forums but we aren't exactly all privy to that info.
I can only second what wesker said. This "bug" is more of a mechanic and not even one that comes without flaws.
You loose you maneuverability over it and if your targets cruises you are slower or need to recharge cruise.
Also the distances to make this work are quite long so its not like its a secret weapon.
Oh, that report.
Yeah, alright, let me just go out on a limb here at the risk of being meme'd to death and explain why that went through in the first place.
Your warning thread was poorly worded.
There is a reason why it is a warning. The situation has nothing to do with our beloved cruise-drain glitch. Where you jump out of cruise and tap a key to start regenning your shield. No, with how it is, that ''trick'' is so well known and given how it works ''balanced enough'' not to be considered as an exploit. Not a sancitonable one anyway. No, that was not the reason for the report, nor the description of the evidence presented in the report.
The evidence was a very poor quality (read- laggy) video which gathered a lot of "Uh...can anyone else see the moment when..." responses. What it -seemed- to show was the offending ship cruise up to someone and, the moment it was out of cruise, open (continuous) fire with cerbs - aka at full core.
The problem is, it was so poor in quality, there was no way to tell whether or not that was the case. It seemed off, but it was simply too poor to go through. It was settled that "just in case" it should be pointed out to the person. Nobody sanctioned you, dude. Had the topic of this report not been cheating, the evidence would have been discarded as unusable. However with cheating in mind, it did make us go Image for a moment and post this as a warning.
We are not allowed to ignore any report. It was a case of it being processed as a "something's odd, but not enough to be guilty - warn just in case" sort of report. There are not many of those, so when it happens, it is odd. The wording of the sanction thread, however, did not help this at all. Sorry about that.
Edit: Also, please note that it is a warning as in "uh, mate, we had a report about it, can you take a look at it?" sort of warning. Not a "Grrr, you screwed up, do this again and you are an ban" sort of warning. Also, before you ask, the only reason why in such cases people are not PMed about it is because all processed sanctions that are not discarded as unprocessable need to be made public. Nobody is shaming you or nailing you to the cross or anything.
(09-24-2016, 09:18 PM)sindroms Wrote: Edit: Also, please note that it is a warning as in "uh, mate, we had a report about it, can you take a look at it?" sort of warning. Not a "Grrr, you screwed up, do this again and you are an ban" sort of warning. Also, before you ask, the only reason why in such cases people are not PMed about it is because all processed sanctions that are not discarded as unprocessable need to be made public. Nobody is shaming you or nailing you to the cross or anything.
I don't think anyone here is confused about that, Spazzy. It's just that with the recent string of decisions we've seen the admin team make in regards to combat oriented stuff we immediately all assume the worst and try our best to come together and stonewall it before something dumb happens. It's not us jumping the gun over a warning, its us proactively explaining that this is not something wrong.
This has been a thing since the game came out. Everyone and anyone has used it 24/7 and it's never been regarded as an exploit, it's how the game works. It's hardly more of a bug as systemwalling is, and you greens have no problems with that.
(09-26-2016, 09:59 AM)Yber Wrote: This has been a thing since the game came out.
u wot.
cruise drain doesn't exist in the main game. in vanilla you instantly start regenerating as you exit cruise. this trick only exist to work with the cruise drain regen delay (specific to discovery and implemented by Cannon) and it's regarded as being mechanics because it was left unfixed for years (which at this point you can assume it is).
I'm personally not against it, as it was said earlier this isn't the easiest trick to pull off as many things can render the attempt useless, plus it sort of makes sense with inertia.
![[Image: osi-hiring.png]](http://i705.photobucket.com/albums/ww54/Stygian0/osi-hiring.png)
![[+]](/forums/images/collapse_collapsed.png "[+]")
Characters:
![[Image: P6DLUCr.png?4]](https://i.imgur.com/P6DLUCr.png?4)
![[Image: AX5RcTh.png?4]](https://i.imgur.com/AX5RcTh.png?4)
