I will have to do some testing but it is meant to only scan the time for this week. For join date it should be only new members when you log in. When it refreshes deposits, it should do the same. It should scan for this week.

However, when you have all new files... well then it should take a while because it should be scanning all the time that is in LibHistorie. I might have told it to use the guilds created date.

I will look into it though but it has been working. The only issue I have is that LibHistorie has no way to tell me it is processing new things or not. So that has always been a challenge. In reality it could be done but I just don't have a good way to know and even though it is done it is still saying not finished yet.

If you try with all new files and after say 4 hours it says it's not done try just reloading the UI. Again I will try some tests though. No promises when though.

Slash commands

You have to add the guild number, 1 to 5 in the order you have for the Guild Menu drop down. The new output format is on the description page.

You might have a mod installed that suppresses errors then because I accidentally put an invalid command in the code. It would have said something like, "Lua Error in line 718: Attempt to access a Nil Value". That's about what I had anyway. I didn't screen shot it.

Thank you for bringing that to my attention, I addressed that issue.

In regards to sharing

First before I explain everything, I added the last seen information as a feature and as a simple tool because ZOS broke everything and is not fixing it fast enough. There will be things that are beyond my control. You also may have expectations of ZOS but remember they only provide the information they choose to provide.

I do not have the resources to make EXE files or use other languages like python, java, or jason or anything else, upload that to a site and then make it secure somehow such that no other guild could see the information.

I know people are really used to games like WOW where they have hidden chat channels and such but this is ZOS and they do not allow in game sharing. The first thing that would be used to exploit is player position in PVP.

The GM and the officers will simply need to have a standard to follow. If inactivity is less then a certain amount kick them and log why and share that on some kind of website for your guild or in a Discord channel for the GM and officers only. That way if someone in the guild doesn't follow the standard the player has some recourse to be invited back.

Lastly, people using MM 3.0 feel that the server has unlimited information for certain things. So please remember these things.

The first thing to remember is that ZOS does not log when a user logs out and add that to guild history like guild sales are logged. So unless you or an officer are online, you will not see the players online status change. This is shown in the tooltip and the export as "Unseen" which should mean to you and officers, that you just simply were not online if they logged in and then logged out.

However, I added online and offline tracking to this tool on 3/13 which is several days before I uploaded it. I have been online quite a lot (except when sleeping) and out of 498 members 50 have an Unseen status. If users are not logging in more then a few moments and the mod has not caught their online status, (unless they are in EU and everyone else is in NA) and their sales are low, then to be honest, that's not really activity to me.

This rest covers scanning, so if you don't need to know then skip the rest.

LibHistoire and what the tooltips mean

The server does not keep that much information. The server keeps 10 days for Guild Sales, but only maybe 10 to 20 days for other categories.

For gold deposits if you see numbers that make no sense, like 18704 days ago for gold deposits, that means it is undefined. The time is 0 because they didn't make a deposit recently. I'm not going to refine that at this time.

You will also see values for when the guild member joined such as "> 20 days" or if you have used LibHistoire for 200 days then you might see "> 200 days" and all that means is when LibHistoire scanned the guild information the join date was not available because the server had discarded that information.

Remember also that this is the same as with MM 3.0 where sometimes people feel MM does not see information it should. If the information could have been available (less then 10 to 20 days) then that is server or user related. LibHistoire will auto request information from the server but server load will dictate whether or not that automatic request is approved.

If you need accuracy for deposits or joined data, then be sure to scan the Guild and Bank categories the same way you do for MM 3.0. Also the same as MM 3.0, you do not need to do a full complete scan of any category (pressing E until it disappears) more then once. As long as you pay attention to LibHistoire and request about a day of information each day, and click rescan in the LH GUI, then you should always have accurate information.

Although this last part is related to scanning, LibHistoire is not responsible for the online status. That is instant and part of the game's internal C code.