aspoonplaysgames / advocate

A tool to make skin and nose art modding more accessible and less time consuming.

Software Engineer Intern at Criterion.

University student, on placement year, studying Computing.

Currently working on:

• R2Northstar
• Advocate

advocate's Issues

Mod that I made downloads but doesnt work ingame

I made a mod, and it downloaded it fine. I then went to test it ingame, and it didnt show up on my titan. How do i fix this?

Some errors are being caught unnecessarily by try catch

Since the logging rework, some classes should probably log errors and return, instead of throwing exceptions.

Advocate still fails to find some skin files

Generally this is because of weird folder structure, but an attempt should be made to support these nonetheless

Noseart is transparent

All my mods are partially transparent in both the preview window and on titans ingame. Is there any way I can fix this?

Version number does not default to 1.0.0 in the converter

It does in the nose art creator, just a QOL thing really.

After saying cleaning, stays still then just fails.

It says no reason behind the fail, it just fails. Tho it keeps the "cleaning" tag thing next to the main button after the fail, nothing is spitting out of the tool ether

Support every texture that the skin tool supports

Currently, this tool only supports weapon skins, this should be changed to support the full range of skins that the skin tool supports

[FEAT] Ability to install skins after converting them

Some known errors do not get handled as such

Example being "File is not a valid DDS file" which is caused when the file's magic is incorrect for a DDS file. (There is a skin somewhere on thunderstore which is just renamed png files instead of actual dds files)

Incorrect logging shown on UI

Currently logging that is specific to one tool still gets received and handled by all tools. This results in tools sharing statuses and errors, when they shouldn't.

Note: could be fixed by adding a property to LogMessageEventArgs containing a "context" or something and only listening to log messages with the correct context in UI

Debug logging

Logging is currently very basic, more information should be logged to the console and to files for debugging

Logging

Currently, this tool doesn't do logging of any kind, which makes debugging issues harder

Incorrect colour in converted skins

The skin tool seems to not care about if a texture is using SRGB, however RePak does. This results in converted textures having incorrect colour

Intended colour:

Resulting colour: