Last Played Logger

Version 3.X.X

For older versions of the mod, check the wiki.

This mod logs the last date a player was online/logged in into a Google spreadsheet.
It's a utility mod to help you moderate your whitelist.
It only works on the server side and won't work on the client side.

---

You need a server to play with friends? You don't know how to set up one? Just rent an already configured server!

Click on the picture above, select a plan (with recommended at least 6 GB),
use my code agent to get 25% off your first month and enjoy playing with your friends!

---

Support

Minecraft versions, for which the mod is not released, are not supported.
You can find a text version here.

Server Config

The config file can be found in the "serverconfig" folder in the "world" folder and is named "last_played_logger-server.toml". The name of the world folder is set for servers in the "server.properties" file.

• active
  Shall the mod be active or not?
• spreadsheetID
  ID of the Spreadsheet.
• tab_name
  Name of the spreadsheet tab.

Wonder how do you get these data? Read the "How to configure the mod".

How to configure the mod

Set up the Google Cloud project

The "Last Played Logger" needs its own Google Cloud project with the Google Sheets API. Follow the steps of the Google Sheets Java quickstart listed below. You only need these steps, not the sample code.

1. Enable the API: Follow the steps under Enable the API to enable the "Google Sheets API".
2. Configure the OAuth consent screen: Follow the steps under Configure the OAuth consent screen.
   Important: Under "Audience", select External. Google's guide says "Internal", but this only works with a Google Workspace account of an organization, not with a normal Google account.
3. Create the credentials: Follow the steps under Authorize credentials for a desktop application (Application type "Desktop app").
   Create a folder named "last_played_logger" next to the "config" folder and save the downloaded JSON file as "credentials.json" in this folder.
4. Publish the app: Open the Google Auth Platform > Audience page of your Google Cloud project and click "Publish app", so the publishing status changes from "Testing" to "In production".
   You don't have to submit your app for verification, because only you are using it. Google will show a "not verified" warning during the authorization, which you can skip as described below.

Why publishing the app? In the publishing status "Testing" two things happen:

• Only Google accounts listed as test users can authorize the app. All others get "Access blocked: ... has not completed the Google verification process" (Error 403: access_denied) during the first launch.
• Google lets the authorization expire after 7 days. After that, the mod can no longer write to the spreadsheet and you have to authorize it again (see "Authorize the mod again" below).

If you want to keep the status "Testing" anyway, you have to add your Google account as test user: On the Audience page, click "Add users" under "Test users", enter the Google account that owns the spreadsheet and click "Save". Then you have to authorize the mod again every 7 days.

How to set up the spreadsheet

You can copy this Example Spreadsheet to use it with the "Last Played Logger".
For that, you have to click "File" > "Make a copy".

In the copy window, you give it a name and click "OK".

This "Example Spreadsheet" has two tabs.
In the "Online Log" tab, the "Last Played Logger" adds lines for every player joining the server. For players already joint the server, only the date will be updated.

In the "Statistics" tab, you have two lists. The left list shows all players sorted by name and the right list shows all players sorted by the date. The player last online is the first player in this list.

For the mod it's needed, that the spreadsheet is shared. For that you have to click onto the "Share" button.
In the Share window you have to select "Get Link" and on the right side of "Anyone with the link" you have to select "Editor".

In the config, you now have to set "active" to "true" and set the "tab_name". In this example the "tab_name" has to be "Online Log".
From the URL, you have to extract the spreadsheet ID. In this example, the spreadsheet ID is "1dcoWy1ZOCEzf9wSqpsd731MKr8rBsazUVuUYafF4nzA".

What is to do on the first launch

When you have finished the config and done all previous steps, it gets to the first launch and the authentication of the server/mod.
Important: The first launch of the server has to be on your local desktop pc. During the following steps don't stop the server.
After you launched the server and a player joined, you find in the log a link with the following lines:

Please open the following address in your browser:
https://accounts.google.com/o/oauth2/auth?access\_type=offline&client\_id=...
Attempting to open that address in the default browser now…

Maybe the link is opened by your default browser automatically. If not, copy the link to your browser and open it.
It opens a website where you have to choose the Google account, from the owner of the spreadsheet.

Next, there opens a warning because your project on which the application is running is not verified. You can ignore the warning and click "Advanced".

Next, you click on "Go to " (in the screenshot the app is named "Quickstart")

After that, a permission request is showing up, that wants to access your spreadsheets. "Allow" clicking will grant this permission.

This permission request has to be confirmed.

If you grant the permission and confirmed it, the "Last Played Logger" will work and add players to your spreadsheet.
If you want to enlarge the formatted area, here is a tutorial: https://spreadsheetpoint.com/color-alternate-rows-google-sheets/
The authorization is saved in the file "StoredCredential" in the "last_played_logger" folder.

Server without browser

The authorization only works on a computer with a browser, because Google redirects back to the computer, on which the server is running.
If your server runs on a rented or remote server without a browser, do the first launch with the same mod, config and "credentials.json" on your local desktop pc.
After the authorization, copy the "StoredCredential" file from the local "last_played_logger" folder into the "last_played_logger" folder of your server.

Authorize the mod again

If the authorization has expired or was revoked, stop the server, delete the "StoredCredential" file in the "last_played_logger" folder and do the steps of the first launch again.

---

Thanks for the logo to Muse31.
You can use this mod in non-commercial modpacks without asking.
You can find more mods from me on CurseForge and Modrinth.