Changes

|version = {{Project64VerVersion|Project64}}

Up to version 2.2, the official installer for PJ64 included opt-out malware in the installer. In July of 2016, the malware was removed from both the source code and installers.<ref>https://github.com/project64/project64/issues/468</ref> However, version 2.3 introduced a benign but irritating nagware screen that pops up when launching PJ64 after starting it multiple times, which grows more persistent with successive launches as a forced waiting period is installed. This You can be disabled type "'''thank you from project64'''" as the notification code, or disable it by modifying <code>project64.cfg</code> to appear as follows: <pre>[Support Project64]Run Count=-1</pre> Alternatively, you can type "'''thank you from project64'''" as the notification code. ===Project64 2.4.0.1555 New Support Code Nag Scheme=== UPDATED MARCH 19, 2021 -There is now a per-machine ID that gets generated on the user side and requests a confirmation code associated with it. -Setting the Run Count to -1 in project64.cfg no longer stops the nag. -The "thank you from project64" code no longer works (obviously, since they are now unique for every machine). 9 JULY 2021 - Thanks for the heads-up, some notes. -You should be able to reset the new counter by removing registry key "user" in HKEY_CURRENT_USER\Software\Project64 (this is just a reset though) -Project64's nag screen won't activate itself too quickly, making testing a little... interesting. -Any change that prevents reading the registry key should also stop Project64 from advancing the run counter. -Code validation is done with a server. Not possible to stop without proxy or patching. -Registry key is also machine ID keyed, however code MAY only be checked on first entry, and a dedicated program could easily generate the registry key for any given machine ID. -Those with even basic W32 API knowledge and C knowledge, consider studying https://github.com/project64/project64/blob/develop/Source/Project64/UserInterface/ProjectSupport.cpp -I think even a Python script could do it, just be sure to GPL the results so someone else can take over. It's just good practice, morals and transparency anyway. I feel like Project64 have just shown they want to wage a war on their users. But also me. 13 JULY 2021 - I said a Python script could do it, now I've done it... [[Project64/NagScreenBypassScript]]

23 JULY 2021 Version 2.4.0.1555 introduced a new method, with a per- Turns out emugen (thread 344228293, post 344459325) already knew of someone else's bypass script, machine ID that gets generated on the user side and requests a confirmation code associated with it. You can avoid it thanks to [https://github.com/Rosalie241/PJ64Launcher - don't even bother with the above lolthis script] by Rosalie241.

Project64 still ships used to ship with Jabo's video and audio plugins , and for many years , used them as defaults (along with his input plugin). These plugins are closed-source, haven't been updated since the 1.7 days, and even have regressions compared to Jabo's 1.6.1 versions. However, Project64 now defaults to its own branded video, audio, and input plugins that are a fork of Glide64, a new audio plugin loosely based on Azimer's and mupen64plus's code, and original respectively. It additionally ships with GLideN64 and N-Rage's input plugin, both of which are recommended over the defaults. Users may still prefer additional plugins for accuracy or feature set, such as Angrylion video, Azimer's audio, and HatCat's RSP interpreter.