Go to Page... |
Compatibility: | Craglorn (1.1) Live (1.0) |
Updated: | 01/18/15 10:28 PM |
Created: | 05/23/14 01:45 PM |
Monthly downloads: | 171 |
Total downloads: | 5,077 |
Favorites: | 10 |
MD5: |
EsoheadMerge_SavedVariables = { ["Default"] = { ["@Sharlikran"] = { ["$AccountWide"] = {
Esohead_SavedVariables = { ["Default"] = { ["@Sharlikran"] = { ["$AccountWide"] = {
Esohead_SavedVariables = { ["Default"] = { ["@Change To Your Account name"] = { ["$AccountWide"] = {
File Name |
Version |
Size |
Uploader |
Date |
0.2.0 |
5kB |
Sharlikran |
06/26/14 12:36 PM |
|
0.1.9 |
5kB |
Sharlikran |
06/08/14 11:20 PM |
|
0.1.8 |
4kB |
Sharlikran |
05/31/14 06:58 PM |
|
0.1.7 |
5kB |
Sharlikran |
05/31/14 10:33 AM |
|
0.1.6 |
4kB |
Sharlikran |
05/31/14 08:34 AM |
|
0.1.5 |
5kB |
Sharlikran |
05/28/14 09:26 AM |
|
0.1.4 |
5kB |
Sharlikran |
05/27/14 11:10 AM |
|
0.1.3 |
5kB |
Sharlikran |
05/25/14 03:19 PM |
|
0.1.2 |
5kB |
Sharlikran |
05/25/14 10:42 AM |
|
0.1.1 |
4kB |
Sharlikran |
05/25/14 09:04 AM |
|
0.1.0 |
4kB |
Sharlikran |
05/23/14 01:45 PM |
Comment Options |
05/26/14, 05:36 AM | ||
Warning: Spoiler
Above is a quote of Sninni's post. Another proof of concept is Shinni's screen shot of his database for HarvestMap. See the riduclous amount of pins there are? It's because Esohead was recording too many duplicate nodes prior to 0.1.11. (which isn't released) It just didn't handle duplicate nodes well. Esohead 0.1.11 and EsoheadMerge will do a much better job.
Last edited by Sharlikran : 05/26/14 at 05:39 AM.
|
||
|
Sharlikran |
View Public Profile |
Send a private message to Sharlikran |
Find More Posts by Sharlikran |
Add Sharlikran to Your Buddy List |
05/26/14, 05:11 AM | ||
Warning: Spoiler
Lua Code:
That is for Esohead, not EsoeadMerge. You can just take my word for it and just use EsoheadMerge, or alter Esohead 0.1.11 with the above code. If you can paste the above block of code into Esohead and it will spam you with an unnecessary amount of debug messages that will show you what is happening. The reason for you to test it isn't because I haven't tested it but to trust what EsoheadMerge is doing you would have to see Esohead working in action. If you look at the debug spam, you will see that nodes are detected close to the one you are looting. When nodes are really close together but they are named different like Nirnroot, and Water hyacinth, the nodes won't be considered duplicates. Why would testing be this important? Because I have updated EsoheadMerge with the updated routines I have been testing to improve accuracy in Esohead, Harvester, and HarvestMap. I downloaded the latest daily merge file and edited it because it's too big to load. I edited out everything but harvest and, I imported it into EsoheadMerge. Then I restored the file and, edited out just harvest leaving the reset there. Then I imported into EsoheadMerge. The 8.08 MB file was reduced to 3.36MB. That includes all the localized maps like "Schnellwasserhöhle^fd,in". Which is so much smaller I don't know if people will believe what is happening. So yeah, people need to see Esohead in action, see that it's accurate, so that you understand the new EsoheadMerge routines work properly. Also, if for some reason it's not working as it should I can tweak it. However, I don't think it needs further tweaking. I already diligently tested logging a fishing node by standing on one side of it, and inching towards it. That way it recorded my position not where it's actually located. Then ran to the other side to tweak the distance with which you can record a new node. It's not perfect but there isn't a good way to detect the distance you are from your target. ESO API functions don't make it easy. If you are in Deshann by mournhold and you log the fishing node there while your map says "Mournhold" you will get a node. Then when you move just a very small amount of distance away from the city so that your map says Deshann, you will get a new node for the same fishing hole. That can't be prevented. I will continue to test it in case I made a mistake. However, I don't think I have. It's just a much better way to detect the nodes. But with the new routines when people compare the size of the Merge File imported into EsoheadMerge you will wonder why the save file is so small and why there are about half the nodes in all categories. You need to see Esohead 0.1.11 for yourself.
Last edited by Sharlikran : 05/26/14 at 01:05 PM.
|
||
|
Sharlikran |
View Public Profile |
Send a private message to Sharlikran |
Find More Posts by Sharlikran |
Add Sharlikran to Your Buddy List |
05/26/14, 01:17 AM | |
Does this mean there is no longer a limit to how much info you can have in a Savedvariable file without crashing?
|
|
|
Saftsuse |
View Public Profile |
Send a private message to Saftsuse |
Find More Posts by Saftsuse |
Add Saftsuse to Your Buddy List |