I made a horrible mistake with my first game

So for context: I'm a programmer and I like the idea of not using a game engine, but I have no real prior experience with game development specifically.

I thought it was a good idea to make a text adventure game (think Zork) in C, since the language offers great portability, including the ability to run code on the 6502. Also a text adventure game made sense because I can't make art and idk anyone else who wanted to work on a game with me.

This was a terrible idea for a few reasons:

1. A text adventure game is impossible to make with a small scope
2. My from-scratch engine wasn't really designed with modifying the game data mid-development in mind
3. I have no clue what I'm doing.

I just don't know what to do now. Any ideas? @gamedev

VERY WIP. Please be kind :)

This is a talk from BenUI for #notGDC.

Covers UI / UX best practices and thinking through the lens of:

• Letting the player know something
• Letting the player do something
• Letting the player feel something

Slides are available as well

This is a talk from BenUI for #notGDC.

Covers UI / UX best practices and thinking through the lens of:

• Letting the player know something
• Letting the player do something
• Letting the player feel something

Slides are available as well

This is a talk from BenUI for #notGDC.

Covers UI / UX best practices and thinking through the lens of:

• Letting the player know something
• Letting the player do something
• Letting the player feel something

Slides are available as well

This is a talk from BenUI for #notGDC.

Covers UI / UX best practices and thinking through the lens of:

• Letting the player know something
• Letting the player do something
• Letting the player feel something

Slides are available as well

Narrat Jam 2

The Narrat Jam 2 is a month-long game jam for games created using narrat

Narrat is a game engine for narrative RPGs that's very accessible and beginner friendly. It can make narrative games, visual novels, point and click etc, but also comes with built-in RPG features like inventory, quests and skills.

There is also a narrat forum to discuss the jam!

Narrative scripting languages like Yarn Spinner or Inkle were originally meant for writing dialogue, but I think they can also be used for scripting the world progression even when no dialogue or even narration is involved.

Example for something silent that can be scripted with a narrative scripting language:

1. When the player pulls a lever...
2. Move the camera to show a certain gate
3. Open the gate
4. Move the camera to show something interesting behind the gate
5. Return the camera to the player

Even though no text nor voice are involved here, I think a narrative language will still fit better than a traditional scripting language because:

• Narrative languages describe everything in steps. Scripting languages will need to work a bit harder to generate steps the actual game engine can use.
• Narrative languages have visual editor that can help showing the flow of the level as nodes.
• The interface between a narrative language and the game engine tends to be seems to tend to be higher level (and less powerful) than the one with a traditional scripting language.

On the other hand, flow control seems a bit more crude and ugly with narrative scripting languages than with traditional scripting languages. It should probably still be fine for simple things (e.g. - player activates a keyhole. Do they have the key?), but I wonder if a game can reach a point where it becomes too complex for a narrative language (I'm still talking about simple world progression, not full blown modding)

So, this engine is new to me. I was looking for a rendering-only engine (which this isn't) when I found this.
I'm wondering if anyone has any hands-on experience with it, his it compares to everything else out there, etc.
Any recommendation or, on the contrary, advice to stay away from it?

I have plans for making video game, and so far Godot looks most promising out of free game engines (completely free and open source, native script language - GDscript - similar to Python which I know and from yt tutorials it seems very intuitive). Any couterarguments?

I didn't see IndieDev, which is a community I frequented a lot on reddit. Between this one and IndieDev, that's where I spent most of my time. I'm honestly not even sure what the distinction between the two is anymore.

I'm developing my own game from scratch, and up until now I've been using json (nlohmann) for de-/serialization. My game generates a lot of objects procedurally (think of it as Minecraft in size) and objects load/unload pretty slow and occupies a lot of disc space. I've seen lots of people recommend creating your custom serialization instead of using something like protocol buffers, but I cannot find much on the subject in terms of general guidlines and principles.

What I'm looking for:

• Highly performant (probably a format that translates directly from and to the objects themselves?)
• Simple to extend existing classes with serialization/deserialization instructions
• Serialization of objects with nested objects
• Handling of arrays/vectors and primitive types

I might be thinking wrongly on these wishes, please tell me if so =)

I've been pondering and searching for guidance but not finding anything concrete. I thought that there's probably some of you smart people that have experience with this!

Trying to get my page ready by the deadline...

Narrat is a beginner friendly game engine for narrative RPGs, with a UI and systems inspired by games like disco elysium and TTRPGs in general. You can make games for Web and desktop with it and it's very easy to use

I'm working on a game right now and I've added some post processing and I'm loving how it looks, but I'm realizing I don't know anything about it. What does your post processing stack look like? How does it fit into your game's overall art style? Would love some resources on post processing if anyone has them!

I've been working on my 3D platformer, but when people play test it they find the actual platforming part hard to control. I am using the thirdpersoncontroller from unity assets - is there a guide or a book out there that walks you through fair level design and player mechanics? I don't even know what I should be targeting

For me, I recently had to revamp something because I was taught to use PlayerPrefs for saving all game data and had to move everything to a JSON in order to make cloud saves work or even just transfering save files to other devices.

If you had an idea for a game that you eventually wanted to be procedural generated would you first play with the design on a static tileset?

If so is there anything to keep in mind while designing your assets / game objects?

Wanted to share this.

As someone who's an experienced developer in Unity who wanted to learn good practices for how to program player mechanics in Unreal 5, I've found this course to be really really helpful.

Goes over making custom movement modes, ray tracing, creating Animation Blueprints from scratch, and how to dynamically place hands on nearby surfaces with IK. Also shows how to import animations in that aren't using the exact same skeleton hierarchy as Unreal's default mannequin.

I just found out that Battle Bit Remastered exists and it supports 254 simultaneous players per game.

I am wondering how that is even possible. Does anyone know of any details on how they achieved it? Are there any resources for making a networking engine capable of supporting that many players?

I've been going through a course on udemy and learning unreal engine first time ever consistently for the past month, but haven't finished a game just yet, and I don't think I care enough to put any effort on anything other than gamedev. It has been my passion since like 6 years, that's why I left my old job as an Ops engineer; should I continue and work on different projects simultaneously (opengl and unreal) or just stick to one. FYI, I'm not employed atm and would hope to work on gamedev professionally. I appreciate any advice to build my portfolio or any keypoints to get better at gamedev.

tl;dr would learning unreal and opengl simultaneously benefit me to get hired in a gamdev studio or should i stick to unreal and finish some games first?