The following warnings occurred:
Warning [2] Use of undefined constant SAPI_NAME - assumed 'SAPI_NAME' (this will throw an Error in a future version of PHP) - Line: 3388 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3388 errorHandler->error
/showthread.php 116 build_archive_link
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/inc/functions.php 3324 build_forum_breadcrumb
/showthread.php 195 build_forum_breadcrumb
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/showthread.php 195 build_forum_breadcrumb




SphereCommunity / Sphere 0.56d / Script Submissions v / Negotiate Features - AssistUO/Razor


Post Reply 
 
Thread Rating:
  • 1 Votes - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Negotiate Features - AssistUO/Razor
Author Message
Feeh
Sphere Developer
*****

Posts: 156
Likes Given: 6
Likes Received: 40 in 29 posts
Joined: Sep 2012
Reputation: 4



Post: #52
RE: Negotiate Features - AssistUO/Razor
The negotiation protocol uses the packet command 240 (0xF0) the same used by newer clients to move the char around.
Yeah, they "can" coexist, their sizes are way different but it would require a lot of effort filtering the packet content based just on packet length, and since we have no control of how the packets are changed over time, we can not produce a reliable code to work with both feature negotiation and the new movement request

The reason you can still use the features negotiator with newer clients is that sphere does not use the new movement by default (it is not finished but is there), you will have to choose between having a feature negotiator or a more reliable (as we expect) movement control IF EA does not kill the old movement

There is no reason to be worried YET, you can safely use the negotiator even with latest clients as long you keep the new movement disabled on INI (FEATURE_SA_MOVEMENT 02). Just have in mind it can be broken anytime in the future newer clients
Feeh/Epila - Nightly releases / SphereWiki / Github Issues / Sphere's GitHub
(This post was last modified: 05-17-2014 03:10 AM by Feeh.)
05-17-2014 03:09 AM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Negotiate Features - AssistUO/Razor - Feeh - 05-17-2014 03:09 AM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us | SphereCommunity | Return to Top | Return to Content | Mobile Version | RSS Syndication