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

Custom Navmesh Handling #122

Open
suineg opened this issue Jun 13, 2021 · 0 comments
Open

Custom Navmesh Handling #122

suineg opened this issue Jun 13, 2021 · 0 comments

Comments

@suineg
Copy link

suineg commented Jun 13, 2021

Often people have created meshes that have personal improvements or specific pulling paths. These might not be good enough for "official" and as such will get overwritten if they do an update. An update is not necessary all that often but it can be annoying.

Proposal - Folder or file name addendum that allows a personal navmesh to be loaded before the regular navmesh is. This could look like either of these options.

C:\Users\suineg\AppData\Local\VeryVanilla\Live\Release\MQ2Nav\custom\templeveeshantwo.navmesh
or
C:\Users\suineg\AppData\Local\VeryVanilla\Live\Release\MQ2Nav\templeveeshantwo-1.navmesh

Problem that arises is how to use meshgen on either file to generate or build. This is doable but how do you present that to the UI and make it flow well?

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

No branches or pull requests

1 participant