Windower 4 - Discussion and Support

**Wheeldog** · 2016-04-06 21:02

Originally Posted by Sechs

The line was " for _,item in ipairs(bag) do", sorry.
I dunno, I never managed to learn what "ipairs" do and how it works so I can't understand what's broken, but something has gotta be different somewhere in GS because that same custom validate.lua used to work flawlessly in december.

THIS is the original post when I developed the changes.
The current validate.lua I have is exactely the same, aside from the fact I also added wardrobe2.

From what I remember I modified the "validate" function to handle multiple types of validation (by default it only handles "sets" and "inv" options).
Then I modified the "validate_inventory" function to accept two parameters in entrance, one is the same as default, the second defines the specific bag to perform the validation on.
I can't remember any other differences I created and it worked perfectly fine.

I noticed a small difference in your own coding though.
New
display_list:map(function(item) msg.add_to_chat(120, windower.to_shift_jis((string.gsub(item, "^%l", string.upper))) ) end)

Old
display_list:map(function(item) msg.add_to_chat(120, (string.gsub(item, "^%l", string.upper)) ) end)

I have an up to date version of your gear not in lua validate.lua I can pass along when I get home tonight. There was a change to that file and as a result it clobbered the old version and removed the changes you made. I reapplied them yesterday and got your functionality to work again.

**Sechs** · 2016-04-07 01:14

I would apreciate a pastebin of it if you have a working version!
I was unaware other people were actually using that modded version I made several months ago.
I admit I used this custom thing rarely, but when I do I found it very useful to "catch" random items you have in your repositories and that you no longer use in any of your jobs' lua.

If other people really use it then maybe it could be considered to post these changes on github and make them official for release version? Byrth what do you think about it, what's your stance?
Validate.lua has to be updated anyway, if I'm not wrong the "validate_sets" function only checks wardrobe and inventory so it has to be updated for wardrobe2 as well.

**Wheeldog** · 2016-04-07 10:46

Originally Posted by Sechs

I would apreciate a pastebin of it if you have a working version!
I was unaware other people were actually using that modded version I made several months ago.
I admit I used this custom thing rarely, but when I do I found it very useful to "catch" random items you have in your repositories and that you no longer use in any of your jobs' lua.

If other people really use it then maybe it could be considered to post these changes on github and make them official for release version? Byrth what do you think about it, what's your stance?
Validate.lua has to be updated anyway, if I'm not wrong the "validate_sets" function only checks wardrobe and inventory so it has to be updated for wardrobe2 as well.

Sorry for the delay, got busy last night and didn't have time to upload it. Here is the new version that should work (it was for me yesterday): http://pastebin.com/wYLREKNV

**RalphTheDwarf** · 2016-04-07 14:13

I notice that whenever I use the Raptor mount I'll get the numbers 85 appearing in the windower console for some reason. Didn't see it when I used the chocobo instead.

**Sechs** · 2016-04-07 15:43

Working for me indeed, gonna check later to see where the error was.
For the time being, thanks a lot Wheeldog!

**trv** · 2016-04-07 19:14

This site will probably help you find the error. https://www.diffchecker.com/

**Wheeldog** · 2016-04-07 22:38

Originally Posted by Sechs

Working for me indeed, gonna check later to see where the error was.
For the time being, thanks a lot Wheeldog!

I'm pretty sure the one line I really changed/fixed was this:

Code:

local extra_items =search_sets_for_items_in_bag(items.repository,filter)

To this:

Code:

local extra_items =search_sets_for_items_in_bag(items[repository],filter)

I had to do this to your previous version too because you want to pass the table value associated to the value of repository not the table value associated with the string "repository" (which doesn't exist).

**Sechs** · 2016-04-08 08:01

It's likely I had to do that change myself but I forgot about it, and when I tried again 2 days ago after the patch I used an older version =/

**Roland_J** · 2016-04-10 15:59

I am having a problem with what I would call a spam of ghost actions being attempted while I play. It doesn't happen until 15+mins of play. The symptom is that eventually I can no longer interact with NPCs unless I spam the enter key. Once I do interact the message "You cannot use that command at this time." begins to spam my chat log very rapidly. I counted 6 lines of that message per second on average. Whatever this action is I have no idea what it is as my character does not try to perform any actions at all before or after interacting with the NPC. Is there a way for me to turn on a debug mode that'll let me see what this action is?

If I /logout and log back in it'll go away until it builds up to critical mass again. After not much longer (15mins or so) it gets to the point where my ffxi starts stuttering and I have to relog if I want to perform well :/

This only started happening post-April5th,2016 >.> All of my job.luas are the same as they were before the update.

http://s18.postimg.org/ngwb2bdwp/ghost.png

**dlsmd** · 2016-04-10 16:05

Originally Posted by Roland_J

I am having a problem with what I would call a spam of ghost actions being attempted while I play. It doesn't happen until 15+mins of play. The symptom is that eventually I can no longer interact with NPCs unless I spam the enter key. Once I do interact the message "You cannot use that command at this time." begins to spam my chat log very rapidly. I counted 6 lines of that message per second on average. Whatever this action is I have no idea what it is as my character does not try to perform any actions at all before or after interacting with the NPC. Is there a way for me to turn on a debug mode that'll let me see what this action is?

If I /logout and log back in it'll go away until it builds up to critical mass again. After not much longer (15mins or so) it gets to the point where my ffxi starts stuttering and I have to relog if I want to perform well :/

This only started happening post-April5th,2016 >.> All of my job.luas are the same as they were before the update.

http://s29.postimg.org/clomo9wjr/img...407_173642.png

are you using gearswap or a custom(none official) addon??

**Roland_J** · 2016-04-10 16:21

I am just using plugins and addons.

Spoiler: show

It only happens on one account and not the other, too. One account is mainly blu, which isn't a motenten job.lua. My other account is whm, geo, blm, and sch, which are all motenten, and it seems to do it no matter what job I'm playing. I was just doing trials as geo and limbus for abc's as sch immediately after closing/relaunching ffxi (dc'd so it wasn't a /logout) and it started doing it once I warped into town after limbus :/

**dlsmd** · 2016-04-10 16:30

the only way to know what addon is causing it is to unload the one by one when it happens and when it stops the last one unloaded is the one that causes it
tho just to be safe wait for 5-10 seconds to unload the next one
if that does not fix it do the same for plugins(except for luacore as it cant be unloaded)

**Roland_J** · 2016-04-10 17:35

Ah, thank you for the unload method of testing. It must be my job.lua then, no doubt. I just did 1h worth of trials on geo again and no error message played on NPCs in town after I warped. I changed to WHM, did an Arch-Omega, warped to town, and error messages ensued.

//lua u gearswap ended the error spam and let me talk to NPCs without spamming enter.

Here is my whm.lua... It did not give these errors until after this recent update. Is there some code that needs to change in gearswap.lua? Or was certain code that I use made outdated and I need to update it? I'm guessing it's somewhere in mote's stuff. My user update function prints an error now, for example! When I press F12 if I'm not in town then Light Arts and Afflatus Solace activate (this is tied into mote's user-update via code in my whm.lua. functioned fine for many many months before the update). Now when I press F12 those JAs do activate but it also prints a 'attempt to index field 'Defense' (a nil value)' on 'local defMode = state.Defense.PhysicalMode' which is line 722.

Spoiler: show

**dlsmd** · 2016-04-10 18:12

first make sure that you do not have some stuck keys on your keyboard or something like that

then there are only 2 functions that could be causing the error(as far as i can tell)
job_update
handle_strategems

to test these just comment them out to see which the error comes from ,to comment out a lot of lines put --[[ in front and ]] at the end, then you need to figure out what part of the code is causing it(this will take time)

**Roland_J** · 2016-04-10 21:26

I might have found my error. What I did find stopped the error I get on F12 key presses.

I had changed mote_include_version to 2 in a half-hearted attempt to upgrade my whm.lua and get that pesky "your job.lua file is out of date" message to go away. Changing it back to version 1 stopped this error. I'll play around some more on whm and see if the error spam starts happening again. Hopefully this is the root of that problem, too. This job.lua was working perfectly with version 1 of mote include; I might not even bother upgrading it if it's gonna be this pesky.

Unfortunately I had decided to try upgrading it right around the same time as the version update and so it was hard for me to tell that this was the culprit at first. Assuming this is the entire culprit. that is. We'll see.

**Trumpy** · 2016-04-11 00:13

I have found sometimes that when I get silenced, I have it set to use echoes (Ive had this kind of code a long time and it never acted like this before, didnt even spam it). but occasionally it will spam it, which I understand (and can accept) but alot of times it will successfully start using the item a couple times in the spam usage of it, but not actually work. its like the echo doesnt get fully used. I did update some stuff in that part of the code and I got it much better, and it doesnt happen as much. but when i first started having that happen it would spam enuf to lag the shit out of me (like tons of memory gets used or something)

I write my own luas tho so no Motes. I am going to be starting from scratch again though soon. much better code with what I have learned to do lately.

**dlsmd** · 2016-04-11 00:19

Originally Posted by Trumpy

I have found sometimes that when I get silenced, I have it set to use echoes (Ive had this kind of code a long time and it never acted like this before, didnt even spam it). but occasionally it will spam it, which I understand (and can accept) but alot of times it will successfully start using the item a couple times in the spam usage of it, but not actually work. its like the echo doesnt get fully used. I did update some stuff in that part of the code and I got it much better, and it doesnt happen as much. but when i first started having that happen it would spam enuf to lag the shit out of me (like tons of memory gets used or something)

I write my own luas tho so no Motes. I am going to be starting from scratch again though soon. much better code with what I have learned to do lately.

i recommend you find a timer to wait a set time till it allows you to use another echoes
then (but in mot sure if it will work) put a check in aftercast to see if the item was interupted if it was re send the command

**RalphTheDwarf** · 2016-04-12 10:11

Findall doesn't seem to be able to find the new ambuscade equipment on slip 23, and still getting the numbers 85 appear on console when using raptor mount.

**Kenshi** · 2016-04-12 14:03

For the error of gearswap printing the 85 as a temporal fix you can edit the statuses.lua in the resources and add this line at the end:

Code:

[85] = {id=85,en="Mount"},

**Trumpy** · 2016-04-12 14:03

Originally Posted by dlsmd

i recommend you find a timer to wait a set time till it allows you to use another echoes
then (but in mot sure if it will work) put a check in aftercast to see if the item was interupted if it was re send the command

Aftercasts were pretty cool until bout a year or so ago. Then code would be spotty on what would work and what wouldnt. If I changed a variable, or made a custom timer in aftercast it seems to usually work but I started have trouble with other things that I used to do all the time. Cause of that I tried to keep most code out of aftercast. I cant even really remember things I had issues with cause I found otherways to deal with what I needed, many of which turned out better. I believe most the problems I had were with the interupted check itself.

I'm not a genius coder or anything. im pretty subpar actually and Im sure if you saw my code you would be workin all day on it lol. I have no ideas about how to set timers within gearswap. I imagine it would be kinda like that code that prevents spell spamming where it prevents spells after trying to cast one, which is cool in theory but i found it blockin casts for up to 5-10 seconds and it was horrible for me. I remember that from a couple years back but I dont remember what it was called. My current solution and its one i been using alot lately is something like this... When i get silenced, i have it send a self command. that command checks if im silenced then uses echo drops. after the drop it is sent again after a certain amoutn of seconds, like 5-7 or however long an echo drop takes and then a couple more seconds maybe, I dont remember exactly. If im not silenced it does nothing. this way if it attempts an echo and is prevented either by throwback/movement or im casting or something, it will try again in the alloted time. and if it works that second check will just do nothing. I think any problem i have now with spammage is because i might have another addon or something also tryin to use echos, so i need to go thru those or something. like aecho i think does use a echo when silenced. I can also add a job check in the code and make it universal for all my jobs. that way its not trying to use echos when im a monk or whatever.

My post was more directed at Roland J who was having spamming issues. ive for the most part fixed those issues for myself.

============================

@Findall the slips.lua in the libs folder prolly needs updating then.

Thread: Windower 4 - Discussion and Support

Thread Tools

Similar Threads

Service and Support

Windows vista and FFXI problem

Windows Vista and Windower

Latest Threads

Up & Coming Threads

Hottest Threads