Maybe I'm just crazy, but wouldn't
<if status="event">
<return/>
</if>
right at the top of your xml fix this?
Maybe I'm just crazy, but wouldn't
<if status="event">
<return/>
</if>
right at the top of your xml fix this?
When I try to unload scoreboard from inside FFXI via //lua unload scoreboard, the message says that it is "unloading addon scoreboard".
However, while scoreboard stops working until I load it again, the distracting text remains; is there a way to remove that, too?
Kapersky just decided windower 4 was downloading a trojan. I've just made the entire folder an exception but I figure antivirus programs thinking it's a virus is an issue you might want to fix.
It wouldn't be enough to stop it, because that's not the status you have when the problem occurs, namely when you're just finished talking to an NPC, so you'd need to check not your current status but the previous one. That's not possible natively, but you could define a variable to track your status and check it every time your current status changes to idle.
I've watching the discussion on the spellcast swapping to idle issue since it first started happening to me after the <st*> update and figured I would chime in with what I have found.
The main issue seems to come from how spellcast is interpreting the autosets in regards to the event and zoning status. As a simple test, you can define the variable inEvent <var name="inEvent">0</var> to keep track of your previous status. When talking to an NPC, typing "/echo %status" returns the status "Event" as we now know it to be working. In theory, the rule
<if status="event">
<var cmd="set inEvent 1" />
</if>
would change the variable "inEvent" from 0 (false) to 1 (true). Talking to a NPC and then typing "/echo $inEvent" should return 1 but actually returns 0. So even though your status is "event", spellcast did not parse the autoset change, I believe this to also be the case for "idle"->"zoning".
Personally, I do not see the need to differentiate between "idle", "event" and "zoning" aside from semantics. You can't change gears or trigger any abilities while in an event/zoning so why have these special cases? This could be why spellcast doesn't trigger anything on these statuses.
For now, my fix has been to just remove anything that would parse on change to "idle".
Its not event thats causing people problems, its idle.
Basically everyone wants "Idle" to change to their idle gear every time they're "idle", except if changing from "event" to "idle".
try <cmd>sc var set inEvent 1</cmd>
or something similar.
i think your syntax is incorrect
I need some help getting scoreboard to work,
When I first picked up 4.0 scoreboard worked fine, it's windows 8, ran it a couple times... Had a windower 4.0 error that Ihm helped me with personally, but now scoreboard will not load no matter what.
The libs file got wiped out so I had to get them all back manually, and it still doesnt work.
This is the error I'm currently getting:
Lua error...... gram files (x86)\\windower4\\addons\\scoreboard\colors.lua\13 : attempt to index a nil value.
Edit: Nevermind, I just kept fucking with it and fucking with it and fucking with it... it works again... (deleted everything and repasted)
His syntax was correct, the <var> tag allows for sc variables commands to be set with the cmd attribute. While the internals may work differently, the end result should be the same and it should work just fine.
The error messages definitely need to be improved. This means that you were missing ffxidata.json (the file containing some of the color data), but a reload of the libraries should fix that (as it did in your case).
I believe I fixed it for 3.4. Anyone using that give it a shot. I'll port it to 4.0 later tonight if someone confirms it works for 3.4 (I'm at work and cannot test).
THIS IS A 3.4 PLUGIN, IT WILL NOT WORK IN 4.0
http://forums.windower.net/files/file/4-spellcast/
Is Chatmon fully functional in windower4? I'm not getting any tell alerts. Computer's sound working fine, game sound works fine for the most part, except oddly enough FFXI's built in /tell chime doesn't work either.