Cheat Engine

[AylinCE]

Hello again..
I had a saying for Google Sheets.
I tested its feasibility and I'm publishing the result.

( The first version is available at this link and in Google Docs.
https://forum.cheatengine.org/viewtopic.php?t=613418 )

What's in this version:
1) Used Google Sheets instead of Google Docs.
2) "Version" option for trainer limitation.
3) User registration or usage restriction.
4) Set start and end time for user.

(And of course heed this warning from @atom0s.
https://forum.cheatengine.org/viewtopic.php?p=5758266#5758266
Besides, All these steps are options available after complex protection. )

Before moving on to the code, review some exceptions and create your own table according to this pattern.



1) The first line (1A-1B-1C-1D) should always be reserved for Trainer information.
In order: Trainer name (1A), Trainer version (1B), Admin (1C) and the site link to reach the Admin (1D).

2) All other lines are reserved for user information.
The record order should be as follows:
Username (column A), User ID (column B), Start Date (column C) and End Date (column D) for limited use

Just follow this format for writing History:
09/09/2023--22:50:10
(Day/Month/Year--Hour:Minute:Second)

Note: I recommend you choose the date and time differences according to your country.
The example country used in the Trainer is the Netherlands (ID: 4, and you must take your own country ID number from the table below and write it in the relevant section of the code.

[a2z]

The Trial time sometimes was giving me wrong output. E.g. I put
Trial Start: 09/25/2023--00:00:00
Trial End: 03/25/2024--00:00:00
Which is 6 months, but it was showing me more than a Year..

I have changed some parts to fit what I needed.
Date format: day/month/year
Time format: 24hrs
Remaining Trial : Days, Hours, Minutes, Seconds (Year variable due to leap year, and month variable can be 28, 29, 30 or 31. So I Opted out of year and month).

[AylinCE]

This requires complete modification with a different idea to the entire reading code.
Reading the Trainer game name and version is taken from the first line for different game Trainer and requires spreading across multiple lines.

My advice is to open different documents for different game Trainers using the same base code.
This approach means less workload for the code that reads and parses the document.
(As the rows increase, the reading procedure becomes slower.)
Additionally, a user who purchased 2 Trainers will have 2 different time periods with the same ID, and parsing this into a single document requires an additional element to the document table.

The entire document and code changes.
Document;
Trainer game name
Trainer usage version
User ID
User name
Starting date
End date

It contains 6 items.

In the code, a different test code based on the Trainer game name should be written for 6 items instead of 4 in the document list (Table parsing items.) and after finding the user ID.

If you are still determined to list all these changes in a single document, leave a comment.