Yeah, I, wasn't so lucky in that regard. I started with python, but when I picked up BGT a lot of that went right out the window, and BGT's manual teaches you some really, really bad habits I had a hard time unlearning.

The problem with C# is that it forces you to use an IDE. Don’t like VS or VS code? Too bad, you’re shit out of luck, basically. In my experience VS is also extremely laggy with NVDA, and I despise the whole business of adding references with a GUI.

@28: Audiogame devs are concerned with security. C# isn't very secure when packaged as an executable. Neither is Python, but Cython is easy enough to implement effectively. Securing a C# project seems to start with writing a C++ loader yourself.

@31 this might be the case however I was lucky enough to start learning it already in an accessible manner. I find visual studio very friendly towards screen readers and the lag isn't that bad on my machine with the settings recommended by my teacher, who happens to be completely blind aswell. Mainly I had to disable previewing and this fixed most of the issues I was having with the lag.
As for language specific challenges I admit I am not experienced enough to have faced them but I hope to gain enough wisdom in the future to be able to easily switch between languages. As my teacher pointed out, once you think like a programmer you can easily learn the specifics of a language in a few days and be able to work with it effectively.
My advice for the OP is to get a teacher or a mentor, this will greatly help you because you can gather a lot of information from how he perceives and explains things related to programming.

@28, yeah, what 31 said: people seem to be utterly obsessed on security around here. And I don't really understand why, and this is especially from people who don't know what they're doing either. Security is good and all but there's no reason to obsess over it until you actually need it. And most of the time the ones who claim they need it actually don't, e.g. those who want to protect their code.

If we're talking about things like data structures and sorting and whatever, I rarely write my own algorithms.  When I do write my own algorithms, it's almost always a slightly modified variant on something someone else came up with first.  When it's not, it's usually a variant on something I did in the past.  I don't think I can do anything but a couple basic tree/hashtable things and mergesort without looking it up.  When I do do my own algorithms, it's basically the only thing I do that day.

Learning to think is important.  Learning to write sorting algorithms and things is almost irrelevant.  A JRPG needs almost nothing, not even proper physics.

The rhythm rage level creator was me taking what I knew and just putting it together. I didn't even expect it to work. Strings, functions, integers, and file writing was about all I knew. No arrays, no classes, no dictionaries, and I didn't even know how to return data from a function back then. But somehow, I made it work, by thinking about what concepts I had and what I could do with it. I couldn't load data. I couldn't make an array of aliases or macros. But I could write a very basic program that converted your key presses to a rhythm rage level. And from there, I just kept going, and I learned more concepts even if I hated them. I hated timers back then. I hated arrays with a passion when I found out what they were. But because of that tiny project that I put what I had known so far together, it gave me reason and the ability to learn more and add that new knowledge to that project, and later more projects. It is true what they say. Once you start making your own stuff from scratch, you slowly begin to find potential and create more potential. Modifying already existing projects is ok for learning how to change functions or if statements, but it doesn't teach you how to assemble anything yourself. It just clicked for me once I put that project into motion. I actually didn't even know the difference between sound pool and a sound object. I couldn't even write a script that plays a sound then exits. But overnight, I just kept building once I put one thing in place, testing every single small piece one step at a time. And by morning I had a project that supported aliases and even macros. A very very shitty one, but I was more than grateful it worked, because less than 12 hours before that, I had nothing. That project would later go on to support several different ways to make a level and several useful and useless features throughout the 2 years I worked on it. RIP rhythm rage, because that's why there is no python version of the creator. Plus Oriol could just make one himself in less than half the time with twice as many features.

@21
I guess I'm late and I don't want to derail the train entirely but the answer to your question is that if you want a multi-language library as opposed to something that's just usable by Python or whatever then you have to use C, C++, Rust, or one of a couple other lesser-known options, and you will hate yourself because C/C++ are hard even to those who know them, Rust fries brains of new programmers, and the lesser-known options are lesser known for good reason.  Don't try for this if you're new.  Learn to code well first.

I mean, out, I don't know.  Sam Tupy hacked it somehow.  But if you're thinking that you can represent a player's facing direction as a variable called degrees and do it that way--kind of?  But not really.  If you want something like a Swamp radar out of it then you need trig and a raycaster.  So you'd have to specifically design around anything that needs trig, which you can do it, but you'd be pretty constrained.  North/south/east/west is much much easier.

Hello everybody. I also join the discussion because I know the Python language, I managed to make some small games, like guess number, I played a bit with some functions of Lucia and Earwax, however I lack a guide on how to continue to create an rpg.
Since Jaide asked for help on how to create an rpg, I think that it could be useful to many a guide, also written in a collaborative way, on how to continue, starting from the basics of Python, to develop everything you need for an rpg: that tools to use, how to build a map in an accessible way, etc.
I realize that writing such a guide could be challenging, however I think there are many people who would like help developing their game. So far the only guide of this kind is for the BGT language, which as everyone knows it is advisable not to use.

That's kind of the point of this topic. How to learn programming such that you don't need a guide out there for every type of thing you want to do. If someone writes a guide, then whoever follows it will produce a game that is not really unique, and not really their own. Oh maybe they fudge around the numbers, but it's still got the same mechanics. We don't need a guide telling us how to develop RPGs.

no the other guy