No luck on Sparks yet ?
Really hope some addons coming to auto turn on Eminence quest wherever the zone you went![]()
No luck on Sparks yet ?
Really hope some addons coming to auto turn on Eminence quest wherever the zone you went![]()
What issue is it exactly that you're having?
It looks like pettp started working at least nominally since I went to bed. It doesnt like ifrit though, his name is "unknown". At pil, so gonna play with it a bit, see if i find anything else not working on it.
Luacore has some kind of memory issue, I randomly lock up for 10-15 seconds on 1 instance (2-4 boxing) and then after it unfreezes I get "Lua error (memory) - not enough memory"
Obviously I'm not running out of memory with 16gb of RAM and a 2gb video card, its also only happened since this most recent push.
Pettp is kinda random. It sometimes remembers avatars names, sometimes doesnt. Sometimes loads on summon, sometimes doesnt. When it DOES load on summon, it works spot on.
Not sure whats going on.
Every action I take (cast a spell, JA, WS, etc.) causes a battlemod runtime error.
Ex.
Lua error (runtime) - .... battlemod.lua:490: attempt to index field 'jobs' (a nil value)
Lua error (runtime) - .... parse_action_packet.lua:510: attempt to index field 'monster_abilities' (a nil value)
Gearswap, send, rolltracker, aecho, autojoin, distance, findall, gearswap, highlight, inforeplacer, itemizer, porter, reive, shortcuts, silence, timestamp, update, zonetimer.
It is 100% related to a plugin/lua because it only happens when stuff is going through log/actions being performed, I can stand in my MH without it happening at all. Within 3-5mins of doing a fight at least 1 of my chars will lockup, usually sooner and usually mulitple chars.
Lockups are for 20-120 seconds. When I unfreeze and if it was long enough to DC me, I go back to lobby screen and log back in then immediately get a runtime error and it shuts that instance down. If the freeze wasn't long enough to DC me then I can continue.
The issue only began today and I haven't installed anything or changed anything.
Howabouts would I get a windower based onevent working? The instructions earlier in the thread didn't work, I could only get commands to respond with /echo. Also not sure if it was fixed, but I think there was a shortcuts issue, anytime i tried to do a ws on a mob without specifying a target, it would say cannot attack this target or something of the sort.
That was fixed this morning. Actually almost all of abilities.lua was FUBAR'd, but not very many people noticed.
Any self command works, but others don't work. The sample given was this:
Code:windower.register_event('incoming text', function(text) if text == 'Something' then windower.send_command('stun') end end)
This suggests your resources aren't up to date. Do you have a Windower/res/ folder and are there lots of .lua files in it? If so, go to Windower/addons/libs/resources.lua, open it in any editor and go to line 74, what does it read?
The example file I gave earlier only works without BattleMod loaded. To make it work with Battlemod, add this line right after function(text):
I think this should be enough, but I'm not fully sureCode:text = text:gsub('[' .. 0x1E:char() .. 0x1F:char() .. '].', '')
battlemod have problem w/ scavenge.. just used it and said "Player uses $[ability /> and finds 21336 adlivun bullets...
Rolltracker was having issues with errors whenever somebody else did a roll.
But what it really sounds like, based on the timing you mention, is something falling out of treasure pool and dicking up itemizer or findall. This is why it can hit more than one character too: each of them received a drop.
Rolltracker was having issues with errors whenever somebody else did a roll.
But what it really sounds like, based on the timing you mention, is something falling out of treasure pool and dicking up itemizer or findall. This is why it can hit more than one character at the same time too: each of them received a drop.
This usually happens on an infinite loop, but most of the addons shouldn't be able to produce one. This could also be a GearSwap user file that has some incorrect event handling.
@Fake:
It would be best if you could try to narrow it down to one addon by disabling things one by one and seeing if it still happens.