Prepull Limit Break 3 Generation from Critical Health Healing is doable out of combat

[Nemekh]

Date & Time: 09/07/2019
Frequency: Always
World name: Leviathan
Character name: Nemekh Kinryuu
Retainer name: Naubi
NPC name: N/A
Monster name: N/A
Class/Level: Any current or synced levels in instances
Party or solo: Party
In-game time: N/A
Area and coordinates: Any instances where LB can be generated
Housing: N/A

Steps:
1. Go into a raid instance with a Full Party
2. Have everyone create a naked gear set that they can swap to
3. Have people repeatedly swap between their main gear set and this naked set so that they have lowered hp vs their regular max hp
4. Have one healer repeatedly cast a group heal out of combat
5. Provided the heal resolves while people are at <10% of their max hp, observe as for each player that counts it generates limit break out of combat

This has been a broken problem since at least Stormblood, possibly earlier, however, the interest and testing of Limit Break generation only gained more traction last expansion.

This is a quote from my as of yet unreleased Limit Break document:

The least known method of generating Limit Break and one that comes across as a large design oversight, it was discovered that a party could generate LB without being engaged in an active, hate list established encounter.

Party members pre-pull can perform critical health recovery generation by:

• Having a gear set with minimal or no vitality (e.g. naked with a weathered weapon)
• Swapping to this set after their passive hp and mp recovery tick has happened to reach low health
• Immediately swapping to their regular raiding gear set to have health that is 10% or less of their max hp
• Receive a heal before the next passive hp/mp recovery tick and receive 600 LB units per successful heal check

The LB gen values are correct for 4.5 and have not been verified for 5.0. However, the method still exists and apparently has been possible since ARR.

Please see this clip from Stormblood Sigmascape era.

Please see this clip from current content in Titania Extreme.

In the past the max LB from this method was LB2. Now it can surpass LB2 and reach LB3. While engaging would have the gauge deplete itself, a ranged or caster can precast their LB before the party starts the encounter.

The existence of this is a problem. SE, for the love of Bahamut, please make it so that this cannot be done out of combat.

Connection Specs
- Type of internet connection/provider: BT Internet
- Modem maker/model number: BT Homehub 4

■ PC Specs

-=-=-=-=-=-=- FFXIV Information -=-=-=-=-=-=-

MyDocument C:\Users\Nemekh\Documents
ProxyEnable 0
ProxyServer unspecified
ProxyOverride unspecified


-=-=-=-=-=-=- System Information -=-=-=-=-=-=-

SYSTEM_OS Windows 10 Home 64-bit (6.2, Build 9200) (17763.rs5_release.180914-1434)
SYSTEM_CPU AMD Ryzen 7 2700X Eight-Core Processor (16 CPUs), ~3.7GHz
SYSTEM_CORE_NUM SYSTEM_CORE_LOGIC 16 SYSTEM_CORE_PHYSICS 8
SYSTEM_BIOS BIOS Date: 08/16/18 17:02:59 Ver: 05.0000D
SYSTEM_LANGUAGE English (Regional Setting: English)
SYSTEM_MEMORY 32693.367MB
SYSTEM_VIRTUAL_MEMORY 134217727.875MB
SYSTEM_PAGE_FILE 69557.367MB
SYSTEM_STORAGE C:\ SYSTEM_HARDDISK_DRIVE SYSTEM_TOTALDISC_SPACE 447.139GB SYSTEM_FREEDISC_SPACE 313.336GB
SYSTEM_STORAGE D:\ SYSTEM_HARDDISK_DRIVE SYSTEM_TOTALDISC_SPACE 1863.000GB SYSTEM_FREEDISC_SPACE 1760.483GB
SYSTEM_STORAGE E:\ SYSTEM_HARDDISK_DRIVE SYSTEM_TOTALDISC_SPACE 465.663GB SYSTEM_FREEDISC_SPACE 61.046GB
SYSTEM_DIRECTX_VERSION DirectX 12
SYSTEM_GRAPHICS NVIDIA GeForce GTX 1070 Ti
SYSTEM_GRAPHICS_DEVICE \\.\DISPLAY1
SYSTEM_GRAPHICS_CHIP GeForce GTX 1070 Ti
SYSTEM_GRAPHICS_MAKER NVIDIA
SYSTEM_GRAPHICS_VRAM 8080.000 MB
SYSTEM_GRAPHICS_SHARED_VRAM 16346.684 MB
SYSTEM_GRAPHICS_DAC Integrated RAMDAC
SYSTEM_GRAPHICS_DISPLAY_MODE 1920 x 1080 (32 bit) (60Hz)
SYSTEM_GRAPHICS_DRIVER C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_21a764822be8dff8\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_21a764822be8dff8\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_21a764822be8dff8\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_21a764822be8dff8\nvldumdx.dll
SYSTEM_GRAPHICS_DRIVER_VERSION 25.21.0014.1891
SYSTEM_GRAPHICS_DRIVER_DATE 2/6/2019 01:00:00
SYSTEM_GRAPHICS_DRIVER_LANGUAGE English
3.0
SYSTEM_GRAPHICS_PIXEL_SHADER 3.0
SYSTEM_GRAPHICS_VERTEX_TEXTURE SYSTEM_SUPPORT
SYSTEM_GRAPHICS NVIDIA GeForce GTX 1070 Ti
SYSTEM_GRAPHICS_DEVICE \\.\DISPLAY2
SYSTEM_GRAPHICS_CHIP GeForce GTX 1070 Ti
SYSTEM_GRAPHICS_MAKER NVIDIA
SYSTEM_GRAPHICS_VRAM 8080.000 MB
SYSTEM_GRAPHICS_SHARED_VRAM 16346.684 MB
SYSTEM_GRAPHICS_DAC Integrated RAMDAC
SYSTEM_GRAPHICS_DISPLAY_MODE 1680 x 1050 (32 bit) (59Hz)
SYSTEM_GRAPHICS_DRIVER C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_21a764822be8dff8\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_21a764822be8dff8\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_21a764822be8dff8\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_21a764822be8dff8\nvldumdx.dll
SYSTEM_GRAPHICS_DRIVER_VERSION 25.21.0014.1891
SYSTEM_GRAPHICS_DRIVER_DATE 2/6/2019 01:00:00
SYSTEM_GRAPHICS_DRIVER_LANGUAGE English
3.0
SYSTEM_GRAPHICS_PIXEL_SHADER 3.0
SYSTEM_GRAPHICS_VERTEX_TEXTURE SYSTEM_SUPPORT
SYSTEM_SOUND Speakers (3- USB Audio Device)
SYSTEM_SOUND_DEVICE_ID {5F27C9F8-7173-4DB2-B817-C2A28766D6B2}
SYSTEM_SOUND_DEVICE_NAME USBAUDIO.sys
SYSTEM_SOUND_DRIVER_VERSION 6.02.17763.0001
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 9/14/2018 00:00:00
SYSTEM_SOUND Speakers (Yeti Nano)
SYSTEM_SOUND_DEVICE_ID {2CD5B6A0-2C8C-4A1E-AB4D-443BB5D6FA6E}
SYSTEM_SOUND_DEVICE_NAME USBAUDIO.sys
SYSTEM_SOUND_DRIVER_VERSION 6.02.17763.0001
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 9/14/2018 00:00:00
SYSTEM_SOUND Digital Audio (S/PDIF) (High Definition Audio Device)
SYSTEM_SOUND_DEVICE_ID {391EB64B-668F-43BD-A2A1-4AED07FE775C}
SYSTEM_SOUND_DEVICE_NAME HdAudio.sys
SYSTEM_SOUND_DRIVER_VERSION 6.02.17763.0001
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 9/14/2018 00:00:00
SYSTEM_SOUND PL2473HD (NVIDIA High Definition Audio)
SYSTEM_SOUND_DEVICE_ID {7140DEEF-A17C-483A-B054-BC12ECCD3D33}
SYSTEM_SOUND_DEVICE_NAME nvhda64v.sys
SYSTEM_SOUND_DRIVER_VERSION 1.03.0038.0013
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 1/15/2019 00:00:00
SYSTEM_SOUND LG TV (NVIDIA High Definition Audio)
SYSTEM_SOUND_DEVICE_ID {A7DF143C-523D-45DA-BF8F-088E3C13F097}
SYSTEM_SOUND_DEVICE_NAME nvhda64v.sys
SYSTEM_SOUND_DRIVER_VERSION 1.03.0038.0013
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 1/15/2019 00:00:00
SYSTEM_INPUT {6F1D2B60-D5A0-11CF-BFC7444553540000}
SYSTEM_INPUT_NAME Mouse
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 3 SYSTEM_GAMEPAD_BUTTON 8 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {6F1D2B61-D5A0-11CF-BFC7444553540000}
SYSTEM_INPUT_NAME Keyboard
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 128 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {585EEA50-33EA-11E9-8001444553540000}
SYSTEM_INPUT_NAME Razer BlackWidow
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {585FADA0-33EA-11E9-8003444553540000}
SYSTEM_INPUT_NAME Razer BlackWidow
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {5308A0A0-76C5-11E9-8001444553540000}
SYSTEM_INPUT_NAME Yeti Nano
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 3 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {5308EEC0-76C5-11E9-8002444553540000}
SYSTEM_INPUT_NAME Yeti Nano
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {586049E0-33EA-11E9-8008444553540000}
SYSTEM_INPUT_NAME Razer BlackWidow
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 573 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {586070F0-33EA-11E9-800A444553540000}
SYSTEM_INPUT_NAME Razer BlackWidow
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 3 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {585FFBC0-33EA-11E9-8006444553540000}
SYSTEM_INPUT_NAME USB Audio Device
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 1 SYSTEM_GAMEPAD_BUTTON 5 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {585F3870-33EA-11E9-8002444553540000}
SYSTEM_INPUT_NAME USB Receiver
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 767 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {585FD4B0-33EA-11E9-8004444553540000}
SYSTEM_INPUT_NAME USB Receiver
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 3 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {585FD4B0-33EA-11E9-8005444553540000}
SYSTEM_INPUT_NAME USB Receiver
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {586022D0-33EA-11E9-8007444553540000}
SYSTEM_INPUT_NAME USB Receiver
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {586070F0-33EA-11E9-8009444553540000}
SYSTEM_INPUT_NAME USB Receiver
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0

[Nemekh]

After talking it over with friends and colleagues, we realise the problem isn't only limited to out of combat critical health recovery. It's non passive tick limit break generation period.

I came up with a test case to see if you could generate Limit Break in a party without being on a hate list or having anything aggroed. Doma Castle, the one airship that shoots a ground aoe marker. Do the above trick, but instead test Surviving Lethal Limit Break generation with a shield while at low hp.

Here is the result. The party gains Limit Break from the surviving lethal event. Here is another clip of the same LB gen while not in combat.

This extends to more than just the original post's problem. All other non-encounter-specific Limit Break Generation events can result in LB units gained. The passive tick is what checks for being engaged in combat.

[Sevigoth]

This is the in-game definition. "As battle progresses".


And after i've send the same topic on french forum there is the answer of the moderator

Bonjour Sevigoth,

Merci de nous avoir fait remonter ce problème.

Cet élément étant déjà connu de notre équipe de développeurs et considéré comme fonctionnant comme prévu, je vais donc déplacer ce sujet dans la section appropriée du Forum.

Je vous souhaite une agréable journée.

Cordialement,

- GM Thyiaeh.

Translation : work as planned

[Hasrat]

First question to ask: Is there anything that states the Limit Break gauge should not be filling at all out of combat?

[Nemekh]

The emphasis of "as battle progresses" is incredibly important. These "acts of heroism" typically will happen only in combat. You have to go out of your way to force it before engaging.

Now I will be frank, there have been members of the GM team that have shelved detailed posts as having "insufficient information" then later the same bugs being accepted and fixed. I cannot believe the full extent of this is "working as intended" given the numerous oversights.

Yoshida has already spoken out about Limit Break and looking into unintentional abuses of the system in the context of time attacks. He stated that he had not fully grasped the situation at the time and would have to check footage of said speedruns (like the linked examples) to see what was going on and if they could make any changes. It is precisely what had lead to the 5.0 Limit Break system versioning and reducing the resultant gain from "cheesed" sources vs how it was in 4.x and older content.

There is another oversight that has come to light. Thanks once again to the European group that has been testing this in Titania ex, there is another big difference in the 5.0 system that does not exist in 4.0 and prior.

Previous to 5.0, if you pulled a full party boss with any amount of Limit Break, the gauge would reset and the bar would visibly deplete with the 3rd LB bar segment being added. This has been a strict LB rule for as long as we can remember. This is why in Praetorium people will precast LB2 on Nero or else all that LB is lost. Similarly when a player disconnects and the party is no longer a Full Party, if LB is not used quickly enough it will all be lost.

Look here and see how on engaging Titania the bar does not empty. (Clip courtesy of Kirrana's Tivoli/Citrona Ceres)

This seems to be linked to the fact that your max potential bar before engaging is LB3 and not LB2 in raids. This was also tested in Susano. In fights where you only begin with 2 LB bars and gain the 3rd the behaviour is as expected.

Is this truly "working as intended"?

[Nemekh]

I appreciate when people put my crazy thoughts and ideas into practice to show the extent of this problem. Video and raid memes by Kirrana's Tivoli/Citrona Ceres.

Limit Break is broken.

[Nemekh]

The French post that was made has received two GM replies. You can see the thread here. It has since been accepted as a problem

[Qeepel]

Greetings Nemekh,

Thank you for your bug report and for bringing this matter to our attention! We apologize for the confusion any previous responses from a moderator may have caused.

At this time, we are unable to determine if this matter is working as intended or not. However I'll go ahead and submit your report to our development team. Any changes, news or updates regarding this matter will either be made directly to this post, or on the Lodestone site at http://lodestone.finalfantasyxiv.com/pl/index.html and official FFXIV forums.

Again we apologize for the inconvenience but greatly appreciate your patience and understanding. Thank you again!

SQUARE ENIX MODERATOR