EQ2Harvest not moving.

tms

Well-Known Member
Hello.

Seems i am doing something wrong.

I got the newest version from SVN, tried first the normal, then the experimental.
I tried it first in the commonlands, since there were allready an pathing file so there cant be something wrong with it.

My problem at this point is, that eq2harvest refuses to move forward. In the innerspace console i get the following error message spammed: "Could not parse key combination MOVEFORWARD".

I made sure the key's in moveto.iss were correct (even if there is no #define MOVEFORWARD there).

I even added an #define MOVEWORWARD s (after setting autorun to s also). The error message stopped, but he did not start to move.

After this, i tried Autobot which worked fine and he moved around also without any problems.

I just dont know what i am doing wrong. Maybe anyone could give me an little hint.
 

Mortedamour

Active Member
Noticed this was borked myself last night, the problem is in moveto.iss. If you kept a backup of the old, copy it back and it should work again for you.
 

SuperNoob

Active Member
It is in the moveto.iss that was causing the issue and it is current in SVN now. Once the extension is updated make sure the keys defined in moveto.iss are the same as your in game keys and you should be good to go.

-SN
 

tms

Well-Known Member
Pygar said:
Also, make sure you've updated from the SVN. This was fixed some time ago...
I did an SVN update, and both, experimental and normal dont move, while eq2bot move without any problems. I dont know what's the matter.

I realized that (tried to type something in chat) he spamms "w" (which would be move forward). Sometimes he move a bit to the left, right or backwards. But he really refuses to move forward.

After the last update from SVN, IRC rev 120 and an new version of moveto.iss he stopped with the MOVEFORWARD spam in the innerspace console but that was all.
 

Cr4zyb4rd

Active Member
moveto.iss should be set to your autorun-toggle key, not move forward (misleading, i know, which is why we tried renaming it to AUTORUN which caused all of these issues in the first place, but that broke some legacy code) if it's only making the occasional brief stutter-step forward, that's the problem
 

tms

Well-Known Member
Edit at start:

What i now did was replace every MOVEFORWARD with AUTORUN, set #define AUTORUN 'num lock' with #define AUTORUN w (and did set autorun ingame to w of course) - and now it seems to work.





Cr4zyb4rd said:
moveto.iss should be set to your autorun-toggle key, not move forward (misleading, i know, which is why we tried renaming it to AUTORUN which caused all of these issues in the first place, but that broke some legacy code) if it's only making the occasional brief stutter-step forward, that's the problem
Currently i am using "moveto.iss Version 2.1.05 Updated: 05/11/07"

Movement keys are set to:

Code:
#define AUTORUN "num lock"
#define MOVEBACKWARD s
#define STRAFELEFT q
#define STRAFERIGHT e
#define TURNLEFT a
#define TURNRIGHT d
If i press each of this keys ingame they do what they should.

I just deleted my complete scripts + interface folders in my SVN + Innerspace directorys and dowloaded the complete SVN again.

I then copied the scripts + interface folder to my innerspace directory and after this i copied the \experimental\scripts + interface folder to \innerspace\

logged in, started eq2harvest and got again the following errormessage: "could not parse key combination 'MOVEFORWARD'.

eq2harvest.iss has "EQ2Harvest.iss Version 1.3.1"

"AUTORUN" is only found once in eq2harvest.iss, near the end:

Code:
atom atexit()
{
	ui -unload "${LavishScript.HomeDirectory}/Interface/EQ2Skin.xml"
	ui -unload "${UIPath}HarvestGUI.xml"

	SettingXML[${ConfigFile}]:Unload
	SettingXML[${HarvestFile}]:Unload

	if ${Me.IsMoving}
	{
		press MOVEFORWARD
	}
	press -release MOVEBACKWARD
	press -release STRAFELEFT
	press -release STRAFERIGHT
	press -release TURNLEFT
	press -release TURNRIGHT
}
moveto.iss got 2 places with MOVEFORWARD inside, also at the end:

Code:
;Very Basic object to manage auto-run states
function StopRunning()
{
	if ${Me.IsMoving}
	{
		do
		{
			press MOVEFORWARD
			wait 1
		}
		while ${Me.IsMoving}
	}
}

function StartRunning()
{
	if !${Me.IsMoving}
	{
		do
		{
			press MOVEFORWARD
			wait 1
		}
		while !${Me.IsMoving}
	}
}

I am glad you took the time to answer, i am sure i am doing something wrong, but i cant see what :/
 
Last edited:

Cr4zyb4rd

Active Member
I am glad you took the time to answer, i am sure i am doing something wrong, but i cant see what :/
Ignoring those answers for a start. Nobody suggested you do anything beyond update to the latest stable SVN files, and make sure that your key definitions in moveto were in fact set to the keys you use in-game. The files in the experimental directory are just that.
 

tms

Well-Known Member
Cr4zyb4rd said:
Ignoring those answers for a start. Nobody suggested you do anything beyond update to the latest stable SVN files, and make sure that your key definitions in moveto were in fact set to the keys you use in-game. The files in the experimental directory are just that.
That was what i did first, even before i wrote the first post. I tried it with the stable version, used the experimental after that.

I made sure my keys were set how they should.

It's not like i ignored what you wrote.
 

hegvape

Well-Known Member
So whats up with the harvester... Been using it for a long time and never had any problems... downloaded latest files today.. (should have kept a copy of the old ones) and now suddenly it either doesnt move or starts strafeing...
My keys are the same as they always have been.. w,s,a,d,q,e+num lock.

Kindly

Val
 

hegvape

Well-Known Member
It works just fine in First Person!
Used to work in third person for me.. Gonna check options.. and see if I find anything, I know I changed something a few days ago but cant remember what.
 

hegvape

Well-Known Member
Here's the solution that worked for me! (Thanks to SN for his support on irc)

In EQ2 - 'Options/Controls/View Options' I changed the 'Free look controls' to 'Avatar relative'.

Mine was set to 'View relative' and it caused my toon to run everywhere and nowhere when I was in 3rd person view.

Hope this helps others with simular problems.

Kindly

Val
 
Top Bottom