Give up the notion that anyone will ever use it, period. Nobody will. This is not meant to be disparaging, but just a realistic fact of programming. I've been working on a very ambitious programming language for years and nobody uses it except me. This is not to say that you shouldn't design it for other people's needs - just don't get your hopes up that anyone will care. If you can do this for your own enjoyment and education, so much the better; if you're only in it because you want to change the world, you're in for a very disappointing experience.

Just to elaborate on this: Epoch, ApochPiQ's language is fairly smooth. I still don't use it as I use my own. Which says everything, I think.

Hello GameDev Community..

I'm currently pursuing Bachelor Degree in Computer Science, and currently brainstorming some ideas for my Graduation Project. My interests include Compiler Theory and Game programming. I've been using XNA for years and some OpenGL.

I've came up with an idea that I'm hammering right now for flaws and things I may not have considered. and some friend suggested that I should post into forums concerning with games. and Here I'm

My idea is creating a new language for games, making game development easier. It will be object oriented and supporting many high-level gaming features like:

auto-implementing state machines
an enhanced pipeline for loading resources (sounds, models, textures, ....)
defining auto templates for screens, memory management, and other things.

Another thing is that I'm fascinated with the drag and drop code snippets from x-code and unity IDE. I'm hoping that I can make my language as easy to write as that !

The idea that it will not be compiled into machine code but to existing class library i will make in c++ and open-GL. then use a c++ compiler to produce a ready game.
This will enable future enhancements to include another compiler to objective-c and java for mobiles, and maybe to java-script or action-script for web.
The same code for all platforms

I'm currently open to all new ideas. Can i hear your thoughts about other features or things to research in? Thanks.

Hi oamsath,

Visual Scripting is in high demand by many Game Dev Hobbyist who don't desire to code. In fact, its one of my motivators for developing The Super 3D Game Platform. I've looked into approaches used by Kodu, Kismet, Alice. What really caught my attention was LBP Logic Gates. Although not a Visual Scripting perse, LBP Logic Gates provides a interactive and visually entertaining way of creating conditional statements. That experience changed my perspective on editing in general and inspired me to start developing a unique type of 3D GUI system. A GUI system to support a serious Game Creation Suite that is fun to play.

The Game Creation Suite will also include Visual Scripting. I've written a Script Engine (its about the closest I want to get to writing a compiler) with a stack-based bytecode virtual machine. Based on that experience, my desire is to translate the Stack and a small Instruction Set into some form of visually entertaining and intuitive representation for the Visual Scripter.

What you are describing isnt a 'language' but more like a game 'engine' with libraries and tools (and as you will probably find a half dozen different laguages/scripts used to define and crossreference and script the many aspects of a game).

Its a very large project that you might want to pare down to something you could accompilsh in you projects allowed time.

Maybe a state engine library for an existing language (hierarchical with exception fallthru mechanism) that would get you off the hook for having to recreate the the general program language part.

If you want to do a visual language the project might be better as a demonstration of why the complexity of game code gets out of hand very quickly and the limitations for a visual interface (being able to see so little logic at one view because of the logic non-density due to the 'visual' presentations overhead and clutter).

I looked at visual 'building block' logic for FSMs over 10 years ago and came to the conclusion that real logic of sufficient complexity quickly becomes unwieldy and visualization of sufficient amounts of a 'program' declined too much -- even with nifty visual navigation mechanisms helping.

My idea is creating a new language for games, making game development easier. It will be object oriented

By "object oriented", do you mean similar to C++, similar to Smalltalk, or something more exotic? Please explain what you consider novel about your design. If it is like existing languages, how can it be better?

and supporting many high-level gaming features like:

auto-implementing state machines
[/quote]
How do you compete with existing state machine code generators? What if one doesn't want state machines?

an enhanced pipeline for loading resources (sounds, models, textures, ....)
[/quote]
Enhanced over what perceived shortcomings of current techniques? This seems a very mature area that doesn't allow significant technical progress.

defining auto templates for screens, memory management, and other things.
[/quote]
Please explain what valuable "templates" you want in your framework. What's the alternative if they don't fit the needs of the game?

Another thing is that I'm fascinated with the drag and drop code snippets from x-code and unity IDE. I'm hoping that I can make my language as easy to write as that !
[/quote]
Are you designing a language and framework, or an IDE? You would be wise to focus on the former.

The idea that it will not be compiled into machine code but to existing class library i will make in c++ and open-GL. then use a c++ compiler to produce a ready game.
[/quote]
If you are committed to C++ and OpenGL, you are leaving out many platforms.

This will enable future enhancements to include another compiler to objective-c and java for mobiles, and maybe to java-script or action-script for web.
The same code for all platforms
[/quote]
This will never happen.
You are talking about a substantial standard library, and implementing it five or more times is an herculean, desperate and useless effort. You should focus on one platform (C++/OpenGL on proper computers) instead of making more compromises than you really need to in order to support different platforms that potential users aren't interested in.