Developing games with Unity without the Unity editor. Is it possible to?

Question

Unity

Hello.
I want to describe the situation.
I'm blind. Completely blind.
Among the blind programmers, there are those who develop sound games.
What does it look like?
Imagine GTA, Mafia, Call Of Duty, any shooter. Only without graphics, and without the height of the sight. And you navigate by the 3D sound, shoot by the sound, etc.
Lately, there are a lot of people writing in Python. But personally, I wouldn't trust Python with a good online project...
I love C#. I love this language. Therefore, I decided that I would try to write in C#.
If we develop in pure C #, then we need:
Game window, keystroke processing - Win Forms;
Sound - OpenAL and other libraries.
But I decided to try the engines. Such as Unity and Monogame.
Monogame is quite accessible, it works.
Now, to continue, it should be noted that we use screen readers to work with the computer. Programs that sound everything that is on the computer screen.
More details can be found here:
https://habr.com/ru/post/260463/
https://habr.com/ru/post/336600/
What is the problem with Unity?
Unity editor is not available. At all.
I don't know with what tools it was developed, but navigating through the interface is unrealistic.
Blind developers have repeatedly written about this on the official Unity sites, but alas, we have not been heard for many years.
My question is the following:
How Much Should You Do in the Unity Editor? How can and is it possible to write game code in the studio without resorting to an editor, or to reduce it to a minimum that can be done on Autoit?
Thanks in advance!

Answer 1

Some part is possible. If you DO NOT need a visual in the game (a game for the blind), then in principle 90% of the tasks there are solved through code.
If a visual is needed, then it will be much more difficult, but still not impossible.
But to sum it up, a unit for "writing games ONLY with code" is not the best choice.

Answer 2

You need to understand: what actions are impossible in the code without the Unity GUI, how exactly this happens and port all the work (drag-n-drop bindings, changing properties, etc.) from the GUI to the "pure" API.
Complicated? Yes.
Maybe? Definitely!