Pages: [1] 2 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 3 post(s) |
|
CCP FoxFour
C C P C C P Alliance
3457
|
Posted - 2014.08.19 15:14:00 -
[1] - Quote
Hey guys,
As you may have seen there was a post on Reddit, which then started a thread on the forums here, about how you could detect mobile siphon units through the API. When mobile siphons were introduced we decided we did not want you to be able to detect them via the API and so put measures into place to ensure you could not.
The post on Reddit gave a supposed example of detecting these siphons via the API. Their example was simple:
- Setup a POS and harvester.
- Check the API and notice it is working. In their case there was 100 units in the silo.
- Empty the silo.
- Deploy mobile siphon.
- Wait an hour, check API, notice only 40 units instead of the 100 that should be there, clearly a siphon MUST be involved.
You can see the Reddit post here: http://www.reddit.com/r/Eve/comments/2dgv6n/ccp_allows_siphon_detection_through_api/
There are a few suspect about the post, but lets ignore that and pretend that is all legit as others have now reported this same issue.
I went on Sisi and did the following:
- Deploy POS
- Anchor silo and harvester
- Setup the chain
- Advanced the cycle
- 100 units went into the siphon
- Checked API, 100 units there
- Removed the 100 units from the silo
- Deployed siphon
- Advanced the POS cycle
- Checked in the client and there was 40 units clearly in the silo
- Checked the API and it showed 100 units, as if nothing had been siphoned
So admittedly I did a few things players cannot:
- Advanced the cycle of the POS manually
- Cleared the API cache
I have repeated the above without those with the same result. This is just my much easier to reproduce test case because to hell with waiting hours for things to cycle and caches to expire.
Before we continue I want to point out that if the siphon does not exist in space we report the exact contents of silos, not the fudged numbers.
What I am looking for is someone who can offer a 100% reproducible test case (if you need help testing like the API cache on Sisi cleared let me know) or an instance of this happening on TQ/Sisi right now. One that you have not touched since noticing it happening and that we can look into.
If you can come up with one of the above we would greatly appreciate it. If you do please feel free to contact me at the following: @RegnerBA on twitter [CCP]FoxFour on irc.coldfront.net CCP FoxFour in EVE Mail regner [insert some kind of sign relating to email here] ccpgames.com
On a final note, we here at CCP really do appreciate it when you contact us directly about issues instead of telling everyone about problems that can be used to negatively impact their experience. There are many ways to do so, bug reports with good steps detailing how to reproduce something is generally the best way. You can however also EVE Mail specific devs if you know they are active. Twitter or IRC also work.
The main point is we really appreciate discretion in these kinds of things, and publicly posting just makes us really not like you very much. In crazy cases if we know your character or account you may even find your API restuls suddenly have the following appended to them:
[specialMessageJustForYou]You can find the bug reporting page here https://community.eveonline.com/support/submit-bug-report and using that makes us friends. Stop being a bad.[/specialMessageJustForYou]
* [ used instead of < because forums. CCP FoxFour // Game Designer // @RegnerBA |
|
Sentient Blade
Crisis Atmosphere
1325
|
Posted - 2014.08.19 15:26:00 -
[2] - Quote
I think the better question is did API-undetectable siphons ever have any meaningful or positive effect on game play, or did they just make more logistics operators want to top themselves. |
Aryndel Vyst
GoonWaffe Goonswarm Federation
773
|
Posted - 2014.08.19 15:54:00 -
[3] - Quote
If you didn't want siphons to be detected through silo levels and people don't want the API giving flat out lies, why have the API report silo levels in the first place? |
Daktar Jaxs
Wildly Inappropriate Goonswarm Federation
42
|
Posted - 2014.08.19 15:59:00 -
[4] - Quote
I'm sorry, CCP cannot accept player submitted evidence. |
Gossamer DT
Wildly Inappropriate Goonswarm Federation
107
|
Posted - 2014.08.19 16:00:00 -
[5] - Quote
When you guys first released this screwing of the API, you did state it was going to be random.
What would be nice is if you guys would go fix the broken Jobs API instead of waisting time on this API that takes 6 hours to even be seen anyways just to prevent a little more PassivePVP. who is your main, and what does he do? |
Andski
GoonWaffe Goonswarm Federation
10930
|
Posted - 2014.08.19 16:01:00 -
[6] - Quote
Aryndel Vyst wrote:If you didn't want siphons to be detected through silo levels and people don't want the API giving flat out lies, why have the API report silo levels in the first place?
way to steal my line jerk Twitter: @EVEAndski
"It's easy to speak for the silent majority. They rarely object to what you put into their mouths." -á-á - Abrazzar |
thetwilitehour
GoonWaffe
278
|
Posted - 2014.08.19 16:01:00 -
[7] - Quote
CCP FoxFour wrote:Hey guys, On a final note, we here at CCP really do appreciate it when you contact us directly about issues instead of telling everyone about problems that can be used to negatively impact their experience. There are many ways to do so, bug reports with good steps detailing how to reproduce something is generally the best way. You can however also EVE Mail specific devs if you know they are active. Twitter or IRC also work. The main point is we really appreciate discretion in these kinds of things, and publicly posting just makes us really not like you very much. In crazy cases if we know your character or account you may even find your API restuls suddenly have the following appended to them: [specialMessageJustForYou]You can find the bug reporting page here https://community.eveonline.com/support/submit-bug-report and using that makes us friends. Stop being a bad.[/specialMessageJustForYou] * [ used instead of < because forums.
As wonderful as this snarky little dump you're taking on your players chests is, CCP has a long track record of ignoring problems until player outrage is raised. See: the T20 incident, BoB involvement with RP events, ISD problems and eventual disband, and even currently Somerblink.
So if you want players to report stuff directly to you instead of just posting it for the community, you need to show a consistent track record of responding to player reported issues in a timely and positive fashion. Instead you're part of a company that is famous for "logs that show nothing".
I mean, you have a goddamned group of players who advocate to you and get FLOWN TO ICELAND because you had a developer ACTIVELY CHEATING AND COVERING IT UP. Your response to someone making it known that ONE OF YOUR EMPLOYEES WAS CHEATING was to BAN THAT PLAYER. So please shut up about your desire for private whistle blowers. |
Retar Aveymone
GoonWaffe Goonswarm Federation
702
|
Posted - 2014.08.19 16:06:00 -
[8] - Quote
Aryndel Vyst wrote:If you didn't want siphons to be detected through silo levels and people don't want the API giving flat out lies, why have the API report silo levels in the first place? this is the worst idea in the history of bad ideas
removing silo levels from the api would be just pointless misery on poshavers |
mynnna
GoonWaffe Goonswarm Federation
3710
|
Posted - 2014.08.19 16:36:00 -
[9] - Quote
I know it's not what you're asking for, but the better way to fix this has nothing to do with changing the API. Instead, have a design team make the following tweaks:
- Siphons no longer take materials on an hourly basis, they merely keep track of how long they would take.
- To steal material, a "Steal Material" option in the dropdown menu of the siphon must be used. This would transfer the appropriate amount of material into the siphon as well as destroys the portion it's supposed to.
It's that simple!
The upside to you, of course, is no more API nonsense. If you detect a siphon via API in this model, it's because someone already stole from you and may have done so again (the assets API only updates every six hours, if I recall correctly).
The gameplay upside is that there are now vastly more opportunities for player interaction surrounding the siphons. Instead of a small team of logistics players monitoring the API and responding to them as needed - and mind you, as they're the only ones who can put the goo back into the silos, they are the only ones who do this - anyone can do siphon patrols, because all they have to do is shoot the things. On the flipside, it's no longer sufficient as an attacker to just spam a bunch of siphons and then ignore them, knowing that they're causing a bunch of extra effort for the logisticians and causing damage (in the form of the moongoo that the siphon destroys). If a player using siphons for guerilla warfare wants to cause harm, they have to stay in the area, monitor their siphons, return to actually loot them, or they do nothing.
This change would make it far more likely that opposing players actually encounter each other and require active gameplay input on both sides, instead of the relatively passive low interaction model they drive now, solve the problem of the API, and do so in a way that doesn't change the overall function of siphons nor needlessly punch reaction operators and other legitimate POS-havers in the balls. Member of the Goonswarm Economic Warfare Cabal |
Aryndel Vyst
GoonWaffe Goonswarm Federation
774
|
Posted - 2014.08.19 17:41:00 -
[10] - Quote
Andski wrote:Aryndel Vyst wrote:If you didn't want siphons to be detected through silo levels and people don't want the API giving flat out lies, why have the API report silo levels in the first place? way to steal my line jerk
#rekt |
|
Bienator II
madmen of the skies
2794
|
Posted - 2014.08.19 20:17:00 -
[11] - Quote
mynnna wrote:I know it's not what you're asking for, but the better way to fix this has nothing to do with changing the API. Instead, have a design team make the following tweaks:
- Siphons no longer take materials on an hourly basis, they merely keep track of how long they would take.
- To steal material, a "Steal Material" option in the dropdown menu of the siphon must be used. This would transfer the appropriate amount of material into the siphon as well as destroys the portion it's supposed to.
It's that simple! POS-havers in the balls. you would have to make the siphon auto-steal if it is engaged. But even if you would, a POS owner could secure all materials before killing the siphon. So far i don't think this change would work. eve style bounties (done) dust boarding parties imagine there is war and everybody cloaks - join FW |
mynnna
GoonWaffe Goonswarm Federation
3713
|
Posted - 2014.08.19 20:53:00 -
[12] - Quote
Bienator II wrote:mynnna wrote:I know it's not what you're asking for, but the better way to fix this has nothing to do with changing the API. Instead, have a design team make the following tweaks:
- Siphons no longer take materials on an hourly basis, they merely keep track of how long they would take.
- To steal material, a "Steal Material" option in the dropdown menu of the siphon must be used. This would transfer the appropriate amount of material into the siphon as well as destroys the portion it's supposed to.
It's that simple! POS-havers in the balls. you would have to make the siphon auto-steal if it is engaged. But even if you would, a POS owner could secure all materials before killing the siphon. So far i don't think this change would work.
It doesn't need to auto-steal if engaged because the whole point of the change is that if the POS owner or his friends or allies are vigilant, they lose nothing. Member of the Goonswarm Economic Warfare Cabal |
|
CCP FoxFour
C C P C C P Alliance
3460
|
Posted - 2014.08.19 20:56:00 -
[13] - Quote
Doesn't matter, not the point of this thread. Please stay on topic. CCP FoxFour // Game Designer // @RegnerBA |
|
Saisin
State War Academy Caldari State
115
|
Posted - 2014.08.19 23:12:00 -
[14] - Quote
mynnna wrote:I know it's not what you're asking for, but the better way to fix this has nothing to do with changing the API. Instead, have a design team make the following tweaks:
- Siphons no longer take materials on an hourly basis, they merely keep track of how long they would take.
- To steal material, a "Steal Material" option in the dropdown menu of the siphon must be used. This would transfer the appropriate amount of material into the siphon as well as destroys the portion it's supposed to.
It's that simple! The upside to you, of course, is no more API nonsense. If you detect a siphon via API in this model, it's because someone already stole from you and may have done so again (the assets API only updates every six hours, if I recall correctly). The gameplay upside is that there are now vastly more opportunities for player interaction surrounding the siphons. Instead of a small team of logistics players monitoring the API and responding to them as needed - and mind you, as they're the only ones who can put the goo back into the silos, they are the only ones who do this - anyone can do siphon patrols, because all they have to do is shoot the things. On the flipside, it's no longer sufficient as an attacker to just spam a bunch of siphons and then ignore them, knowing that they're causing a bunch of extra effort for the logisticians and causing damage (in the form of the moongoo that the siphon destroys). If a player using siphons for guerilla warfare wants to cause harm, they have to stay in the area, monitor their siphons, return to actually loot them, or they do nothing. This change would make it far more likely that opposing players actually encounter each other and require active gameplay input on both sides, instead of the relatively passive low interaction model they drive now, solve the problem of the API, and do so in a way that doesn't change the overall function of siphons nor needlessly punch reaction operators and other legitimate POS-havers in the balls. +1 for this idea... As long as the steal material functions within a few seconds, I.e. Below the targeting delay of pos defenses,. "surrender your ego, be free". innuendo.
solo? There is a new hope http://turamarths-evelife.blogspot.com/2014/05/ok-now-im-betting-man.html |
Derrick Miles
EVENumbers
2300
|
Posted - 2014.08.20 03:01:00 -
[15] - Quote
CCP FoxFour wrote:Doesn't matter, not the point of this thread. Please stay on topic. I'd like to try and help with the reproduction of this but unfortunately my player corp hasn't been updated on the latest mirror and I would need to wait a week before being able to deploy a POS with the new system if I started another corp. Any chance you could update my corp history on the test server? |
Antylus Tyrell
MASS A DEATH Mordus Angels
0
|
Posted - 2014.08.20 11:20:00 -
[16] - Quote
If it is possible to detect them by api then many of the large moon owning alliances still have a very long response time. I suspect that this is just an attempt to get them removed from the game. Since they are causing a real headache for the the alliances that want to own hundreds of moons, and don't care to check them. So hopefully if this is a problem it can be fixed.
As for creating an extra step as suggested by mynna... why? I already interact with my siphons on a regular basis. The logistics of siphoning a moon over days already gives numerous attempts for you to kill me. If your logistic guys dont like the work, the solution is simple, downsize the number of moons you own.
|
Gossamer DT
Wildly Inappropriate Goonswarm Federation
110
|
Posted - 2014.08.20 14:42:00 -
[17] - Quote
Antylus Tyrell wrote:If it is possible to detect them by api then many of the large moon owning alliances still have a very long response time. I suspect that this is just an attempt to get them removed from the game. Since they are causing a real headache for the the alliances that want to own hundreds of moons, and don't care to check them. So hopefully if this is a problem it can be fixed.
As for creating an extra step as suggested by mynna... why? I already interact with my siphons on a regular basis. The logistics of siphoning a moon over days already gives numerous attempts for you to kill me. If your logistic guys dont like the work, the solution is simple, downsize the number of moons you own.
Spoken like a true risk avoiding pilot. who is your main, and what does he do? |
Antylus Tyrell
MASS A DEATH Mordus Angels
0
|
Posted - 2014.08.20 15:29:00 -
[18] - Quote
[/quote]
Spoken like a true risk avoiding pilot.[/quote]
There is already so much risk involved with a successful siphoning operation. POS defenses, moving the goo back home. Gate camps. If you want to make it so that siphons are not a passive income, okay lets discuss that. But then moons should not be a passive income either, make your logistics's guys have to actually do some work for the alliance.
|
Gossamer DT
Wildly Inappropriate Goonswarm Federation
110
|
Posted - 2014.08.20 15:56:00 -
[19] - Quote
I will give you that moon is passive, if you setup correctly, but lets not go crazy here and say that logi guys don't work enough all ready. Have you installed any ihub upgrades lately? oh sorry my bad NPC dweller who is your main, and what does he do? |
Alavaria Fera
GoonWaffe
6386
|
Posted - 2014.08.22 04:51:00 -
[20] - Quote
Gossamer DT wrote:I will give you that moon is passive, if you setup correctly, but lets not go crazy here and say that logi guys don't work enough all ready. Have you installed any ihub upgrades lately? oh sorry my bad NPC dweller Doubtless they have a secret gsf director alt which does indeed do it
And is about to drop our sov ^^ Delicious goon ((tech nerf, siphon, drone assist, supercap)) tears.
Taking a wrecking ball to the futile hopes and broken dreams of skillless blobbers. |
|
Mara Tessidar
Dark Star Safari Goonswarm Federation
1142
|
Posted - 2014.08.22 05:05:00 -
[21] - Quote
"Please stay on topic, or else" |
KIller Wabbit
The Scope Gallente Federation
710
|
Posted - 2014.08.22 05:07:00 -
[22] - Quote
Easy fix. Stop reporting silo levels completely. CCP .. always first with the wrong stuff CSM .. CCP Shills with a vacation plan
|
James Amril-Kesh
4S Corporation Goonswarm Federation
11274
|
Posted - 2014.08.22 05:12:00 -
[23] - Quote
CCP FoxFour wrote:The main point is we really appreciate discretion in these kinds of things, and publicly posting just makes us really not like you very much. In crazy cases if we know your character or account you may even find your API restuls suddenly have the following appended to them: Your actions speak louder than your words. It's been quite apparent for some time now that you (CCP) respond a lot better to issues raised on public fora than you do in private. Enjoying the rain today? ;) |
General Nusense
Not Posting With My Main
252
|
Posted - 2014.08.22 05:27:00 -
[24] - Quote
Gossamer DT wrote:I will give you that moon is passive, if you setup correctly, but lets not go crazy here and say that logi guys don't work enough all ready. Have you installed any ihub upgrades lately? oh sorry my bad NPC dweller
you have 11k people in your alliance, you have more than enough people to actually check the pos structures. if this is a problem with 11,000 players, i suggest you get more people to help out.
now please tell us why you cannot monitor you moon empire and install upgrades in ihubs with 11k people.
inb4
deflecting the question with out answering and attacking one of the following:
not posting with your main your opionion dosent matter because you are posting w/an alt shut up nobody grr goons etc. Made a signature so I am taken seriously on the forums, since thats the only thing they are good for. |
Derrick Miles
EVENumbers
2924
|
Posted - 2014.08.22 05:33:00 -
[25] - Quote
James Amril-Kesh wrote:CCP FoxFour wrote:The main point is we really appreciate discretion in these kinds of things, and publicly posting just makes us really not like you very much. In crazy cases if we know your character or account you may even find your API restuls suddenly have the following appended to them: Your actions speak louder than your words. It's been quite apparent for some time now that you (CCP) respond a lot better to issues raised on public fora than you do in private. Doesn't really excuse airing out bugs and glitches in public. |
James Amril-Kesh
4S Corporation Goonswarm Federation
11274
|
Posted - 2014.08.22 05:52:00 -
[26] - Quote
No you're right, better that they're whispered among friends while CCP refuses to acknowledge the problem. Enjoying the rain today? ;) |
Evelgrivion
Calamitous-Intent Feign Disorder
302
|
Posted - 2014.08.22 06:54:00 -
[27] - Quote
mynnna wrote:I know it's not what you're asking for, but the better way to fix this has nothing to do with changing the API. Instead, have a design team make the following tweaks:
- Siphons no longer take materials on an hourly basis, they merely keep track of how long they would take.
- To steal material, a "Steal Material" option in the dropdown menu of the siphon must be used. This would transfer the appropriate amount of material into the siphon as well as destroys the portion it's supposed to.
It's that simple! The upside to you, of course, is no more API nonsense. If you detect a siphon via API in this model, it's because someone already stole from you and may have done so again (the assets API only updates every six hours, if I recall correctly). The gameplay upside is that there are now vastly more opportunities for player interaction surrounding the siphons. Instead of a small team of logistics players monitoring the API and responding to them as needed - and mind you, as they're the only ones who can put the goo back into the silos, they are the only ones who do this - anyone can do siphon patrols, because all they have to do is shoot the things. On the flipside, it's no longer sufficient as an attacker to just spam a bunch of siphons and then ignore them, knowing that they're causing a bunch of extra effort for the logisticians and causing damage (in the form of the moongoo that the siphon destroys). If a player using siphons for guerilla warfare wants to cause harm, they have to stay in the area, monitor their siphons, return to actually loot them, or they do nothing. This change would make it far more likely that opposing players actually encounter each other and require active gameplay input on both sides, instead of the relatively passive low interaction model they drive now, solve the problem of the API, and do so in a way that doesn't change the overall function of siphons nor needlessly punch reaction operators and other legitimate POS-havers in the balls.
No bueno. This would get rid of the current inherent loss that Cyphons provide. Its not a cost effective means of messing with people, but then again, neither is suicide ganking empty hulls. Suck it up and deal with the lost income; EVE is supposed to be harsh. |
Baneken
Arctic Light Inc. Arctic Light
307
|
Posted - 2014.08.22 06:57:00 -
[28] - Quote
KIller Wabbit wrote:Easy fix. Stop reporting silo levels completely.
This, one of the best solutions for this problem and it also limits the amounts of moons you can have with a "human factor". |
PotatoOverdose
Handsome Millionaire Playboys Mordus Angels
2060
|
Posted - 2014.08.22 07:24:00 -
[29] - Quote
Evelgrivion wrote:Siphons are already too weak as it is; they shouldn't be 100% worthless against alliances willing to no-life themselves to their towers. CFC dudes pushing to nerf siphon effectiveness is nothing new, they've been doing it for a while now. |
Quesa
D00M. Northern Coalition.
27
|
Posted - 2014.08.22 07:28:00 -
[30] - Quote
thetwilitehour wrote:[quote=CCP FoxFourI mean, you have a goddamned group of players who advocate to you and get FLOWN TO ICELAND because you had a developer ACTIVELY CHEATING AND COVERING IT UP. Your response to someone making it known that ONE OF YOUR EMPLOYEES WAS CHEATING was to BAN THAT PLAYER. So please shut up about your desire for private whistle blowers. Man, you guys are gonna beat that horse until the game servers get pulled down.
On topic, why not just have a notification that a silo is at 90% capacity, or something close to that? |
|
|
|
|
Pages: [1] 2 :: one page |
First page | Previous page | Next page | Last page |