Problem - .cfg files

[Scorpius]

Hi all
Been trying to get .cfg files working but keep getting errors do command - couldn't parse >command< at login or when entering a zone, all works fine with /loadcfg >zone< when I've zoned in

example - poknowledge.cfg
/windowstate largedialogwindow close <- this is just an info box that pops up on first login and the cfg executes on login to close it if camped there ok
/hidecorpse looted <-just so it is set at login as normally camped in pok - this gives the "do command - couldn't parse /hidecorpse looted" error
If I type /loadcfg poknowledge that line also works fine, seems some things work some don't, but again all work fine with /loadcfg >zone<

I have a free mq2 build and all works fine on that, anything works from the cfg on login / zone in, just an older source and limited plugins etc, would love to get this working here -)

Any thoughts?

Thanks

 

[kaen01]

try this:

/timed 20 /hidecorpse looted

 

[Scorpius]

Thanks for the tip Kaen, I tried this but no avail
/pause / delay /timed don't seem to have any effect with cfg files, even tried with /multiline and always give the /do command error with some commands, odd some work and some don't at login/zoning

When executing the cfg from in game with /loadcfg >zone<, all commands process instantly, regardless of any delay method I set in them and all works fine, will just have to remember set zone cfgs when in game -(
Guess RG build just doesn't fully support them, or at least not for me,

Thanks for the reply -)

 

[jande]

Here is mine that works

/if (${MacroQuest.GameState.Equal[INGAME]}) /multiline ; /hidecorpse allbutgroup; /hidecorpse alwaysnpc

pause / delay will not work (its not a macro you execute its actually the same as typing it in in chatwindow)
/timed does.

 

[Scorpius]

Thanks for the info Jande, but still not working for me -( i dont get any errors now, they just dont seem to execute at all, tried yours and "/if (${MacroQuest.GameState.Equal[INGAME]}) /hidecorpse looted" in the cfg file
and corpse remains after looting, with /loadcfg, it works fine and corpse vanishes

Thanks for the help,appreciated, just a no go for me for some reason, although the free build does work fine so can use that if need be -)

 

[jande]

Just puzzled why it then works for me.

 

[Scorpius]

I'm stumped tbh, can only think that as all the commands seem to execute instantly (for me) the gamestate isn't in game when executed, so its not executing the /hidec command so not giving the error
I dont know, really weird, thanks again for the info -)

 

[jande]

Try this in the config file, what is echoed in the mqchat window ?

/echo 1\aw${MacroQuest.GameState}
/timed 30 /echo 2\aw${MacroQuest.GameState}

 

[Scorpius]

1 UNKNOWN
2 UNKNOWN
if run from /loadcfg, and says INGAME for both

I tried adding to the other free compile cfg just for curiosity (all works on that) and get
1 awINGAME
2 awINGAME

Thanks again for all the help, maybe something is bugged in my copy, will try deleting all and doing fresh install as seems it should be working

 

[jande]

Has to be bugged as even on the login screen the ${MacroQuest.GameState} exists, you are not perhaps on an emulated server ?

 

[Scorpius]

yes i am playing on a emu server that allows mq2 and using the VV emu RG build, fully updated -)
once in game i can run cfg's no problem, it's just on login/zoning it errors out on some things not all, very very odd

Anyways thanks for all the help, really appreciated, will update once i have reinstalled it all - time for new year drinks to get going here - 1hr to go

Have a great one

Update
Did a backup of my macros/cfgs etc and fully uninstalled / downloaded & reinstalled
Running default settings, just set a cfg with the 2 lines in
1 UNKNOWN
2 INGAME

Timed seems to be working now, before it seemed to have no effect
"/timed 30 /hidecorpse looted" now triggers on login/zoning and gives the chat window message- yay

Now to edit all of them and see if all the other commands work that was giving the error, i'm sure they will -)
/hidecorpse was just an example of the error -)

Still odd it works fine on the other build without the /timed setting but happy this workaround sorts it -)

Thanks again Kaen/Jande for all the help sorting