Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Would you be able to provide a screenshot of that room? It's difficult to imagine the Bobbies can block you from Taking your Joy, since there are 2 Joy Booths in the area. There have been rare reports of Quests failing to update, meaning they can't be completed, so with that in mind, would you be able to provide a Screenshot of the Quest Tracker with Oh Behave! highlighted as well?
Screenshot 1: https://steamuserimages-a.akamaihd.net/ugc/965347254966452738/17084D525B767A0206B0B613590ABA52933E4B24/
Screenshot 2: https://steamuserimages-a.akamaihd.net/ugc/965347254966454153/6962DDF73778F841194F454A0DDA174747CBECC0/
The guy already there doesn't move when I trigger the cinematic part.
You're talking about the guy trying to make it through the Downer Detector Beams? Normally he is supposed to try and cross the beams and get electrocuted in the process. The Bobby will then warn you to take your Joy before proceeding.
If anything but this happens in the cinematic. I'd recommend opening a Ticket with Gearbox Support. They give us detailed reports on the issues submitted to them, and forward this information to us. More patches are planned on all platforms.
You can contact Gearbox Customer Support here:
Gearbox Support[gearboxsoftware.zendesk.com]
I'll be lurking these Discussions on Steam for the better part of the day as well, so feel free to add anything, or ask more questions in this thread as well.
after trolling around in town for a while and found the shelter, i fixed it by a bit of console trickery
Yes, as a last resort the Debug Console is something PC users can fall back on if something game breaking is encountered.
Enable the console in We Happy Few
1. Go to your Config Folder and open the Input.ini: ~\Users\<username>\Documents\my games\We Happy Few\Config\WindowsNoEditor/Input.ini
2. Add the following lines to the Input.ini file and Save:
[/script/glimpsegame.glimpseconsole]
bConsoleEnabled=True
3. Run the game and press the ~ key (Under the Esc Key for most Keyboards)
Example Commands:
WARNING - These can break your game!!! Either create a save file you don't care to lose to mess around with Debug, or only use Debug to get out of serious blocking issues.
LoadQuestDebug - Game will "Freeze" for a short time, while it loads various Quest Debug features (that's how you know it worked, the Console will actually say it is an invalid command).
CompleteObjective - Completes your currently tracked Objective
Ghost - Fly and Clip through walls
Walk - Removes the Ghost effect (Back to normal)
GoToFeature <Location Name> - Note that Locations will have different "Debug Names" than the ones being shown on the map, but the command will work if you have a valid partial name (EG: GoToFeature TrainStation, Sally (Sally's Place).
Give <Item Name> - Item names not always the same as in-game name, however similar to GoToFeature, a partially complete name will work. (EG: Give HealingBalm, Banger, Axe, etc...)