Skip to content

Conversation

@aufau
Copy link
Member

@aufau aufau commented May 22, 2024

These are:

  • maps loaded from pk3 in basejka or fs_assetspathjka directories
  • maps loaded from pk3 with ojka_ prefix
  • maps loaded from pk3 with "compatible jka" string in mv.info file

There is a function in place now (MV_GetCurrentMapVersion()) to change engine behaviour depending if map is considered jk2 map or jka - even if the rules how we detect this change.

Some ideas:

  • Blacklisting some file extensions from jka assets on fs_ level
  • Giving priority to jka assets when map is jka on fs_ level
  • Special renderer behaviour to make some missing jka features work
  • Special mvapi and module behaviour to make some missing jka features work

…JKA map

These are:
* maps loaded from pk3 in basejka or fs_assetspathjka directories
* maps loaded from pk3 with ojka_ prefix
* maps loaded from pk3 with "compatible jka" string in mv.info file
@entdark
Copy link

entdark commented May 22, 2024

wow you really like overcomplicating

@UncannyFish
Copy link
Contributor

This pull request breaks support for custom .pk3 files.

Before this pull request:
shot0000

After this pull request:
shot0001

@aufau
Copy link
Member Author

aufau commented Jun 3, 2024

Thanks for testing, I'll check it out (if we are even going the merge this pr in the end)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants