Not at all presuming that you might be thinking just a little about me, given the dashing, debonair and devilishly handsome gentlemen who, besides me, write the majority of our walkthroughs, but just in case:

Symantec has started blocking access to your websites in North America (and presumably elsewhere) with their internet security programs. For the last 2 weeks they had listed your website on their search notices as "suspicious". Within the last eight hours Symantec has starting declaring trle.net and the forums as "unsafe" due to a virus. The user has to choose to go to trle anyway. The downside to this is that new or potential users will simply avoid your site and the custom levels, and the Tomb Raider editor community will gradually wither away over time.

Symantec has based their decision on the inclusion of the level "Search for the Ankh" by Jean from 2013 on your level page, which they say has a virus not a Trojan. Check it out!

Symantec has blocked treditor.hu for over a year based on multiple levels (even though there is no problem), but they never blocked trle.net until you rebuilt the site. You better see what you did in your rebuild that creates the suspicions.
This situation will only get worse over time because the protocols for files and websites to prevent viruses/trojans are becoming more intense due to the worldwide hacking problem.

NO
forget it TombTitan
you refer to one of the most resources eating programs ever created
if u only have a ordinary hdd i wanna bet it take 5 or more minutes to start your pc
dunno about a ssd
but check out this site https://www.virustotal.com/
Symantec want to install something on my Pc and that's not gonna happen
and you know that all tr4.exe files are false positive cos they are patched

More recently google has claimed the site to be unsafe and then as a webmaster I can follow a few steps and then their robots check again and suddenly we are not unsafe anymore...

The problem is that a well intended approach at making the net "more secure" does stumble across the issue that automated rules do not work really well when exceptions come into play - like the false positive tomb4.exe files...

There is not much I want or can do about it though. I certainly have no intention of removing levels with patched tomb4.exes. As and when I find these kind of "warnings" I usually go there and trigger the process to clean it up - at least where such a process is being offered...