Ideas Lab

Real problems people complain about online, pulled every morning and scored out of 100. Build, validate, or skip. How scoring works

Ideas
4,820
BUILD
702
Sources
8
Last sync
7h ago
382 ideas
Dev

Obfuscate GDScript in production export

### Describe the project you are working on Any project which can be released publicly where the developer might not want to have their code or structure implementation easily stolen. ### Describe the problem or limitation you are having in your project Currently Godot [supports encryption of the exported files](https://docs.godotengine.org/en/stable/development/compiling/compiling_with_script_encryption_key.html) (if you use a custom build of the export templates) However this is not really good enough. Almost every successful engine will at some point have a decompiler for the exported assets. (see [ILSpy](https://github.com/icsharpcode/ILSpy)). In-fact, due to the open source nature of Godot, I think it would be relatively simple to write a script-dumper, that uses the encryption to first de-crypt the files and then just dump them to some output folder once they've been loaded into memory. Many others have also been worried about this issue, quite often with those issues being closed when the discussion goes more towards DRM or encryption. ### ❗️ This is not a discussion about DRM or Encryption ❗️ https://github.com/godotengine/godot/issues/39115 https://github.com/godotengine/godot/issues/24716 https://github.com/godotengine/godot/issues/19790 ### Describe the feature / enhancement and how it helps to overcome the problem or limitation When exporting to production, exported GDscript files can be obfuscated with the names mangled. In this case, adding encryption would add a layer of security, and if someone does decide to extract the files from the pck, they are left with an unintelligible mess of obfuscated code. This additional security would put godot at the top end of protecting game assets, and likely bring users to our community. ### Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams An example implementation [can be found here](https://github.com/javascript-obfuscator/javasc

GitHub4y agoToolDev

62FL score
0Sign in to vote

Do not require OpenRouter API key when running local models (Ollama, LM Studio, custom URL)

I love the idea here for Claudish. Having used `cline` and feel like I'm going backwards in tooling, being able to use Claude-code with local models feels like a game-changer. However.... ### Problem Claudish requires an OpenRouter API key even when running with a local model such as `ollama/llama3`, LM Studio, or a custom HTTP URL. This blocks users who only want to run local models and do not require any cloud/OpenRouter features, and creates confusion for users who have no need for an OpenRouter account or API key. ``` # tried with `ollama/model` syntax ➜ ~ claudish --model ollama/devstral-small-2:24b OpenRouter API Key Required Get your free API key from: https://openrouter.ai/keys ? Enter your OpenRouter API key: > API key cannot be empty # Also tried with endpoint to ollama ➜ ~ claudish --model http://localhost:11434/devstral-small-2:24b OpenRouter API Key Required Get your free API key from: https://openrouter.ai/keys ? Enter your OpenRouter API key: ``` ### Proposal - Skip OpenRouter API key prompting and key checks when the selected model source is a local provider (e.g., model IDs starting with `ollama/`, `lmstudio/`, or a local HTTP URL). - Only require the OpenRouter API key when the chosen model is actually provided by OpenRouter (e.g., `x-ai/grok-*`, `openai/gpt-*`, etc). - Update CLI startup logic and documentation to clarify when the key is and is not required. - Ideally: fallback to degraded behavior or warnings if OpenRouter-only features are attempted with no key, rather than full CLI exit. ### Benefits - Makes Claudish friendlier for fully local/offline workflows. - Avoids unnecessary prompts for users who will never use OpenRouter cloud models. - Clearer separation of local vs cloud/backend authentication requirements. ### Background Related discussion and code: - [src/index.ts](https://github.com/MadAppGang/claudish/blob/main/src/index.ts) - unconditional API key prompt in interactive mode. - [src/cli.ts](https://github.com/MadAppGa

GitHub10mo agoToolDev

67FL score
0Sign in to vote