Windower 4 - Discussion and Support

[Sithel]

Would it be possible to detect if /lockstyle is on or off? Would be handy in Gearswap.

This isn't mine but was posted on the windower forums, so credit goes to tarutarupanic. I currently use it and it's been working fine. It's fairly simple, if inside your spellcast or gearswap job profiles you create a Vanity set and zone, it will change to that set and turn lockstyle on. If you don't create a vanity set when you zone it will still turn lockstyle on but will just lock the set you had on when zoning. It's a basic set of wait commands you'll see in the file so you can have it change to whatever set you want locked if this is what your after when zoning. I use this daily with rng to stop from blinking and sport my good looking gear!

http://www.privatepaste.com/e8c1bfc2dd

[Raelia]

That's a neat example for how to detect a zone change. I already have a swag set swap after any action while idle and you only need a one second delay before /lockstyle and then your pdt/regen/refresh/movement/etc gear, all of which which gearswap can better handle internally. It still results in me being in some unsafe equipment if I fail to autotarget with a bunch of mobs on me for example, so being able to detect if /lockstyle is already active is more of a safety thing.

It would be better if his code issued a Gearswap command though, like '//gs c swag', instead of directly equipping a (mildly) hardcoded set, because it doesn't put you in actual idle gear afterwards.

[JSHidaka]

That's a neat example for how to detect a zone change. I already have a swag set swap after any action while idle and you only need a one second delay before /lockstyle and then your pdt/regen/refresh/movement/etc gear, all of which which gearswap can better handle internally. It still results in me being in some unsafe equipment if I fail to autotarget with a bunch of mobs on me for example, so being able to detect if /lockstyle is already active is more of a safety thing.

It would be better if his code issued a Gearswap command though, like '//gs c swag', instead of directly equipping a (mildly) hardcoded set, because it doesn't put you in actual idle gear afterwards.

just add another line to equip it...
windower.send_command('@wait 12; input //gs equip sets.Idle')

[Raelia]

So let's continue to hardcode direct equip commands with excessive waits in an addon instead of letting gearswap handle it. Right.

Pay attention please, you did everything I said was wrong with that addon. I wasn't asking for a /lockstyle swag method, I was asking if windower could expose lockstyle status to make it faster and safer.

[Byrthnoth]

The problem is that lockstyle is mostly a server behavior. I'd be very surprised to learn that the client monitors lockstyle status at all, which means windowerplugin would have to catch outgoing lockstyle packets (and reset lockstyle to false on zone). Here is an include file that makes a "user_lockstyle" function and passes true (lockstyle is on) or false (lockstyle is off) when lockstyle changes, if you are interested:

_lockstyle = {lockstyle=false}

windower.register_event('zone change',function(...)
    if _lockstyle.lockstyle then
        if user_lockstyle and type(user_lockstyle) == 'function' then user_lockstyle(false) end
        _lockstyle.lockstyle=false
    end
end)

windower.register_event('outgoing chunk',function(id,org,mod,is_injected,is_blocked)
    if id == 0x111 then
        local new_lockstyle = (mod:byte(5)==1)
        if new_lockstyle ~= _lockstyle.lockstyle then
            _lockstyle.lockstyle = new_lockstyle
            if user_lockstyle and type(user_lockstyle) == 'function' then user_lockstyle(new_lockstyle) end
        end
    end
end)

function lockstyle(bool)
    if _lockstyle.lockstyle ~= bool then
        local pants = 0
        if bool then pants = 1
        elseif bool == false then pants = 0
        elseif _lockstyle.lockstyle = false then pants = 1 end
        windower.packets.inject_outgoing(0x111,string.char(0x111,4,0,0,pants,0,0,0))
    end
end

I also included a function named lockstyle() that takes a boolean argument and either unlocks (false) or locks (true) your lockstyle. If you don't provide the boolean, it toggles it based on the current state.


I didn't bother testing it, but it probably works. Use print statements to debug it if you care.

[pancakesandsex]

I hooked up that debugger and was unable to repeat the crashes, don't know what was going on. Oh well.

[Arcon]

Yeah, it seems a debugger has the latent effect of preventing the crashes it's supposed to debug. Some people attach it just to play better <_<

[pancakesandsex]

Yeah, it seems a debugger has the latent effect of preventing the crashes it's supposed to debug. Some people attach it just to play better <_<

Some other stuff updated when I loaded windower prior to testing so it's also possible those moving parts corrected the crash. I'll find out eventually

[Trumpy]

I used to use a plugin/addon that either doesnt do it anymore or i dont load it anymore that would replace {tnl} with my "experience to next level" like 495/9847 in chat. there were other things it did similiar but i happened upon that part of it and started using it. But now {tnl} isnt workin so i am tryin to find out if i stopped using it or the plugin/addon stopped using it, anyone have any ideas?

Also I used to have reminders usin autoexec when in dynamis when procs were changin cause id find myself fightin the same mobs when procs changed cause i didnt notice the game time (Also before weathermon i had the same thing but for weather). But now those arent workin it seems. Recently i made some codes when i was fishin up a sawfish so that i headed to catch a ferry in time and i got some of them to work but not others.

This used to work:
<register silent="true" event="time_0.00">wait 1;input /echo ========== 0:00 Dynamis Proc Change ********** 0:00 ********** ========== </register>

This does work:
<register silent="true" event="time_12.10">input /echo ========== 12:10 Manaclipper Reef Run Arriving ********** 12:10 ********** ========== </register>

When i copy paste the one that works and change the time and the message it suddenly doesn't work. Im nto sure if i am doin the below 10 oclock numbers right, I am not sure if its 9.00 or 09.00 Ive tried both ways and nothing, but also usin stuff over 10 didnt work at that point either. for my manaclipper code i had a few lines there and everything after 10:00 worked. It is just frustrating me i cant get it to work so i started thinkin maybe something time wise is broke in windower possibly? If it isnt a bug in windower can someone assist me with code that can do this? (also i tried using dynamis helper long ago and it never showed the right procs for mobs for me for some reason. Now when i try it it seems to put a timer up for the duration of a proc but i havent seen any display to tell me what procs to use, or anything else)

[Mafai]

I used to use a plugin/addon that either doesnt do it anymore or i dont load it anymore that would replace {tnl} with my "experience to next level" like 495/9847 in chat. there were other things it did similiar but i happened upon that part of it and started using it. But now {tnl} isnt workin so i am tryin to find out if i stopped using it or the plugin/addon stopped using it, anyone have any ideas?

Also I used to have reminders usin autoexec when in dynamis when procs were changin cause id find myself fightin the same mobs when procs changed cause i didnt notice the game time (Also before weathermon i had the same thing but for weather). But now those arent workin it seems. Recently i made some codes when i was fishin up a sawfish so that i headed to catch a ferry in time and i got some of them to work but not others.

This used to work:
<register silent="true" event="time_0.00">wait 1;input /echo ========== 0:00 Dynamis Proc Change ********** 0:00 ********** ========== </register>

This does work:
<register silent="true" event="time_12.10">input /echo ========== 12:10 Manaclipper Reef Run Arriving ********** 12:10 ********** ========== </register>

When i copy paste the one that works and change the time and the message it suddenly doesn't work. Im nto sure if i am doin the below 10 oclock numbers right, I am not sure if its 9.00 or 09.00 Ive tried both ways and nothing, but also usin stuff over 10 didnt work at that point either. for my manaclipper code i had a few lines there and everything after 10:00 worked. It is just frustrating me i cant get it to work so i started thinkin maybe something time wise is broke in windower possibly? If it isnt a bug in windower can someone assist me with code that can do this? (also i tried using dynamis helper long ago and it never showed the right procs for mobs for me for some reason. Now when i try it it seems to put a timer up for the duration of a proc but i havent seen any display to tell me what procs to use, or anything else)

Might have been attainment. Did you replace it with pointwatch? I think attainment supported these commands:

{current_exp}
{exp_next_lvl}
{tnl}
{total_exp}
{last_exp}
{exp_k_per_hour}
{current_limits}
{max_limits}
{tnm})
{merits}
{total_cruor}
{last_cruor}
{cruor_k_per_hour}
{pearl}
{gold}
{silver}
{ebon}
{azure}
{ruby}
{amber}
{visitant}
{alabastor_granules}
{amber_granules}
{azure_granules}
{crimson_granules}
{obsidian_granules}
{hourglass}

[Trumpy]

yea thats what i thought too, that it was attainment. But i dont recall it working before pointwatch came out and I always had attainment on before PW. I will try it out again though and see if it works.

[Trumpy]

Well it isnt Attainment that does the {tnl}, or at least it doesnt anymore whether its broke or it was removed i dunno. on another note no one knows how to use autoexec to give me a echo at a specific gametime (specially a time before 10:00 that doesnt seem to work for me at all)? If i copy paste the code that works it seems to have no problems until i change anything about it. I dont really get why. Is there a bug with time related things in windower maybe?

[Arcon]

There is nothing that replaces {tnl} in the chat log, I'm not aware of anything that ever did that.

Time events work fine as far as we know, which means if you suspect a bug try to narrow it down and report it.

[Trumpy]

I cant even remember how i stumbled upon it but when i found it worked in chat i had put a tnl report in my engaging macro when i played as a monster. I still have the macros but doesnt work anymore. so prolly jsut a fluke way back a couple months back or so.

OK well should this work or do i have an error here for autoexec:
<register silent="true" event="time_0.00">input /echo ========== 0:00 Dynamis Proc Change ********** 0:00 ********** ========== </register>

This is copied straight from my autoexec file that used to work but doesnt seem to do anything now. So i was wonderin if someone could lemme know if i have an error here (am i doing it right)? Thanks for any help you guys.

[Arcon]

OK well should this work or do i have an error here for autoexec:
<register silent="true" event="time_0.00">input /echo ========== 0:00 Dynamis Proc Change ********** 0:00 ********** ========== </register>

This is copied straight from my autoexec file that used to work but doesnt seem to do anything now. So i was wonderin if someone could lemme know if i have an error here (am i doing it right)? Thanks for any help you guys.

Try 00.00, I think that should work.

[Trumpy]

Ok I think i found the problem...
This works:
<register silent="true" event="time_0.50">input /echo ==== 0:50 ==== ;chatmon play c:\chatmonwavs\tada.wav</register>
This doesnt work:
<register silent="true" event="time_0.00">input /echo ==== 0:00 ==== ;chatmon play c:\chatmonwavs\tada.wav</register>

having the last two numbers as 00 seems to make it break.

[Arcon]

You need 0.0, not 0.00. Leading zeroes are omitted.

[Trumpy]

Alright that works... thank you arcon. so would 1:50 also get coded as 1.5 or would that be 1:05 (just checking) I had a feeling my problems were some thing stupid i was doin thanks.

[Arcon]

1:50 is still correct, only leading zeroes are omitted. Not sure why that is the case, but it appears that's what's causing it.

[Raelia]

Addon version of Distance doesn't work for Subtarget. Might go back to the plugin, lol.