SphereCommunity / General Discussion / UO/Sphere Discussion v / Change-Speed Detectation


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Change-Speed Detectation
Author Message
XuN
Sphere Developer
*****

Posts: 852
Likes Given: 102
Likes Received: 156 in 119 posts
Joined: Jul 2013
Reputation: 30



Post: #21
RE: Change-Speed Detectation
(03-17-2014 02:09 AM)Feeh Wrote:  What about the DEBUGF_WALK 02000? It does use the F0/F1 packet?

Right now it is being called from 02 packet, F0 needs to be updated and F1 created.
03-17-2014 04:30 AM
Find all posts by this user Like Post Quote this message in a reply
Ben
Sphere Developer
*****

Posts: 612
Likes Given: 2
Likes Received: 123 in 70 posts
Joined: Mar 2010
Reputation: 18

SphereCommunity
Post: #22
RE: Change-Speed Detectation
DEBUGF_WALK is just used to display some debug information in walking... which is why I find it weird that DEBUGF_WALKCODE is used to activate a feature. A broken one I might add, but a feature nonetheless.

I'll check it out to see if I can get this to work properly...

F0,F1 packets are only used if FEATURE_SA_MOVEMENT is activated in sphere.ini (which has been disabled due to not working properly)
That's another issue we need to look into Smile
AxisII's current version: 2.0.4j
AxisII SourceCode on Github
AxisII up to date changelog
(This post was last modified: 03-17-2014 07:18 AM by Ben.)
03-17-2014 07:15 AM
Visit this user's website Find all posts by this user Like Post Quote this message in a reply
Coruja
Sphere Developer
*****

Posts: 987
Likes Given: 5
Likes Received: 226 in 187 posts
Joined: Jul 2012
Reputation: 7

Dimension Shard
Post: #23
RE: Change-Speed Detectation
any news about the packet "0bf 01" and "0bf 02" to regenerate walk keys? Smile
Code:
//Send new walk keys to client
[FUNCTION InitializeFastWalkKeys]
SENDPACKET 0bf W29 W01 D<R1000000000> D<R1000000000> D<R1000000000> D<R1000000000> D<R1000000000> D<R1000000000>

[FUNCTION AddFastWalkKey]
SENDPACKET 0bf W09 W02 D<R1000000000>

//Check walk packets (add PACKET2=ClientWalkRequest on sphere.ini)
[FUNCTION ClientWalkRequest]
SERV.B <LOCAL.0> <LOCAL.1> <LOCAL.2> <LOCAL.3> <LOCAL.4> <LOCAL.5> <LOCAL.6> (packet length: <LOCAL.NUM>)
Using DEBUGF_WALKCODES these functions can send the keys to the client, and the client will receive it and use on next step(s). But even with these numbers set the char still unable to walk
(This post was last modified: 03-24-2014 05:32 AM by Coruja.)
03-24-2014 05:24 AM
Find all posts by this user Like Post Quote this message in a reply
Ben
Sphere Developer
*****

Posts: 612
Likes Given: 2
Likes Received: 123 in 70 posts
Joined: Mar 2010
Reputation: 18

SphereCommunity
Post: #24
RE: Change-Speed Detectation
Nothing yet... been busy with other things
AxisII's current version: 2.0.4j
AxisII SourceCode on Github
AxisII up to date changelog
03-24-2014 05:35 AM
Visit this user's website Find all posts by this user Like Post Quote this message in a reply
xfolder
Apprentice
*

Posts: 9
Likes Given: 0
Likes Received: 0 in 0 posts
Joined: Mar 2012
Reputation: 0



Post: #25
RE: Change-Speed Detectation
It could be useful for someone.. Wink

Code:
[function f_speedhack]
ref1=<local.char>
local.times=200
if (<ref1.ctag0.times> =< <local.times>)
    if (<ref1.ctag0.lastevent>==<ref1.lastevent>)
        ref1.ctag0.same += 1
    endif
    ref1.ctag0.times += 1
elif (<ref1.ctag0.same> > 11)
    serv.log [SPEEDHACK] UID: <ref1.uid> ACCOUNT: <ref1.account> NAME: <ref1.name>
    ref1.ctag0.same
    ref1.ctag0.times
else
    ref1.ctag0.same
    ref1.ctag0.times
endif
ref1.ctag.lastevent=<ref1.lastevent>

Add PACKET2=f_speedhack in sphere.ini
(This post was last modified: 09-23-2014 07:54 AM by xfolder.)
09-23-2014 07:53 AM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Forum Jump:


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

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