ApacheTech Posted April 11, 2020 Report Share Posted April 11, 2020 I get the following errors: Quote > add-dll OptiZoom == Loading VintageStory == Searching for VS in "D:\Games\Vintage Story\" ... VintageStory v1.12.11 detected! Outdated VintageStory version detected. New version v1.12.14 available! Continuing anyway ... == Running Task == 'OptiZoom' is not a valid modid! > add-dll "OptiZoom" == Loading VintageStory == Searching for VS in "D:\Games\Vintage Story\" ... VintageStory v1.12.11 detected! Outdated VintageStory version detected. New version v1.12.14 available! Continuing anyway ... == Running Task == 'OptiZoom' is not a valid modid! > add-dll 'OptiZoom' == Loading VintageStory == Searching for VS in "D:\Games\Vintage Story\" ... VintageStory v1.12.11 detected! Outdated VintageStory version detected. New version v1.12.14 available! Continuing anyway ... == Running Task == ''OptiZoom'' is not a valid modid! After the first command failed, I asked on Discord, and received the advice that the <modid> needed to be in quotations, so tried single and double quotation marks, and neither worked. There is no information at all, on the wiki, about what a "modid" is, apart from noting that it will be the assembly name. I want OptiZoom to be my assembly name. Link to comment Share on other sites More sharing options...
Vies Posted April 13, 2020 Report Share Posted April 13, 2020 Did you try to make your modid all lowercase? It accepted mine when I did that. I know from Minecraft modding, the modid must be lowercase. I hope this helps! Link to comment Share on other sites More sharing options...
ApacheTech Posted April 13, 2020 Author Report Share Posted April 13, 2020 I did try that, and it worked. I'm not willing to use all lower-case assembly names though, because it breaks .NET coding conventions. The wizard seems to be completely redundant anyway. It just dumps you out into a completely empty project, with no boilerplate at all. Add -> New Project to Solution would have done exactly the same thing, but without the three hours of troubleshooting a badly written third party tool. Link to comment Share on other sites More sharing options...
P3t3rix Posted April 25, 2020 Report Share Posted April 25, 2020 Had the same reaction. I then followed copygirls tutorial for .netcore and created a template https://github.com/p3t3rix/VsModDotnetTemplate The modtools are more targeted towards new programmers that may not have much experience with c#/programming in general. But i agree it's pretty ugly to have lowercase assembly names. Link to comment Share on other sites More sharing options...
Recommended Posts