kurststsar Posted November 3, 2018 Share Posted November 3, 2018 I was using Vortex normally when suddenly i wasnt able to deply mods anymore.Heres the error message Unexpecteed token in JSON at position 0 when i click more. I have no mods conflicting but i cant install mods anymore. Link to comment Share on other sites More sharing options...
InfernalUnity Posted November 4, 2018 Share Posted November 4, 2018 Might of been a mod you installed. Failing to deploy mods means Vortex was not able to move files to the correct destination. Link to comment Share on other sites More sharing options...
Grestorn Posted November 4, 2018 Share Posted November 4, 2018 What is shown if you click on "More"? Link to comment Share on other sites More sharing options...
rzude Posted January 24, 2019 Share Posted January 24, 2019 (edited) ***SOLUTION*** I struggled with this error for weeks with absolutely ZERO help from the Vortex reporting/feedback process. I came across one guy's post that said he simply DELETED the Vortex.deployment file in his SSE folder. I tried it, and it WORKED. No more FTD mods, unexpected token at JSON position 0 errors and no issues whatsoever with my build. UPDATE: I did receive a message from support stating my vortex.deployment file (that I sent) was corrupted and the instruction to me was to delete it, open Vortex, and re-deploy mods. So, that said, my solution may only work with similar type issues. Edited January 24, 2019 by rzude Link to comment Share on other sites More sharing options...
Pickysaurus Posted January 25, 2019 Share Posted January 25, 2019 While I'm glad you got it working, that solution may cause errors in your setup down the link as deleting it effectively makes Vortex "forget" which files it had deployed to the folder, so purging may not uninstall mods correctly. Link to comment Share on other sites More sharing options...
wartzdal Posted January 31, 2019 Share Posted January 31, 2019 So no fix? I am having the same problem. Link to comment Share on other sites More sharing options...
norkal0105 Posted February 28, 2019 Share Posted February 28, 2019 hopfully deleting it is okey since i have the same problem and i could not find any other solution when i was googelig the problem Link to comment Share on other sites More sharing options...
HadToRegister Posted February 28, 2019 Share Posted February 28, 2019 If people want to try the "delete" solution, my suggestion would be to rename the file to something like "X_Vortex.deployment" and close and open Vortex.That way, if anything messes up, you still have the original file. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now