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.

Sign up for GitHub

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

Jump to bottom

Refactor texdata when moving/renaming VMTs #49

Open
granis48 opened this issue Jul 7, 2024 · 0 comments
Open

Refactor texdata when moving/renaming VMTs #49

granis48 opened this issue Jul 7, 2024 · 0 comments
Labels
Priority: Medium Something that should be tried to be done in this release, but not as important as High priority. Size: Small Something that may take a day at most to do. Type: Enhancement This can improve a system/thing already in place. Where: UI Something that primarily affects the Lumper.UI codebase.

Comments

@granis48
Copy link
Member

granis48 commented Jul 7, 2024

Currently when renaming a vmt file in the pakfile explorer it doesn't refactor the brushes that material is referenced on, meaning any brush that's using that material will now show an error.
@tsa96 tsa96 added Size: Small Something that may take a day at most to do. Type: Enhancement This can improve a system/thing already in place. labels Jul 7, 2024
@tsa96 tsa96 added Priority: Medium Something that should be tried to be done in this release, but not as important as High priority. Where: UI Something that primarily affects the Lumper.UI codebase. labels Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority: Medium Something that should be tried to be done in this release, but not as important as High priority. Size: Small Something that may take a day at most to do. Type: Enhancement This can improve a system/thing already in place. Where: UI Something that primarily affects the Lumper.UI codebase.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsa96 @granis48