Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Co-Op map 'Overlord Surth-Velsok' not playable #3294

Open
magge-faf opened this issue Jan 12, 2025 · 5 comments
Open

[Bug]: Co-Op map 'Overlord Surth-Velsok' not playable #3294

magge-faf opened this issue Jan 12, 2025 · 5 comments
Assignees
Labels

Comments

@magge-faf
Copy link
Collaborator

Describe the Bug

Starting the co-op map 'Overlord Surth-Velsok' results in the error 'Game could not be created' because the map file does not exist.

This issue has been reported occasionally on the FAF forum and FAF Discord. The issue has persisted for over a year, apparently. I could not find any open issues referencing this map name.

Log file or Error Message

error_log_coop_,map.txt

Reproduce the bug

  1. Start FAF Client
  2. Play tab, Co-Op tab
  3. Select 'Overlord Surth-Velsok'
  4. enter title
  5. host game fails

Expected Behavior

The map should work

Screenshots

grafik

Additional context

No response

Which Operating System are you using?

Windows

@magge-faf magge-faf added the bug label Jan 12, 2025
@Brutus5000
Copy link
Member

This is a deployment error, not a client problem. Generating the files on the server breaks due to the map using subfolder structures that the script does not know about.

@magge-faf
Copy link
Collaborator Author

Can you transfer the issue to the related project, please? If that is not possible, just point me to it, and I will re-create the issue there.

@Brutus5000
Copy link
Member

There is no related project on Github

@magge-faf
Copy link
Collaborator Author

Oh, well. You can decide how to proceed with this issue. You could close it to declutter the 'issues' queue, add it to an internal To-Do list, or handle it in whatever way you think is best. Or let it stay open as a reminder. shrug

@Brutus5000
Copy link
Member

Brutus5000 commented Jan 15, 2025

It can stay here, and I can assign it to me. I thought it was just important to give this info so that nobody tries to find a fix in this repo.

@Brutus5000 Brutus5000 self-assigned this Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants