Windower 4 - Discussion and Support

[Scrynth]

Any reason why this settings/timers.xml doesn't work? It will only load the global settings.

Spoiler: show

<?xml version="1.0" ?>
<settings>
<!--
This file controls the settings for the Timers plugin.
Settings in the <global> section apply to all characters

The available settings are:
enableRecast = Enables recast timers (Default: true)
enableBuffs = Enables buff timers (Default: true)
graphicalMode = Enables graphical timers (Default: true)
slimMode = Enables slim graphical timers, must be used with graphicalMode true (Default: false)
flashOnComplete = Flash timers upon completion (Default: true)
showTenths = Show detailed countdown when less than 10 seconds remaining (Default: true)
orderAlphabetically = Order timers alphetically instead of by duration (Default: false)
show1HourName = Show the actual name of the 1-hour on cooldown (Default: true)
highRed, highGreen, highBlue = The RGB values to use for the bar when it is under 50% complete
medRed, medGreen, medBlue = The RGB values to use for the bar when it is between 50% and 75% complete
lowRed, lowGreen, lowBlue = The RGB values to use for the bar when it is above 75% complete
textA, textR, textG, textB = The Alhpa RGB values to use for the text shown
bgA, bgR, bgG, bgB = The Alhpa RGB values to use for the text background when graphicalMode is false
flashR, flashG, flashB = The RGB values to flash when a timer is complete
fontName, fontSize, fontBold = The font name, size and if it is bold
recastX, recastY = The x and y position on screen of RECAST timers (Default: 20 & 350)
buffsX, buffsY = The x and y position on screen of BUFF timers (Default: 200 & 350)
customX, customY = The x and y position on screen of CUSTOM timers (Default: 380 & 350)
barSpacing = The spacing between bars (Default: 0)
recastTimerLimit = The maximum number of recast timers that can be seen at one time, 1 minimum (Default: 10)
buffsTimerLimit = The maximum number of buff timers that can be seen at one time, 1 minimum (Default: 10)
customTimerLimit = The maximum number of custom timers that can be seen at one time, 1 minimum (Default: 10)

Blacklist/Whitelist
Timers will ALWAYS be in blacklist or whitelist mode, even if you dont set anything. The default is blacklist
mode. Blacklist mode means anything listed will NOT be shown. Whitelist mode means ONLY what is set will be
shown.
blacklistMode = Enables blacklist mode (Default: true)
whitelistMode = Enables whitelist mode, overrides blacklist mode setting (Default: false)
recastList = The list of recasts to blacklist/whitelist
buffList = The list of buffs to blacklist/whitelist
-->

<global>
<enableRecast>true</enableRecast>
<enableBuffs>true</enableBuffs>
<graphicalMode>true</graphicalMode>
<slimMode>true</slimMode>
<flashOnCompletion>true</flashOnCompletion>
<showTenths>false</showTenths>
<orderAlphabetically>false</orderAlphabetically>
<show1HourName>true</show1HourName>
<highRed>255</highRed>
<highGreen>0</highGreen>
<highBlue>0</highBlue>
<medRed>255</medRed>
<medGreen>160</medGreen>
<medBlue>0</medBlue>
<lowRed>0</lowRed>
<lowGreen>255</lowGreen>
<lowBlue>0</lowBlue>
<textA>255</textA>
<textR>255</textR>
<textG>255</textG>
<textB>255</textB>
<bgA>128</bgA>
<bgR>0</bgR>
<bgG>0</bgG>
<bgB>0</bgB>
<flashR>255</flashR>
<flashG>255</flashG>
<flashB>0</flashB>
<fontName>Tahoma</fontName>
<fontSize>8</fontSize>
<fontBold>false</fontBold>
<recastX>565</recastX>
<recastY>350</recastY>
<buffsX>565</buffsX>
<buffsY>425</buffsY>
<customX>0</customX>
<customY>450</customY>
<barSpacing>0</barSpacing>
<recastTimerLimit>5</recastTimerLimit>
<buffsTimerLimit>10</buffsTimerLimit>
<customTimerLimit>5</customTimerLimit>
<blacklistMode>true</blacklistMode>
<whitelistMode>false</whitelistMode>
<recastList></recastList>
<buffList></buffList>
</global>
<scrynth>
<enableRecast>true</enableRecast>
<enableBuffs>true</enableBuffs>
<graphicalMode>true</graphicalMode>
<slimMode>true</slimMode>
<flashOnCompletion>true</flashOnCompletion>
<showTenths>false</showTenths>
<orderAlphabetically>false</orderAlphabetically>
<show1HourName>true</show1HourName>
<highRed>255</highRed>
<highGreen>0</highGreen>
<highBlue>0</highBlue>
<medRed>255</medRed>
<medGreen>160</medGreen>
<medBlue>0</medBlue>
<lowRed>0</lowRed>
<lowGreen>255</lowGreen>
<lowBlue>0</lowBlue>
<textA>255</textA>
<textR>255</textR>
<textG>255</textG>
<textB>255</textB>
<bgA>128</bgA>
<bgR>0</bgR>
<bgG>0</bgG>
<bgB>0</bgB>
<flashR>255</flashR>
<flashG>255</flashG>
<flashB>0</flashB>
<fontName>Arial</fontName>
<fontSize>10</fontSize>
<fontBold>false</fontBold>
<recastX>720</recastX>
<recastY>720</recastY>
<buffsX>920</buffsX>
<buffsY>720</buffsY>
<customX>1120</customX>
<customY>720</customY>
<barSpacing>0</barSpacing>
<recastTimerLimit>10</recastTimerLimit>
<buffsTimerLimit>10</buffsTimerLimit>
<customTimerLimit>10</customTimerLimit>
<blacklistMode>true</blacklistMode>
<whitelistMode>false</whitelistMode>
<recastList></recastList>
<buffList></buffList>
</scrynth>
<!--
You may also override specific settings on a per-character basis here.
-->
</settings>

[grevenilvec75]

Does the name have to be capitalized?

[Scrynth]

No it spits out an error and then unloads itself if its capitalized.

[Elpy]

Noticed GearSwap using up way too much memory (300~700mb) after a while recently.

[Arcon]

Notticed GearSwap using up way too much memory (300~700mb) after a while recently.

LuaCore has a known but very hard to pinpoint memory leak. We're currently doing a major recode of LuaCore, so we spent little time debugging it so far, as it might be irrelevant soon. Once that's done we can see if the leak persists and if so try to debug it.

[Nitrous24]

Any reason why this settings/timers.xml doesn't work? It will only load the global settings.

I'm fairly certain this isn't your issue, but, You only need to include the fields that are changed between global and your character. Which, after a very quick (so possibly missed something) skim through, is nothing except the positions.

[Elpy]

world.weather_element in GearSwap is not factoring storms again.

[Byrthnoth]

Does any buffactive work? I have not made any substantial change to gearswap in a week or so, so that indicates a failure in LuaCore.

[Elpy]

Yeah, buffactive does work.
world.weather_element works naturally, but not with storms.

On another note, this may be my failure in lua, but i cant get local variables to work atm, not sure whether it worked before or not. For example, something like this from included files

		elseif spell.english == 'Impact' then
			local tempset = sets['midcast_'..spell.type]
			tempset['body'] = 'Twilight Cloak'
			tempset['head'] = 'empty'
			cast_delay(1.5)
			weathercheck(spell.element,tempset)
		else

will change the actual set, so '//gs equip midcast_BlackMagic' will start equipping Twilight instead of whatever there was.

[Cairthenn]

Why would you expect world.weather_element to check for buffs?

[Elpy]

Storm is a buff. SCH storms i mean.
At least thats how SC behaves and only reason i can think of why it shouldnt behave like that are weather trials, but thats what world.real_weather_element is for. Makes it rather difficult to factor storms on your own otherwise.

[Warusha]

I can't wait for gs. Seeing you guys talk about it makes me jelly!

[Cairthenn]

Oh I see, refresh_ffxi_info does does account for weather for world.weather. Just seemed strange given the name.

It may be luacore then, or there's a possibility the array is being cleared before refresh_ffxi_info is called.

[Arcon]

LuaCore does not give Storm info in the weather value, and I see no reason why it should, as that is not technically weather and even behaves differently. The only sensible thing is to check for it in the buffs. Idk what GS does, but having weather report Storms seems illogical to me.

[Byrthnoth]

It makes sense, because storms emulate single-potency weather. They replace whatever weather is currently present with single potency weather, so there is never a time where you actually care what the real weather is when storms are up. They trigger gear, weather bonuses, etc. It makes sense to treat them as the current weather rather than having everyone that uses weather logic have to make the same exact function to account for them.

The real question is why I still have world.real_weather in, and the answer is that I just left it in for the hell of it in case it becomes useful some day.

[Elpy]

Checked it further, seems like its a case sensitive issue, storm gives lower case 'ice', while real weather and spell.element is 'Ice'.

if spell.element:lower() == world.weather_element:lower() or spell.element == world.day_element then

Works for now.

[Arcon]

It makes sense, because storms emulate single-potency weather. They replace whatever weather is currently present with single potency weather, so there is never a time where you actually care what the real weather is when storms are up. They trigger gear, weather bonuses, etc. It makes sense to treat them as the current weather rather than having everyone that uses weather logic have to make the same exact function to account for them.

The real question is why I still have world.real_weather in, and the answer is that I just left it in for the hell of it in case it becomes useful some day.

I meant for LuaCore, not GS. In GS I can see a benefit for it, although it's still not the right way to do it imo, as storms do not replace weather, they count instead of it in certain situations but not others (trials were mentioned). It would be best to have it as its own, but different variable (weather_effect or something). Otherwise someone who doesn't know about it might be confused by the naming.

[Byrthnoth]

Checked it further, seems like its a case sensitive issue, storm gives lower case 'ice', while real weather and spell.element is 'Ice'.

if spell.element:lower() == world.weather_element:lower() or spell.element == world.day_element then

Works for now.

Okay. I upper cased the first letter of all of them now, but I recommend leaving your fix in. I'll have to decide which way I want it (upper case first or all lower) later. All lower is more consistent with everything else.

[Foldypaws]

So... I have a feature request (for shortcuts? as a standalone thing? whatever.)

I typo'd /haste as /h aste.... and /h is the shortcut for call for help.

A way to just block that command and variations from keyboard input completely would be aces <_<

[Arcon]

There used to be a CFHProtect plugin, honestly, no idea why it's gone oO I was kinda surprised not to see it in the plugin list.

I can make an addon to mimic its functionality, but it will only work on the 4.1 branch (development build).

Edit:
Apparently there is now a /blockhelp command, which is why CFHProtect was deprecated, and which is also why I don't see a need for this addon, so nevermind!