Some things you need to know

Contens

If you're thinking about getting started with SymOntoClay there are a few things you should know. SymOntoClay lets you create game AI in a different way than you usual do. As such, you should take time to inform yourself before using SymOntoClay for any serious projects.

I know that learning and using SymOntoClay by others is very unlikely yet. But I must take steps to prevent misunderstandings.

Plus another language, in addition unknown

SymOntoClay is only for creating game AI. This means that all other parts of the game (animations, visual effects, scene management, etc.) will need to be done in the scripting language of your game engine.

For Unity this means that you have to write one part of the code in C# and the AI code in SymOntoClay. Create game with two different programming languages is not convenient.

Also SymOntoClay is unknown language. You can not find developers who know this language.

I hope that in the future the benefits of using SymOntoClay will outweigh these obstacles. But now that's far from the case.

SymOntoClay lacks features for game development

I'm focused on adding interesting features that will make SymOntoClay stand out from other languages. But I don't have enough free time. Therefore, many important, but not impressive, features are not added to the language for a long time.

As a result, SymOntoClay has many interesting features (like fuzzy logic or complex triggers), but lacks many of the features that even the simplest programming languages generally have.

SymOntoClay does not have a debugger.

Module (package) infrastructure and standard library in very rudimentary state.

In general and frankly, I think that SymOntoClay is still too experimental and raw for practical use.

SymOntoClay contains many bugs and is very unstable

I'm focused on adding interesting features that will make SymOntoClay stand out from other languages. But I don't have enough free time. Therefore, SymOntoClay contains many bugs and is very unstable.

Right now my main goals are:

to add more interesting features
to make the simplest Zero player game in SymOntoClay

Bugs are fixed only those that are direct obstacles to achieving these goals.

SymOntoClay is very slow and consumes a lot of computer resources

I think that to some extent, slowness of NPC code is normal. This makes the NPC's reaction speed similar to the player's reaction speed.

But with more than 10 NPCs, they become too slow. When the number of NPCs is more than 30, they generally stop react to anything.

My PC:
CPU: AMD Ryzen 5 4600H with Radeon Graphics, 3000 Mhz, 6 Core(s), 12 Logical Processor(s)
RAM: 16.0 GB

I'm thinking of ways to improve the performance of the engine and have planned to implement several ways. But as I mentioned before, I'm focused on adding interesting features and don't have free time to optimization.

SymOntoClay does not have a community and is being developed for free by only one person in his spare time.

I am developing SymOntoClay in my free time. Development is not too intense because SymOntoClay is a hobby and also I want to keep work-life balance.