Go Back   EQEmulator Home > EQEmulator Forums > Development > Development::Development

Development::Development Forum for development topics and for those interested in EQEMu development. (Not a support forum)

Reply
 
Thread Tools Display Modes
  #1  
Old 08-12-2014, 03:51 PM
lerxst2112
Demi-God
 
Join Date: Aug 2010
Posts: 1,742
Default

The concept of a "perception bubble" is not terribly complex for a simple implementation assuming the client knows about entities in a circular region around itself. It can get quite a bit more complicated if you exclude information based on stuff like line of sight, z-height, etc. but there's generally not a ton of benefit to doing that.

The problem you might run into is the client. Usually there's some cooperation needed between client and server to make sure they agree on things like number of entities and having the client be able to request more information from the server if for instance it gets a movement update for an entity it doesn't know about. The client can also be a bit proactive about despawning entities that are out of range without the server specifically telling it to.

I haven't used ShowEQ or MQ2 on a live server for a while, so they may already have a system that does this. It always seemed like the next logical step to combat ShowEQ during the time where they were actively trying to stop it.

Last edited by lerxst2112; 08-12-2014 at 03:52 PM.. Reason: Typos and wording.
Reply With Quote
  #2  
Old 08-12-2014, 06:02 PM
Shin Noir's Avatar
Shin Noir
Legendary Member
 
Join Date: Apr 2002
Location: Seattle, WA
Posts: 506
Default

Quote:
Originally Posted by lerxst2112 View Post
The concept of a "perception bubble" is not terribly complex for a simple implementation assuming the client knows about entities in a circular region around itself. It can get quite a bit more complicated if you exclude information based on stuff like line of sight, z-height, etc. but there's generally not a ton of benefit to doing that.

The problem you might run into is the client. Usually there's some cooperation needed between client and server to make sure they agree on things like number of entities and having the client be able to request more information from the server if for instance it gets a movement update for an entity it doesn't know about. The client can also be a bit proactive about despawning entities that are out of range without the server specifically telling it to.

I haven't used ShowEQ or MQ2 on a live server for a while, so they may already have a system that does this. It always seemed like the next logical step to combat ShowEQ during the time where they were actively trying to stop it.
I normally use MQ, it seems if you aren't near an entity the update packets of where the entity is located (if it's moving) is looser, e.g. you may only get an update packet every 12-24s instead of instantly, I've never seen an entity not sent to the cilent..

I have a rough idea of how to implement this, and yeah, not trying to depop the non-LOS or anything complicated like that, more just trying to stop cross-zone targetting and knowledge. Probably like a ~1k radius (or a reasonable view distance in an open field number) of spawned entities..

if it's too complicated, I may just drop the idea. But it'd be nice to lessen the benefits of MQ.
__________________

~Shin Noir
DungeonEQ.com
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

   

All times are GMT -4. The time now is 03:02 PM.


 

Everquest is a registered trademark of Daybreak Game Company LLC.
EQEmulator is not associated or affiliated in any way with Daybreak Game Company LLC.
Except where otherwise noted, this site is licensed under a Creative Commons License.
       
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Template by Bluepearl Design and vBulletin Templates - Ver3.3