HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
godotengine
godot-proposals
OPEN SOURCE2020–2026
godotengine / godot-proposals

godot-proposals

Godot Improvement Proposals (GIPs)

26Distinct people
29Mentions
0Explicit recommenders
1.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Godot Improvement Proposals (GIPs)

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:01:57 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year29 dated mentions

Observed mentions: 2020-01-29 19:13:19 UTC to 2026-07-28 13:45:17 UTC.

0369122020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 11 mentions; 2 submissions, 9 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC707
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC1129
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC303

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Godot Improvement Proposals Welcome to the official Godot improvement proposals repository! Here, the Godot community shares and discusses ideas to improve the engine. Everyone is welcome to participate. If you have an idea, please read the introduction below to get started. We also encourage you to browse existing proposals and participate in their discussions. TipUse the Godot proposals viewer to browse proposals, and the discussions tab to browse ideas. Bug reports are not a subject of the proposal process. If you experience an issue while using Godot that cannot be attributed to a missing feature, please file a bug report instead. How to suggest improvements You have two options to suggest improvements for the engine: issues and discussions. To create a proposal issue, you should have a well-developed idea of the change you're suggesting, and put effort into a highly detailed description of it. Please read the rules below before you create a proposal issue. You may also wish to read about our evaluation process to improve the chances of your proposal being accepted. If you have a more general idea for an improvement without specific details, please start a discussion instead. We also encourage you to iterate and expand upon ideas of other contributors and try to formulate proposal issues (with appropriate attribution to those other contributors). This helps the ideas come to fruition by giving the community something specific to discuss or implement. All proposals, both issues and discussions, will be discussed and evaluated by the community, and may even end up being implemented by a fellow motivated Godot contributor. Keep in mind though that all changes need the approval of Godot maintainers before they can be merged. Rules for proposal issues Note: The following points describe requirements for a proposal issue. A discussion, on the other hand, can be started in any form. Do your research. Before you post, discuss your idea with the community, to find if other people are experiencing the same problem and brainstorm solutions together. Search existing proposals and ideas for potential duplicates. And search the internet and asset library for addons that can solve your problem without an engine change. Use your own words. You are not allowed to use AI / an LLM to write your proposal. AI-written proposals are hard to read and often invent facts and solutions that won't work. If you aren't comfortable with English, write your proposal in your mother tongue and use dedicated translation software (not a chat bot) to translate it into English. Give context to your problem. To give an example in cooking: Say you wanted to bake a cake and found a recipe. Don't write your problem as "I need flour", write "I want to bake a cake". To add flour is the proposed solution. You should also describe which workarounds you tried and link related proposals. If you do not provide a well-founded motivation, your proposal will be closed. Be specific with your solution. It is not enough to describe just the idea; your proposal should make all the necessary design decisions such that they can be discussed by the community. Include images, mock-ups, diagrams, code, if applicable. If your solution lacks in detail, is ambiguous, or otherwise unactionable, your proposal will be closed. Use one issue per proposal. Do not cram multiple feature requests into a single proposal, as this makes it harder to discuss features individually. Have patience. Godot is community-driven: if no other users are interested in your proposal, it will not be added to Godot. Remember that the more effort you put into your proposal, the more likely it is to gather attention. You could also share and discuss it in Godot's community channels to draw attention to it. What to do if your proposal is closed We usually only close invalid, duplicate, and rejected proposals. We do not close proposals lightly, but we can make mistakes: If you think we should re-open it, please join us in the contributor's chat and describe the situation. If your proposal was closed as invalid, please review the rules above and put more effort into your next proposal. If your proposal was closed as a duplicate, please review the linked proposal. If it is truly duplicate, or more detailed than yours, we encourage you to support that proposal and contribute to its discussion. If you think your proposal is sufficiently different to stand on its own, please appeal this decision by making a comment. If your proposal was rejected, please review the stated problem and see if you can find another solution. Often, solutions that are rejected for Godot can be implemented as a plugin or GDExtension. How we evaluate proposals The following is a list of considerations that Godot maintainers use when deciding to accept, close, or leave a proposal open. These considerations are in balance; no one is more important than another. Godot maintainers have discretion to weigh the factors as they see fit. In addition, consider reading this article which describes technical considerations of Godot maintainers for new features. 1. Does the proposal comply with the rules? Read the proposal and check to see that it complies with the above-stated rules. If it does not, close the proposal. 2. How much support is the proposal receiving? Evaluate the amount of support the proposal is receiving. This is an ongoing analysis. If a proposal receives little support at first, it may receive additional support later on. 3. Can this proposal be implemented with an addon or GDExtension? Evaluate whether it is possible for the solution to be implemented as an addon or GDExtension. If it is possible for the proposal to be in an addon, it is less likely to be accepted. 4. Does this proposal benefit most users? Determine whether this proposal benefits all users, or just certain users. For example, a feature that can only be used for 3D FPS games is less likely to be accepted th
Read the full README on GitHub

What Hacker News says

7 sources
We're working on those, but at some point Godot Engine 4.0 needs to ship.. * https://github.com/godotengine/godot-proposals/issues/4435 (spatial audio) * https://github.com/godotengine/godot-proposals/issues/3904 (network interest management) * I can't find the proposal, but we, V-Sekai, call those physical materials or sound materials. Like a piece of concrete has different friction and a different sound. The worst part is it requires the Godot Engine 4 artists to conform to like 300 materials.
In Godot 4 Beta 1
> One person can effectively stall all progress out of spite. I'm not sure about this one, I can understand why someone might agree with some of the arguments about list comprehension making readability worse, like stated in this comment: https://github.com/godotengine/godot-proposals/issues/2972#i... I have to agree with @pycbouh. While a lot of things python does is good, I really don't like list comprehension, especially when it becomes nested. numbers = [[1, 2, 3], [4, 5, 6], [7, 8, 9]] print([n for sublist in numbers for n in sublist if n % 2 == 0]) # > [2, 4, 6, 8] Not very readable, and you save what, 3 lines? Not worth. Some might enjoy writing code like that, others might dislike it. The current lack of such functionality doesn't hold anyone back that much and therefore doesn't get prioritized. It might get intro
Read the rest
duced in the future, but when there is still lots of discussion for and against adding it instead of how best to actually implement it, you know that the time has not yet come. Personally, I enjoy both LINQ in C# and Streams in Java, perhaps more than a one liner. But again, that's a personal preference and the opinions are often split about syntax related questions.
In Godot 4.0 development enters feature freeze ahead of the first beta
Godot is effectively not accepting contributions, and masquerades as open source. List comprehension, one of the most sought-after features and requested by dozens of people, is repeatedly undermined by maintainers, because they happen to dislike the syntax. Godot offers nothing similar in terms of processing arrays, so it makes any code involving them ugly and more complex than it needs to be. There was even a pull request implementing this feature opened, but they claim the assigned maintainer just didn't have the time to review it yet (over 5 years!). One person can effectively stall all progress out of spite. That's no way to run an open source project. Just look at this discussion: https://github.com/godotengine/godot-proposals/issues/2972
In Godot 4.0 development enters feature freeze ahead of the first beta
Of course. I use both the built in Godot profiler and perf. Which led me to change many things in the implementation and I also ended up patching the Engine multiple times. One example is this (which I have patched on my Godot version): https://github.com/godotengine/godot-proposals/issues/4050 I profile my game all the time, but sometimes it's not clear if there is a bottleneck or if there are just too many things at the same time. Also the bottleneck can change in different parts of the game. Sometimes I have removed a bottleneck on the CPU just to find another in the GPU.
In Roguelike Tutorial in Rust (2019)
> can't tell what kind is the wrong kind To some extent you can tell from their title and previous work, just like with developers. Foe example, I had an entirely non-technical boss that understood I might not be the guy to re-write some printer drivers because I was a web developer. He didn't know the specifics, but being in charge, knew he had to ask someone who did, or do enough research to figure it out. Likewise, UI designers will specialize in designing UIs and be better at making buttons look like buttons than Graphic Designers, and Experience Designers will be better at integrating user feedback and research into projects. Just like you wouldn't trust any one developer to implement critical functionality you don't understand without outside input, you probably shouldn't rely on one designer to that either. If you maintain a projec
Read the rest
t, though, you can't expect designers to instinctually work around what you don't know. Being in charge means that you're in charge of figuring out how to evaluate it. I'm positive that a "I'm not sure how to interface with this sort of thing. Let's work through it so I can figure it out." will be received kindly by people you should consider working with. Good design proposals should already come with explanation and justification to help you down the path This is a random selection from a google image search of proposal ideas. It was from another post where I was talking about higher-level topics but the principle is the same. Changing a set of control widgets should require no less thought and explanation. https://github.com/openstreetmap/iD/issues/759 https://github.com/stashapp/stash/issues/1549 https://github.com/newrelic/nr1-groundskeeper/issues/3 https://github.com/creativecommons/creativecommons.github.io... https://github.com/godotengine/godot-proposals/issues/1823 > Developers absolutely refer to developers with glib contempt. ok— now copy and paste the rest of what I wrote. An overly opinionated, defensive person with veto powers that understands the purpose and value of your work is fundamentally different.
In The end of the nice GTK button
You've never seen a thorough design proposal? Typical commercial pre-wireframe research and proposal: https://web.stanford.edu/~eadolfo/cis-redesign/attachments/p... More common in FOSS: https://github.com/openstreetmap/iD/issues/759 https://github.com/stashapp/stash/issues/1549 https://github.com/newrelic/nr1-groundskeeper/issues/3 https://github.com/creativecommons/creativecommons.github.io... https://github.com/godotengine/godot-proposals/issues/1823 (from google searching for things like site:github.com "wireframes" "design" "proposal") > a) They have, b) it's definitely not rare, and c) it is an enormous time-drain and source of frustration for maintainers in the FOSS community. I can't claim to be omniscient but I've been a constant open source contributor for 10 odd years and heavy user for nearly 25 and I've never seen that, or ev
Read the rest
en heard people complain about it, let alone enough to be an enormous problem. I've seen ill-conceived gripe lists, superficial 'lets make this look cool,' and 'this font sucks' type issues periodically. None of those are serious design proposals any more than "make everything faster" or "I hate when your program does x" or "I think we should get rid of this and make it in react" are serious development proposals. I'll happily put together a guide on cutting through bullshit UI change proposals if I could evaluate some issues/PRs for open source repos that constantly experience this problem.
In My Pinephone Setup

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.