Skip to content

Glitchless Build #1

@PussInScreen

Description

@PussInScreen

Is your feature request related to a problem?

Honestly... Not really....

Describe the solution you'd like.

The idea is to patch all found glitches and exploits in the original Jak series games that are considered mostly harmless or beneficial in some regards, i.e. patch legacy glitches that are sometimes used intentionally by the community (primarily speed-runners) or considered not worth patching in the main project.

The benefits for this feature is twofold;

  1. Reinvigorate speed-running of the game with a new category that renders old speed-running tech and strategies redundant. Possibly even introducing a need to find new unknown glitches and exploits (even if these are introduced as part of the build itself... In which case I can make a sequel... 😉).

  2. Provide newcomers with a more polished experience, higher likelihood that "jank" and other oddities will not occur.

This will stay as a fork from the original project as fixing some of these bugs / glitches / exploits could prove volatile to the main build of OpenGOAL and its gameplay. It may also lead to a Ship of Theseus issue where replacing original components and mechanics from the game flies in the face of game preservation and may lead to "fun" or "OG" mechanics being removed. However patches may be cherry-picked if needed and the community considers them beneficial to the main project.

There will be no official "release" of the glitchless build until all items in the additional context below have been completed and I've created an actual official build (v1.0 as it were). Once this is done there will be no further patches or code changes made in order to preserve consistency. Instead, as hinted at before, a v2.0 can enter development with further patches and such applied. The idea is that when this releases, it is flawless in regards to glitches and exploits as at the time of the release. Throughout development I'll keep the associated branch synced with the master branch of the main project so as many QoL improvements and other features are included as possible.

Please be sure to mention anything I may have missed in the comments below, I'd love to discuss all of this! 😀

Additional context

The following is a list of things to be patched or fixed in this build;

Edit 1; Finished off the list of things to do and added more context into what the finished build will look like, also invited people to make suggestions.

Edit 2; Still adding to list, it's going to be huge... I won't make note of any of these edits in the future.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requesthelp wantedExtra attention is needed

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions