-
Notifications
You must be signed in to change notification settings - Fork 5
[REQUEST] Import HarvestMap files #3
Comments
I don't play ESO anymore, but if you link that script I can have a look and try to write something up you can test. |
I looked at the addon, there's a bash script in there DownloadNewData.command it looks like it's for Mac OS, but if you set the path (basedir) to your ESO directory it should work on Linux, it doesn't seem to do anything that wouldn't work on Linux. If it errors out, let me know and we'll try to get it working. |
I tested the HarvestMap mac command on Linux, but it seems that whatever arcane coding wizardry was intended for HarvestMap's data collection doesn't work with the mac script any more. I did however discover that it is possible to set up the powershell script to run through ell.sh by simply calling for pwsh to run the powershell script. In my case I just dropped the DownloadNewData.ps1 file into ESO Linux Launcher's directory and renamed it hm.ps1, and added a new function to ell.sh to check for HarvestMap updates in between TTC and Addon updates, with a proper toggle as well. Example here:
DownloadNewData.ps1 is possibly not legally allowed to be added directly to the launcher as hm.ps1, so figuring out how the command works may be necessary to making it able to be bundled with this git project. Alternatively, though, simply asking the user to copy DownloadNewData.ps1 to the directory as hm.ps1 would work too. The only change really required in DownloadNewData.ps1 is to modify the following line to point to your compatdata directory instead, like so:
Also, if running as a shortcut, make absolutely sure to delete the following line from DownloadNewData.ps1 if you want to actually run the game:
|
I'm not very familiar with shell scripting, but it looks like it should be feasible to add in scripting to (optionally) merge HarvestMap data - their powershell script is runnable if you install powershell for linux, but I suspect everything it does is reproducible in a bash script, negating the need to rely on a powershell script.
The text was updated successfully, but these errors were encountered: