Announcement on Steam.

Announcement on Steam.

Greetings, dear manager.

The following are issues that have been identified in the Nov. 14th Scheduled Update.

In order to correct the following issues, we intend to deploy a hotfix by today 17:00(KST).
The hotfix does not require a separate client update; however, please note that additional in-game downloads may occur.

▶ EN Only) Fixed an issue where Fell Bullet Yi Sang E.G.O was missing player ticket phrase and word

▶ JP Only) Fixed incorrectly translated words in "Check Passed" and "Post-Uptie Chat 2" voicelines for The Princess of La Manchaland Rodion

▶ JP Only) Fixed an issue where an unintended line break was added to The Princess of La Manchaland Rodion's "The Finale" Skill

▶ KR Only) Fixed an issue where the highlights for Fell Bullet Yi Sang E.G.O's Uptie 4 Corrosion Skill

We apologize for the inconvenience.

Announcement on Steam.

Announcement on Steam.

Announcement on Steam.

Announcement on Steam.

Post on twitter.

Announcement on Steam.

Announcement on Steam.

Announcement on Steam.

Announcement on Steam.

Announcement on Steam.

Greetings, dear Manager.

The following are issues that have been identified in the Oct. 24th Scheduled Update version of the game.

We will deploy a hotfix for the following issues by 21:00 today.
The hotfix will be deployed without having to download a separate client update; restart the game to access the newest version of the game. Please note that additional in-game downloads may occur.

▶ Fixed an issue where Yearning-Mircalla E.G.O of Meursault's "Lose X Count" was missing the description for which Keyword it was supposed to lose Count for

• Before: [On Hit after Clash Win] Activate Bleed on the target once (target loses 1 Count)
• After : [On Hit after Clash Win] Activate Bleed on the target once (target loses 1 Bleed Count)

▶ Fixed an issue where, in the first phase of the last Encounter in 7-36 caused 'Unknown' to load in the Passives descriptions for summoned units

▶ Addressed typos and missing Keyword highlights in the last Encounter of 7-36

▶ (JP Only) Fixed an issue where a certain Passive in the last Encounter of 7-36 was incorrectly translated

▶ (EN Only) Improved clarity for a notice description in the Support Unit UI and fixed a typo in story

We sincerely apologize for the inconvenience.

Announcement on Steam.

Hello,
This is Project Moon.

After identifying the issue where some users were experiencing a progression blocker in all Story Dungeons, we decided to implement a temporary measure via a hotfix.

The hotfix will be deployed without having to download a separate client update; restart the game to access the newest version of the game. Please note that additional in-game downloads may occur.

Cause

• Caused by progressing through the dungeon after deploying a Support Identity, which you do not own, from a Friend

Hotfix Date

• After Oct. 24th (THU), 16:30

Temporary Measure

• We have disabled access to Support Identities in all Story Stages.

Solution (Applied with the next Client Update)

• We corrected the logic that was causing this issue.
• We plan to deploy a new client update with the fix on our next update, and Support Identity functions will be enabled again once that fix deploys.

We sincerely apologize for the inconvenience.

[Oct. 24th Scheduled Update Error Compensation]
Compensation : Lunacy x1000
Recipients : All users whose accounts were created before Oct. 31th 2024, 10:00
Can be claimed once per Account
When : After Oct. 24th 2024, 17:00

Announcement on Steam.

We have identified the cause of the black screen progression blocker issue in all story dungeons that some of our players have been experiencing.

Issue

• Occurs when slotting in a friend Support Unit upon entry to the Story Dungeon Stages for the first time
• Progressing through the Story Dungeon with the said loadout will cause the black screen progression blocker issue

Cause

• In the progress of limiting the deployment of Don Quixote in all Story Dungeons, the logic to implement that interfered with the logic that deploys Friend Support Units, which caused the black screen progression blocker issue.
• Once it occurs, the user's loadout data will be saved in an abnormal state, causing the issue to repeat even upon restarting the game.

In order to play through the dungeon properly, please follow the below procedure.

• Upon first entry to the dungeon: please do not deploy a Friend Support Unit in your loadout.
• In the in-dungeon Checkpoints: please do not deploy a Friend Support Unit in your loadout.

If the issue is already occurring, and if you are already inside the dungeon, please forfeit the dungeon and enter again with a new loadout.

How to forfeit a dungeon

• Select the cogwheel on the top right corner of the Dungeon UI, and select "Forfeit" in the subsequent options menu.
• If there is an issue preventing you from attempting the above fix: attempt to enter a different Story Dungeon, and once the "You're currently exploring (Other Dungeon)'. Forfeit your progress and enter a new dungeon?" popup appears, press "Yes".

We will update you via an additional notice as soon as we resolve this issue.

We sincerely apologize for the inconvenience.

Announcement on Steam.

We have identified an issue where, after the 1.61.0 update, some users are experiencing issues progressing through the game due to getting stuck in a black screen.

This issue is likely linked to the Friend Support Identity function of the game. Please try entering the Canto 7 Dungeon without slotting in a Friend Support Identity for now.

We are currently investigating the issue, and we will inform you via an additional notice as soon as it is addressed.

Post on twitter.

Hello,

If you visited the community's page in the last two weeks, you might have seen that it still mentions the previous season of Limbus Company. Or maybe you've seen the correct season. This is because lemmy's last update (in June) broke some moderation features when the moderator is not on the instance hosting the community.

In this case, I cannot change the sidebar and make sure it stays changed, it reverts to its previous state regularly, and now I can't even get the change to federate as far as I can see.

The code to solve the problem exists but won't be active until lemmy rolls out a new version. In the meantime there's nothing I can do to reliably update the information, so please hang in there, it should hopefully get better at some point.

(This is also why I can't unpin the pinned message. We're stuck with this one until I get back full moderation tools.)

Announcement on Steam.

Announcement on Steam.

[Notice: Issues Identified in the Oct. 17th Scheduled Update]

Greetings, dear manager.

We have identified the following issues in our October 17th Scheduled Update.

1. An issue where the game may get softlocked during the battle in Stage 7-26

7-26 We have identified an issue where the game has a chance to softlock in Stage 7-26.

Please refer to the following for more information.

[Conditions]

• May occur in Clashes against a special enemy that appears only in Stage 7-26.

• There is approxiatemly 20% chance that your character will freeze during a Clash, softlocking the game.

• This issue is localized entirely within this single stage.

[Cause]

We created a specialized clash script only for that combat Encounter Stage.

However, there was a logic error in that script tied to a specific animation, which causes the softlocking issue.

You can lower the chance of triggering this issue by minimizing the number of clashes in the Stage(by targeting only a single enemy Skill Slot with all of your Skills, for example)

If the game softlocks, please select the gear wheel icon on the top right corner of the screen and select 'Give Up' to exit the stage. Then, you should be able to either retry the stage or access other content of the game.

[Solution and our future measures]

We identified the problem logic and corrected the issue.

We plan to add additional logic for exception cases so that no soft locking issue may occur due to similar cutscene logic issues(such as the next animation not loading for a certain amount of time).

However, as our current goal is to focus on the stability of the content for the next part of the chapter, we kindly ask for your understanding that the fix for this issue will be deployed with our next Scheduled Update, Canto 7 (Part 3).

2. Notice: Oct. 17th Scheduled Update Error Hotfix

We will deploy a Hotfix for the following issues by 17:00 today.

Hotfixes can be deployed without a separate client update, and can be applied by restarting the game. However, please note that additional downloads may occur.

▶ Fixed an issue where 'The Barber of La Manchaland Outis' Skill 3's "[On Use] If the target has 5+ Bleed, Coin Power +1" works up to "Coin Power +2"

▶ (EN Only) Fixed an issue where Faust's Lasso E.G.O Corrosion Skill Threadspinning Tier 4 has an issue where "(max 2)" was missing from "Coin Power +1 for ever 7 Rupture on the target (max 2)"

▶ (KR Only) Fixed typos in 'The Barber of La Manchaland Outis' self-introduction lines & voice lines

▶ (JP Only) Fixed an issue where a certain character's Skill Keyword was mislabeled as "Poise" instead of "Rupture"

▶ Updated the BGM for Stage 7-34 with a more recent version of the song

We sincerely apologize for the issues, including the game softlocking issue mentioned above.

[Oct. 17th Scheduled Update Error Compensation]

• Compensation: Lunacy x500
• Recipients: All users whose accounts were created before Oct. 24th 2024, 10:00
• When: After Oct. 17th 2024(THU), 17:00 (KST)
• Can be claimed once per account

This error compensation can be claimed until Oct. 24th (Thu) 2024, 10:00 (KST) via the in-game Mailbox. (Mail available for 7 days)

Announcement on Steam.

Announcement on Steam.

Announcement on Steam.

Announcement on Steam.

Hello everyone,

One of the admin of the instance hosting this community (lemmy.ml) apparently took an interest in this community and deleted several of my posts. I tried contacting them after the first deletion but got no answer.

Given that the first fanart deleted was an entirely SFW picture and got deleted for being "porn", I can't just stick to the most covered characters while this gets sorted out because it's entirely possible it will get seen as porn too. For this reason, I won't post any more fanart until I get more information.

I'll keep posting the official updates.

Thanks for your understanding.

Ezra by @1444tmt@twitter.com