Fly over Waypoint with no Stop
Posted: Mon Jan 07, 2013 4:46 pm
Like I promised I searched deeper for solution. I found out that in the past someone seems to tried it already.
I work with Rock“s RC3 so I found "WP_NO_STOP" in the player.lua on the bottom of "moveTo".
Wasn't declared so I had to add it in Setting.lua that I changed:
player.lua:
Bottom of moveTo
So it will work even it has no quick-turn on
bot.lua:
When a point Is reached it would be nice he didn't need to stop for code execution my solution
about Line 909
This has its limit you can't load a new file or make "GoThroughPortal" or leave the instance(by end of the file) but changing profile or inviate a other player/bot seems to be okay
By the way this thing works the bot run much less like a puppet and is a littel bit faster too, but this isnt finished I still need to add something in the waypoint tags, because at the moment I need turn off the feature one waypoint befor so I need:
to stop it befor execute the code and "moveTo".
also need a Zone to setup the point easier , because hitting the wall is very likly if you run this in Quick-Turn off so the bot needs may turn sooner, so I may pass to moveTo a extra buffer for the position that would be make setup old WP easier.
I work with Rock“s RC3 so I found "WP_NO_STOP" in the player.lua on the bottom of "moveTo".
Wasn't declared so I had to add it in Setting.lua that I changed:
player.lua:
Bottom of moveTo
Code: Select all
if (settings.profile.options.WP_NO_STOP ~= false) then
if (dontStopAtEnd ~= true) --[[or (settings.profile.options.QUICK_TURN == false)]] then
keyboardRelease( settings.hotkeys.MOVE_FORWARD.key );
end
else
keyboardRelease( settings.hotkeys.MOVE_FORWARD.key );
end
bot.lua:
When a point Is reached it would be nice he didn't need to stop for code execution my solution
about Line 909
Code: Select all
-- Execute it's action, if it has one.
if (settings.profile.options.WP_NO_STOP ~= false) then
if( wp.Action and type(wp.Action) == "string" and string.find(wp.Action,"%a") ) then
local actionchunk = loadstring(wp.Action);
assert( actionchunk, sprintf(language[150], __RPL.CurrentWaypoint) );
local co = coroutine.create(function () actionchunk(); end);
coroutine.resume(co);
end
else
if( wp.Action and type(wp.Action) == "string" and string.find(wp.Action,"%a") ) then
keyboardRelease( settings.hotkeys.MOVE_FORWARD.key ); yrest(200) -- Stop moving
local actionchunk = loadstring(wp.Action);
assert( actionchunk, sprintf(language[150], __RPL.CurrentWaypoint) );
actionchunk();
end
end
else
__WPL:advance();
-- Execute it's action, if it has one.
if (settings.profile.options.WP_NO_STOP ~= false) then
if( wp.Action and type(wp.Action) == "string" and string.find(wp.Action,"%a") ) then
local actionchunk = loadstring(wp.Action);
assert( actionchunk, sprintf(language[150], __WPL.CurrentWaypoint) );
local co = coroutine.create(function () actionchunk(); end);
coroutine.resume(co);
end
else
if( wp.Action and type(wp.Action) == "string" and string.find(wp.Action,"%a") ) then
keyboardRelease( settings.hotkeys.MOVE_FORWARD.key ); yrest(200) -- Stop moving
local actionchunk = loadstring(wp.Action);
assert( actionchunk, sprintf(language[150], __WPL.CurrentWaypoint) );
actionchunk();
end
end
end
By the way this thing works the bot run much less like a puppet and is a littel bit faster too, but this isnt finished I still need to add something in the waypoint tags, because at the moment I need turn off the feature one waypoint befor so I need:
Code: Select all
<waypoint x="4340" z="1026" y="679" WP_NO_STOP="false" > </waypoint>
also need a Zone to setup the point easier , because hitting the wall is very likly if you run this in Quick-Turn off so the bot needs may turn sooner, so I may pass to moveTo a extra buffer for the position that would be make setup old WP easier.
Code: Select all
<waypoint x="4340" z="1026" y="679" WP_NO_STOP="true" WP_ZONE="20" > </waypoint>