A new feature for meta.xml (https://github.com/multitheftauto/mtasa-blue/pull/3203) allows us to add patterns to file paths which saves a lot of time when writting a new meta.xml file. Sadly this only works for script and files but not for html files. If you attempt to load html files by using the usual *.extension pattern mta will simply not recognize it.
Steps to reproduce
1.- Add a few png files to your resource
2.- Add <html src="*.png" raw="true"/> to your meta.xml
3.- The resource will throw an error.
4.- The <file src="*.png"/> equivalent will work with no problem.
Version
Client 22650
Server 22650
Additional context
After giving it more thought, I think this qualifies better as a feature request rather than a bug, since the original pull request never stated it would work for html files. Still, html files are important and a QoL feature like file path patterns are always needed and welcome.
Relevant log output
No response
Security Policy
[X] I have read and understood the Security Policy and this issue is not security related.
Describe the bug
A new feature for meta.xml (https://github.com/multitheftauto/mtasa-blue/pull/3203) allows us to add patterns to file paths which saves a lot of time when writting a new meta.xml file. Sadly this only works for script and files but not for html files. If you attempt to load html files by using the usual
*.extensionpattern mta will simply not recognize it.Steps to reproduce
1.- Add a few png files to your resource 2.- Add
<html src="*.png" raw="true"/>to your meta.xml 3.- The resource will throw an error. 4.- The<file src="*.png"/>equivalent will work with no problem.Version
Client 22650 Server 22650
Additional context
After giving it more thought, I think this qualifies better as a feature request rather than a bug, since the original pull request never stated it would work for html files. Still, html files are important and a QoL feature like file path patterns are always needed and welcome.
Relevant log output
No response
Security Policy