Can you dm me the link? Also, someone should upload a torrent of the latest version even if it is uncracked so that anyone can try to crack it easily.
Clickteam Fusion 2.5+ Developer with Extensions!
- Thread starter Kippykip
- Start date
I know how to crack Clickteam Fusion. If you could send it to me I can do it for you. Please and thank you.
I know how to do it if you still need help.
Hi, all. I have Clickteam Fusion 2.5 Developer build 294.4 with all DLC including Firefly (no Mac Exporter). Unfortunately, I don't have Clickteam 2.5+. Anyone know how I can obtain the files for it? Then I can post the upload for everyone.
You can try to take the 2.5+ version files in the old versions and put them in the new
Use steamless to remove the DRM but that is gonna leave you with a dummy CTF2.5 because EDRT.exe isnt cracked unless you manage to make the main exe not require a runtime the same version as it then you can use the 292 crack's EDRT.exe
shut the fuck up this doesnt even work its a dummy version
Yeah, I'll experiment. Thanks.
I sent you a DM. Respond at your earliest convenience.
Yeah, because that's only one step of the cracking process. There's a couple others to completely crack it. I would like to help you if you don't mind.
Wow looks great!
Using this c*acked version, getting a lot of File Error! messages for no apparent reason.
View attachment 786
View attachment 786
So Build R292.22 is the latest stable, without File Error! messages? What fixes/features do I miss if I revert to 292.22? I hope that my project can be opened in the older version.
does anyone have a new clique crack?
Well I tried and this is as far as I can get guys.
As for the explanation, R293+ use steamstub drm.
There's also code in the main mmf2u executable that detects the presence of SmartSteamEmu.dll and SmartSteamEmu folders been in there since R292 or so.
Also SmartSteamEmu.ini being present will hide some extensions for some reason?
Attempting to export or use the runtime buttons while SSE is detected will generate purposely unfinished CCA files. Which the runtime generates "File error!". (The same error occurs if you run a sub application and point it to a broken .CCA file).
If you hide the SmartSteamEmu files, you get a "This application has been built with an incompatible version of Clickteam Fusion" error and still get weird .CCA files generated, but bigger ones compared to when you leave SmartSteamEmu files near the main executable, it must still being detected somehow.
I don't think it's checking modifications to mmf2u.exe itself as I can mess around with that in a hex editor and start it with steam and export/runtime stuff just fine. It might be checking for some Steam API functions that mismatch.
Also in this state, exporting as an .exe will actually make a broken .CCA file with a .EXE extension.
The .CCA file contents that make the "File error!" message (SmartSteamEmu.dll & SmartSteamEmu directories present next to mmf2u.exe)
What .CCA file genuine steam outputs:
Fun fact, if you own the genuine steam version, create a blank file called "SmartSteamEmu.dll" for maximum "File error!" lulz
. Turns out they're just generic sub application extension errors when it reads a broken .cca file. And it was mmf2u.exe's anti SmartSteamEmu piracy generating bad .cca files in the first place.
At the time I suggested EDRT was fault we were trying to figure out File Error! We later found out it was something related to SmartSteamEmu files being present, so we hex edited everything SmartSteamEmu named to be ClickteamDumb instead. Which worked fine and is how R292.22 got released here. Now I found out it's only the SmartSteamEmu folder and SmartSteamEmu.dll file that cause this detection which results in "File Error!" during runtime.
edrt.exe is only used when using Runtime but not Exporting. And also yes if you wanted to, you can extract a valid generated .CCA file from the %temp% directory and link it with the sub application object just fine.
But if you point the sub application object to one of the SmartSteamEmu generated .CCA files? You can get both "File error!" and "This application has been built with an incompatible version of Clickteam Fusion". FUN!
If you want to compare the .CCA files yourself, I've bundled them into a zip here.
You can see the differences below!
More info on CCA's: http://web.archive.org/web/20120715000000*/http://www.clickteam.co.uk/resources/GTM/gtm2_6.htm
Anyway if you guys wanna try this out the progress yourself, first here's the Clickteam Fusion 2.5 R294.40 raw steam files RIP
Magnet Link
[Don't forget, you will need a torrent client to use magnet links!]
Doesn't contain CF2.5+ or Flash/Mac exporters though.
Then use a custom hex edited version of SmartSteamEmu Reborn with its StubDRM32 plugin (bypasses SteamStub, another member found a modified winmm.dll worked too with the original non reborn version of SSE).
As mentioned I don't get "File error!" anymore, but a "This application has been built with an incompatible version of Clickteam Fusion" error.
All extensions show.
Alternatively I've zipped up the hex edited version of SSE with the correct arguments below.
As for the explanation, R293+ use steamstub drm.
There's also code in the main mmf2u executable that detects the presence of SmartSteamEmu.dll and SmartSteamEmu folders been in there since R292 or so.
Also SmartSteamEmu.ini being present will hide some extensions for some reason?
Attempting to export or use the runtime buttons while SSE is detected will generate purposely unfinished CCA files. Which the runtime generates "File error!". (The same error occurs if you run a sub application and point it to a broken .CCA file).
If you hide the SmartSteamEmu files, you get a "This application has been built with an incompatible version of Clickteam Fusion" error and still get weird .CCA files generated, but bigger ones compared to when you leave SmartSteamEmu files near the main executable, it must still being detected somehow.
I don't think it's checking modifications to mmf2u.exe itself as I can mess around with that in a hex editor and start it with steam and export/runtime stuff just fine. It might be checking for some Steam API functions that mismatch.
Also in this state, exporting as an .exe will actually make a broken .CCA file with a .EXE extension.
The .CCA file contents that make the "File error!" message (SmartSteamEmu.dll & SmartSteamEmu directories present next to mmf2u.exe)
What .CCA file genuine steam outputs:
There's a lot of misinformation about edrt.exe as I originally thought that was responsible for the anti piracy and thought edrt itself was the culprit before we cracked R292.22
. Turns out they're just generic sub application extension errors when it reads a broken .cca file. And it was mmf2u.exe's anti SmartSteamEmu piracy generating bad .cca files in the first place.At the time I suggested EDRT was fault we were trying to figure out File Error! We later found out it was something related to SmartSteamEmu files being present, so we hex edited everything SmartSteamEmu named to be ClickteamDumb instead. Which worked fine and is how R292.22 got released here. Now I found out it's only the SmartSteamEmu folder and SmartSteamEmu.dll file that cause this detection which results in "File Error!" during runtime.
edrt.exe is only used when using Runtime but not Exporting. And also yes if you wanted to, you can extract a valid generated .CCA file from the %temp% directory and link it with the sub application object just fine.
But if you point the sub application object to one of the SmartSteamEmu generated .CCA files? You can get both "File error!" and "This application has been built with an incompatible version of Clickteam Fusion". FUN!
If you want to compare the .CCA files yourself, I've bundled them into a zip here.
You can see the differences below!
More info on CCA's: http://web.archive.org/web/20120715000000*/http://www.clickteam.co.uk/resources/GTM/gtm2_6.htm
Anyway if you guys wanna try this out the progress yourself, first here's the Clickteam Fusion 2.5 R294.40 raw steam files RIP
Magnet Link
[Don't forget, you will need a torrent client to use magnet links!]Doesn't contain CF2.5+ or Flash/Mac exporters though.
Then use a custom hex edited version of SmartSteamEmu Reborn with its StubDRM32 plugin (bypasses SteamStub, another member found a modified winmm.dll worked too with the original non reborn version of SSE).
As mentioned I don't get "File error!" anymore, but a "This application has been built with an incompatible version of Clickteam Fusion" error.
All extensions show.
Alternatively I've zipped up the hex edited version of SSE with the correct arguments below.
Last edited:
Hello guys,
I'm new to the forum, but I've been following this thread for a long time.
How's it going? It's been silent for some time now... Is version 292.22 the best working, version here right now?
I'm new to the forum, but I've been following this thread for a long time.
How's it going? It's been silent for some time now... Is version 292.22 the best working, version here right now?