Next generation modding platform for Final Fantasy VII (Steam 2013, Steam 2026 Rerelease, GOG, Windows Store) and Final Fantasy VIII (Steam 2013)
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
julianxhokaxhiu/FFNx has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in julianxhokaxhiu/FFNx respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 8.0 places julianxhokaxhiu/FFNx in the D tier.
The external contributor pull request merge rate for julianxhokaxhiu/FFNx is 0.0%, based on public PR activity from non-core contributors.
julianxhokaxhiu/FFNx currently has 9 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/julianxhokaxhiu/FFNx?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
I followed the Install Instrcustions for the 2026 steam release. And i thought the german release is supported aswell. But after doing everything in the instrucstion. The game now starts always in english. And i dont see how i can change the language. Ive seen possibilitys for other versions like the 2013 version by just changing the exe file. But the 2026 doesnt have that. At least as far as i can see. it seems no achievement are triggered. (i also tryed to use the german exe just in the 2026 release dictonary. And it worked is german now. But still no achievements.
Summary Currently, the enable_analogue_controls option adds both analog movement in the field, and a free analog battle camera. This should be separated into two options: one for movement, and another for the battle camera. Motivation The two features enabled by the current option, while connected by their use of the analog stick, are otherwise wholly separate in terms of functionality. Barring some sort of technical constraint, there's no real reason to force a user to use one in order to have the other.
Describe the bug When enabling external mesh loading, the lighting of field models gets modified, even when there are no external meshes being loaded. When enabled, it looks like some form of ambient occlusion is being added, regardless of the advanced lighting option. Screenshots external meshes on, advanced lighting on external meshes on, advanced lighting off external meshes off, advanced lighting on external meshes off, advanced lighting off GPU (please complete the following information): Brand Nvidia (RTX 4070 SUPER) Driver Version 610.47
Describe the bug The stage has a much darker, contrasting border running along the grass at the bottom right, and the water is different. The PSX version proves this is not the case, as it is less dark and smoother. Field name: mogu_1 ( mogu_1 kujata-webapp ) Screenshots PC Steam 2013 PSX To Reproduce Steps to reproduce the behavior: Save05>Game06 ( FF7PC_savegames.zip ) Go to 'Wonder Square' then play 'Mog House' See error Expected behavior Border less dark and smoother. Water corrected. GPU (please complete the following information): NVIDIA 32.0.15.9186 Additional context Low priority bug. Could it be related to the old solved #99 ? Or is it related to any of these: fancy_transparency/shader/alpha/blending/pure black/pure white/smooth semi transparent pixel ? No Mods 7H 4.5.2.6 FFNx 1.24.3.6 PC Steam 2026 (less obvious due to bilinear filter but still there)
I've opened issues regarding sub functions of this opcode before, but I think at this point it's probably better to have a master issue for all of them. The KAWAI opcode is a collection of functions related to model graphical effects, usually pertaining to model lighting. It was left mostly nonfunctional in the PC port, and so its functionality needs to be recreated for FFNx. KAWAI has 15 sub-functions. Working in FFNx already: KAWAI 00 (Eye/Mouth system) KAWAI 01 (Activate/Deactivate Blending) KAWAI 02 (Ambient) KAWAI 06 (LIGHT) KAWAI 0A (SBOBJ) KAWAI 0D (SHINE) KAWAI 0E (RESET) Has functionality but not working as intended: KAWAI 07 (Unknown 7) This KAWAI seems to be some kind of alternate lighting system for models. Used on boulders in Temple of the Ancients. Has strange effect when used currently, so has been no-op'd. KAWAI 08 (Unknown 8) This KAWAI seems like it is supposed to color portions of a model progressively over a stretch of time. In the port it seems to just set th
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to julianxhokaxhiu/FFNx, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of julianxhokaxhiu/FFNx acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
julianxhokaxhiu/FFNx has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 8.0 places julianxhokaxhiu/FFNx in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, julianxhokaxhiu/FFNx currently has 9 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for julianxhokaxhiu/FFNx are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.