|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Razin
The xDEATHx Squadron Legion of xXDEATHXx
231
|
Posted - 2012.02.06 12:25:00 -
[1] - Quote
Nova Fox wrote:They can inhumanly press Dscan every second and if there is a newer entry than them they cloak up until number of entries matches them again.
That is all. It's pretty clear the the current d-scan needs to be reworked for delayed local. This is stated in pretty much every topic advocating delayed local.
For example, my preference for the new d-scan would be to have the auto passive and the manual active modes (with some range and detectability tradeoffs for both), where the liberal use of the active scanner would tun your ship into a warpable signature. |
Razin
The xDEATHx Squadron Legion of xXDEATHXx
231
|
Posted - 2012.02.06 12:37:00 -
[2] - Quote
I'thari wrote:I suspect it's much simplier: any bot program will just have access to info server sends to client... and client knows who is in system in any given time and where he is (at least if old vid with GM menu is to be belived). So, by removing local you won't change anything for bots, but real people will have more trouble telling if there's one in system... So, the GM client couldn't possibly request this info from the server? |
Razin
The xDEATHx Squadron Legion of xXDEATHXx
231
|
Posted - 2012.02.06 13:46:00 -
[3] - Quote
Buruk Utama wrote:I'thari wrote:I suspect it's much simplier: any bot program will just have access to info server sends to client... and client knows who is in system in any given time and where he is (at least if old vid with GM menu is to be belived). So, by removing local you won't change anything for bots, but real people will have more trouble telling if there's one in system... Pretty much this. Bots monitor the data coming into the client and when someone enters the system your client is forcefully updated. The bots recognize this signature change and therefore know immediately that someone came into system and to dock up or start their friend/foe subroutine before docking up. You don't get the point because you are too stupid. No biggie, here it is simplified: bots detect changes in system population because we have instant local. Hope that helps. |
Razin
The xDEATHx Squadron Legion of xXDEATHXx
231
|
Posted - 2012.02.06 15:14:00 -
[4] - Quote
Nova Fox wrote:Okay lets go hypothetical and I am not an idiot bot programmer and let my bots do something a person cant.
I have 100 bots and I sync them to dscan one ship every 1/100th of a second from the next one and have them setup to talk to each other. The moment one of them sees +1 more ship than them theyll cloak up. Only thing a bot needs to do is count dscan results not much different from current bots.
Now you might be smart enough to smash dscan as soon as you jump in and before you decloak/recloak to go hunting but in tha tone instance boom they're gone. IMO your mistake is in looking for a flaw in the current d-scan that works with current local. Granted, CCP is known for taking the easy way out (see WTZ); however there is hope that d-scan gets some severe updates if and when delayed local is implemented.
|
Razin
The xDEATHx Squadron Legion of xXDEATHXx
237
|
Posted - 2012.02.07 19:51:00 -
[5] - Quote
Msgerbs wrote:Razin wrote:Nova Fox wrote:They can inhumanly press Dscan every second and if there is a newer entry than them they cloak up until number of entries matches them again.
That is all. It's pretty clear the the current d-scan needs to be reworked for delayed local. This is stated in pretty much every topic advocating delayed local. For example, my preference for the new d-scan would be to have the auto passive and the manual active modes (with some range and detectability tradeoffs for both), where the liberal use of the active scanner would tun your ship into a warpable signature. Please for the love of god no. No what? |
|
|
|