Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Dal Thrax
Caldari Multiverse Corporation The Core Collective
|
Posted - 2007.03.19 16:59:00 -
[1]
From the patch notes:
Forcefields do not deploy in an activated state. If the password for a forcefield has not been set, the forcefield is not active and therefore not visible.
I assume this means that if you don't have a password set tbe forcefield will turn off after the next patch. Everyone please set passwords on your POSes today. I don't want to have to hear the forum posts when somebody who didn't get the memo looses a POS.
Thanks Dal
|
Shiwan Khan
Vengeance of the Fallen Curse Alliance
|
Posted - 2007.03.19 17:05:00 -
[2]
Edited by: Shiwan Khan on 19/03/2007 17:01:26 or some capitals or even supercapitals
Edit - 1st! ive never been first before :) ____________________________________________
"XirtamVOTF -> Spiritual Father of CA." - Lallante
AEKDB |
turnschuh
Brutor tribe
|
Posted - 2007.03.19 17:06:00 -
[3]
seams tommorow is the best day to run around in 0.0 and steal ships
|
Pepperami
Art of War Cult of War
|
Posted - 2007.03.19 17:08:00 -
[4]
Wait so I could be flying along and go 'omg that pos is offline', warp to it and the guns are active?
BAIT POS TIME
|
Cmdr Delrox
Black Lance Against ALL Authorities
|
Posted - 2007.03.19 17:29:00 -
[5]
Originally by: Pepperami Wait so I could be flying along and go 'omg that pos is offline', warp to it and the guns are active?
BAIT POS TIME
I think Singularity has been using the POS bait tactic already. We got quite a few ships from there a couple weeks ago, when they put up a new POS and forgot to set it up correctly. Poor samthenoob!
Alt Posting
Death to Dark Shikari |
Kam'Sing Tung
|
Posted - 2007.03.19 18:58:00 -
[6]
*snip* Posting with an unidentified character and characters in NPC corporations in this forum is prohibited. If you wish to participate in the discussions here, be sure to have your corporation and or alliance status ticked in your forum settings. - Kreul Intentions ([email protected])
|
Empyre
Domestic Reform
|
Posted - 2007.03.19 19:32:00 -
[7]
now they just need to make it so passwords set on ships stay activeuntil it changes hands or something.. well they don't need to, but it would make me bounce off my own shields less often!
People argue when their personal views are at odds, whereas a debate is a more formal method of analyzing the angles of an issue |
Joshua Foiritain
Gallente Coreli Corporation Corelum Syndicate
|
Posted - 2007.03.19 19:52:00 -
[8]
Its not in the patch notes...? -----
[Coreli Corporation Mainfrane] |
Xeron Silverblade
Esthar Industries
|
Posted - 2007.03.19 20:09:00 -
[9]
interesting point.. true.
|
patteSatan
Celtic Anarchy Anarchy Empire
|
Posted - 2007.03.19 20:17:00 -
[10]
Originally by: Pepperami Wait so I could be flying along and go 'omg that pos is offline', warp to it and the guns are active?
BAIT POS TIME
I will love to be there with you m8!
<br> ...you women are creepy, but amusing as hell.
|
|
Ephemeral Waves
The Nine Gates Executive Outcomes
|
Posted - 2007.03.19 20:26:00 -
[11]
Perhaps you could point out where it says that in the patch notes? Otherwise, you're just trolling.
Eph.
Now Recruiting |
Elve Sorrow
Amarr Shinra Lotka Volterra
|
Posted - 2007.03.19 20:43:00 -
[12]
Read the thread where Kieron announces the patchnotes, it has a few more updates.
|
Dal Thrax
Caldari Multiverse Corporation The Core Collective
|
Posted - 2007.03.19 20:49:00 -
[13]
Originally by: Joshua Foiritain Its not in the patch notes...?
The quoted text was copied and pasted from the patch notes. The item was added in green at some point after the formal posting. The item was removed after my post was made to COAD. It is my guess that the devs have decided to hold off on making the mentioned change for reasons listed in my initial post.
Dal
|
Farrellus Cameron
Sturmgrenadier Inc R i s e
|
Posted - 2007.03.19 20:50:00 -
[14]
Originally by: Elve Sorrow Read the thread where Kieron announces the patchnotes, it has a few more updates.
Read the patchnotes and read the thread and still fail to see any reference to this POS change mentioned by the OP. Anyone care to shed light as to where this is supposedly listed? ----------------------------------------------------
|
Hast
Refused.
|
Posted - 2007.03.19 20:57:00 -
[15]
one question, if there is no pos shield present, does that mean that the people that are next to the POS and the modules are vunerable?
Originally by: omeega PICTURE TOO BIG, KGB INCOMING HAVE FUN.
|
|
kieron
|
Posted - 2007.03.19 21:01:00 -
[16]
There was an internal mix-up regarding the patch note. The announcement thread and patch notes have been updated, I will also post the update here:
Note: The following is a clarification of an earlier patch note that was added and later retracted. The following will not be added in the patch being deployed on 20 March as a part of Revelations 1.4, but will be deployed in the near future in a server-side hotfix-
Previous to this patch, forcefields did not deploy in a completely activated state. If the password for a forcefield was not set, entry into the forcefield bubble was not restricted, yet targeting structures through the field was not possible. Now, forcefields must have a password set before they are activated, thus restricting entry and targeting only after activation.
We apologize for the misunderstanding and confusion this caused.
kieron Community Manager, EVE Online |
|
Dal Thrax
Caldari Multiverse Corporation The Core Collective
|
Posted - 2007.03.19 21:05:00 -
[17]
Edited by: Dal Thrax on 19/03/2007 21:04:33 Deleted. Dev answered the question.
Dal
|
Ephemeral Waves
The Nine Gates Executive Outcomes
|
Posted - 2007.03.19 21:53:00 -
[18]
Edited by: Ephemeral Waves on 19/03/2007 21:49:57
Originally by: kieron Now, forcefields must have a password set before they are activated, thus restricting entry and targeting only after activation.
This is still confusing. I admit that I have never set up a POS ... But currently a POS is set up and you can set it to allow bubble entry to corp or to alliance and you can set it to require a password or not. So a POS is generally set to allow alliance entry to the bubble without a password.
Are you saying that now ALL entry to the bubble will require a password?
Eph.
Edit: I am of course referring to after this patch actually is put in.
Now Recruiting |
Koronos
Interstellar eXodus R0ADKILL
|
Posted - 2007.03.19 22:07:00 -
[19]
Any chance of some community input and clarification before this is put in? My guess this is a fix for a "symptom" and will enable additional "symptoms".
My personal opinion is that this move will be disastrous, but I'm certainly not the expert, so I'd like to see community input taken into account first hand if possible.
Pleaseandthankyouverymuch.
Koronos
P.S. on a completely unrelated note, the forums are a much better place with an ungagged Hast.
|
Lowanaera
Amarr 1st Praetorian Guard Vigilia Valeria
|
Posted - 2007.03.19 23:48:00 -
[20]
This isn't a fix, there's no change here, all they're doing is announcing something that is already the case on TQ as many people seem unaware of it. If you do not set a password, there is no forcefield and anyone can enter the shields or target ships inside the shields. Most of the claims of devhaxsploits from people shooting ships inside of POS shields is due to the lack of awareness of this issue.
If you already knew about this, nothing is changing tomorrow with the patch. If you didn't, go set passwords now and thank $diety you've been lucky up until now.
|
|
Sentinel Eeex
Caldari Gekidoku Koroshiya Buntai
|
Posted - 2007.03.20 00:26:00 -
[21]
Originally by: Lowanaera This isn't a fix, there's no change here, all they're doing is announcing something that is already the case on TQ as many people seem unaware of it. If you do not set a password, there is no forcefield and anyone can enter the shields or target ships inside the shields. Most of the claims of devhaxsploits from people shooting ships inside of POS shields is due to the lack of awareness of this issue.
If you already knew about this, nothing is changing tomorrow with the patch. If you didn't, go set passwords now and thank $diety you've been lucky up until now.
Except the fact we've already had a thread related to "shooting inside POS shields" issue, got different responses from different parties, people had/have different experiences, and POS behavious is not documented anywhere.
Just a week ago, we've had a POS setup w/o a password, where enemies could get inside bubble, but we couldn't target each other. Few months ago, you couldn't even enter POS shield (no matter if it had password) if you were not from same corp/alliance. After this patch, we'll seemingly be able to target ships inside forcefield if POS doesn't have password set?
When will we get bloody DOCUMENTATION for all these POS issues?
And I *really* like "lack of awareness" line. How, exactly, are we supposed to be 'aware', when it's not documented anywhere, and you get different responses from GMs/devs?
If CCP considers 'patch notes' as documentation...
|
Ifni
Developmental Neogenics Amalgamated
|
Posted - 2007.03.20 00:28:00 -
[22]
Originally by: kieron There was an internal mix-up regarding the patch note. The announcement thread and patch notes have been updated, I will also post the update here:
Note: The following is a clarification of an earlier patch note that was added and later retracted. The following will not be added in the patch being deployed on 20 March as a part of Revelations 1.4, but will be deployed in the near future in a server-side hotfix-
Previous to this patch, forcefields did not deploy in a completely activated state. If the password for a forcefield was not set, entry into the forcefield bubble was not restricted, yet targeting structures through the field was not possible. Now, forcefields must have a password set before they are activated, thus restricting entry and targeting only after activation.
We apologize for the misunderstanding and confusion this caused.
Confusion? I'm generally very tolerant of CCP and the stealth nerfs, but when I found a bunch of POS, with no forcefields active, I warped there in my capsule and took a Scorpion (http://homepages.nildram.co.uk/~theodjs/scorp.txt)and Flycatcher (http://homepages.nildram.co.uk/~theodjs/flycatcher.txt). Since I figured the POS was faulty I petitioned this as a bug, and only now, after wasting the GM's time, is it revealed that this is in fact a feature.
I understand it was a mistake, and I'm not expecting reimbursement for the ships, but maybe now you'll realise that its wasting precious GM time too.
You take what is offered. And that must sometimes be enough. |
Desash
The Extremely Norty Gankers Union
|
Posted - 2007.03.20 17:37:00 -
[23]
Originally by: Lowanaera This isn't a fix, there's no change here, all they're doing is announcing something that is already the case on TQ as many people seem unaware of it. If you do not set a password, there is no forcefield and anyone can enter the shields or target ships inside the shields. Most of the claims of devhaxsploits from people shooting ships inside of POS shields is due to the lack of awareness of this issue.
If you already knew about this, nothing is changing tomorrow with the patch. If you didn't, go set passwords now and thank $diety you've been lucky up until now.
I've got the impression that there IS actually a slight change, albeit cosmetic. The orignal, now withdrawn, patchnote stated according to OP '...... If the password for a forcefield has not been set, the forcefield is not active and therefore not visible.' Maybe many of us have been confusing POS shields with forcefields and that when this 'fix' is implemented, if a password isn't set then not only will the forcefield not be active (as is the case now apparently) but also you won't even see the forcefield (ie the thing we percieve as shields).
|
Mattduk
Gallente Universal Army
|
Posted - 2007.03.20 17:47:00 -
[24]
Originally by: kieron Previous to this patch, forcefields did not deploy in a completely activated state.
This means that before this patch, forcefields did not do all that they were supposed to do.
Originally by: kieron If the password for a forcefield was not set, entry into the forcefield bubble was not restricted, yet targeting structures through the field was not possible.
This means that if you did not set a password for your POS, anyone could fly in and out of the sphere, however they could not lock anything inside the sphere
Originally by: kieron Now, forcefields must have a password set before they are activated, thus restricting entry and targeting only after activation.
This means that after the patch, if you do not set a password then not only can anyone fly in and out of your POS sphere, but they can also target items within that sphere.
So, in summary, set a password and then you're covered.
Kind regards Mattduk
|
Xiaodown
Dark-Rising
|
Posted - 2007.03.20 20:57:00 -
[25]
Edited by: Xiaodown on 20/03/2007 20:54:17 I would assume that you can still enter POS's based on standings*.
Maybe it's just me, but I seem to think that the only logical way that POS authentication works should be like this:
Check POS -> personal then POS -> Corp then POS -> Alliance then PASSWORD CHECK if all these fail -> bounce ship, check standings, and start shooting if applicable.
But, then, things in Unix make sense, too. /etc/nsswitch.conf works like this - when you log into a machine, it checks your username and password combo versus local files, then ldap, then nisplus, then nis/yp, then if all these fail -> deny user access.
Everything in life can be solved with a flow chart or a venn diagram!
~Xiao
EDIT: In response to "does that mean we will have to set a password to enter any pos?" Also, keep in mind the word assume here. We all know what it means.
|
Helmut 314
Amarr J.H.E.N.R Pure.
|
Posted - 2007.03.20 21:25:00 -
[26]
Originally by: Desash
I've got the impression that there IS actually a slight change, albeit cosmetic. The orignal, now withdrawn, patchnote stated according to OP '...... If the password for a forcefield has not been set, the forcefield is not active and therefore not visible.' Maybe many of us have been confusing POS shields with forcefields and that when this 'fix' is implemented, if a password isn't set then not only will the forcefield not be active (as is the case now apparently) but also you won't even see the forcefield (ie the thing we percieve as shields).
Cosmetic changes to POS seems to be all that CCP can manage. I and many with me would be very happy if any real improvement was prioritized, but that seems to be at the bottom of the list permanently.
________________________________
Trying is the first step of failure - Homer J Simpson |
Jotan Veer
Wings of Turul Curse Alliance
|
Posted - 2007.03.20 21:43:00 -
[27]
Edited by: Jotan Veer on 20/03/2007 21:42:55 I swear I would so make some people here set up a large POS including a full fit solo with a badger II (carrier deployment doesn't count) in deep 0.0 without escort and have them fuel it for a month and then unanchor the whole deal, before they are allowed to post anything regarding POS warfare.
So anyway;
POS shield = works even if the tower is offline (tried to kill an offline tower lately? You still gotta shoot down its shield bar)
POS forcefield = the 'bubble' around an online tower, didn't do much except protect POS structures before this patch if there wasn't a password set now there won't be any bubble after the patch if you don't set a password so n00b POS builders don't get confused.
Cosmetic change, mostly.
|
eeeweeezeee
Macabre Votum Tactical Narcotics Team
|
Posted - 2007.03.22 02:09:00 -
[28]
Quote: Now, forcefields must have a password set before they are activated, thus restricting entry and targeting only after activation.
does this mean that we can disable and re-enable our shields when ever we want? would be a good way to get around leaving the pos to deploy drones or fighters if you can deploy them and then just re-activate the shield when you are done. also, might be a good way to move that person that inevitably goes afk next to the ship maintenance array.
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |