The activity counter in galaxy view only "DISPLAYS" minutes, yes. Perhaps minutes consist of smaller increments of time? Surly there is code that tracks it by the second.
So your saying, as long as the (10min) appears somewhere in the actual 60 seconds that that window lands in, then you chalk it up as accurate?
Sorry bud, the difference 3 seconds makes is massive and were talking 14.
A report with a time signature showing -16:58:31- means an asterisk should convert to (10min) at -17:08:31-If there was no activity....not -17:22:31- off by 14 seconds. this would imply some activity took place just after the probe.
What server do you play in? lol
Re: Recalled probes still cause activity.
#12read my post again i think he timed it to when he sent the probe if that takes 14 seconds thats your time difference
Re: Recalled probes still cause activity.
#13That's possible. Other than not activating any kind of timer until a report is actually generated. which would require the probe to REACH its target. the initial post by Demon denotes activity being started even if the probe is recalled in the last few seconds.
May another look at the code is what needs to happen.
May another look at the code is what needs to happen.
Re: Recalled probes still cause activity.
#14it does it mass and reloaded and if i remember right it does so in speed it always has with probes what got me was the time difference but i think he timed it wrong
Re: Recalled probes still cause activity.
#15Really baffled by why you moved this out of bugs...a RECALLED mission still triggered activity. It would be like recalling a attack fleet and it causing damage.
Activity has to do with ninja because if they think my probe will land they may view the planet zorg. Which means activity so if I recalled the probe and there was no bug and he had activity I could know he's on. As it is we just know probes cause activity whether they reach the destination, or not. Seems like a bug considering NO OTHER ACTIONS are treated like this....so...move back to bugs yeah?
Activity has to do with ninja because if they think my probe will land they may view the planet zorg. Which means activity so if I recalled the probe and there was no bug and he had activity I could know he's on. As it is we just know probes cause activity whether they reach the destination, or not. Seems like a bug considering NO OTHER ACTIONS are treated like this....so...move back to bugs yeah?
Re: Recalled probes still cause activity.
#16and make them update the game hahaha good luck.Doomrager wrote: ↑Tue Feb 13, 2018 4:28 pmReally baffled by why you moved this out of bugs...a RECALLED mission still triggered activity. It would be like recalling a attack fleet and it causing damage.
Activity has to do with ninja because if they think my probe will land they may view the planet zorg. Which means activity so if I recalled the probe and there was no bug and he had activity I could know he's on. As it is we just know probes cause activity whether they reach the destination, or not. Seems like a bug considering NO OTHER ACTIONS are treated like this....so...move back to bugs yeah?
Re: Recalled probes still cause activity.
#17This is how it is working like forever. Just because you want it to work differently, it does not make it a bug.
Re: Recalled probes still cause activity.
#18It IS a bug. If something is evidently wrong, just because "This is how it is working like forever." doesn't make it right, lol.
If man had originally invented the wheel as a square, then two thousand years later, somebody notices that and says, hey, round wheels would be much better, these square wheels are wrong, do you think somebody would say " They've been square for two thousand years, this must be correct" do you?
Please answer this, why IS there an activity counter there at all?
Re: Recalled probes still cause activity.
#19Lol seems like Zorg is the only on that isn't understanding this. Use that brains
Re: Recalled probes still cause activity.
#20Been that way forever certainly doesn't mean it is right. Simply having brought it up now instead of at day 1 makes zero difference. A fault is fault. If your not wanting to fix it, that is fine, but claiming that is how it is intended is absurd. If I recall ANY type of mission, the mission should not cause: (1. The purpose of the mission (Attack/Defend/Probe). 2. Activity (From Attacking/Defending/Probing.) Otherwise your code is severely flawed, and I can just launch rips at slow random speeds to cause random activity everywhere and cause people to think I'm online all the time, which in 2013 you got onto chuck for using a browser auto refresher to fake activity. So you clearly care about fake activity, but not this kind?