Skip to main content

First quest

Yesterday I managed to implement the first quest of the prototype, and a couple of hours later, the second. I can't say I have a proper quest system (if such thing exists), it depends on loosely related stuff.

The first quest implement involves recovering an stolen item, which requires fighting some weird guys. It is like an introduction to combat. The guy drops the stolen item, or more precise, you get it from his corpse. When you talk to the quest NPC, if you have the item with you, a new option appears in the dialog that allows to deliver the item, receive XP and set the quest as completed.

The second quest is to talk with a guy to receive another quest, the one that triggers the main storyline of the game. Pretty easy. And now that I mention the storyline, I made some work on it this weekend.

The key word when writing the plot for an open world is branching, which is easier to say, but not that easy to achieve. It means that almost every quest or NPC should be the entry point for more quests. Lets say that somebody told you that Williams know somebody who craft excellent weapons. But Williams won't simply send you with the crafter, instead he will ask a favor or something. Take a look at the previous RPG games you have played and you will see this concept in action. In The Witcher 3, virtually every NPC you go to ask somethings, requires completing one or more quests before giving what you need. As I said, sounds easy, but it is not for a single writer.

I also included in the story an old friend of mine, who passed away last year. Like me, gamer since the MS-DOS age, with lots of friends who are now scattered through the world. I'm still thinking how to improve his participation in the story and make it more important.

Comments

Popular posts from this blog

Isometric camera with Godot

Took some effort and some of my sleep hours, but at last, I made it. Here is my first videotutorial: implementing an isometric camera in 3D, with Godot. Useful if you want to emulate the look of old classics like Fallout 2, but with some extra features. Considering that my voice is not so nice, and my english pronounciation is even worse, I also added texts to help you underestand what Im saying. You will also notice some background noise, but cant do anything to solve that. Any suggestion is welcome. Expect another tutorial soon.... or sor tof. This time, will be about my AI system.

Lessons about game dev

 Meet Bobby (not Kotick)! He is going to taught you a lesson about how NOT to make games. Bobby is a very sharp bussinessman, that sees everybody is playing games. More important, everybody is spending money in games. What would any smart bussinessman do? Well, get into the games bussiness, and he knows he has an advantage. See, Bobby is not going to spend hundredths of thousands dollars to make a game, when he can make it much cheaper.  And here comes the first mistake. Bobby goes to his birth city, in a shitty third class communist country, where it is easier to find a honest politician than a game developer. There, he assembles the Avengers... I mean, a team of talented guys that... never made a game in their lives. He invests in hardware, with good workstations equipped with fairly modern GPUs, pairde with the worst, cheapest 18 inches display you can get. Also, a server with a 24 VRAM GPU, because any game studio needs a server for... nobody knows exactly for what, but t...

Vulkan and open source engines

It is weird, but even when Vulkan has embraced the open source philosophy (open drivers, tools, etc), Im not seeing too much enthusiasm to adopt it in open source game engines. I have been following mostly Godot and Urho3D, yet Ogre3D and Irrlicht doesnt seems to be rushing to implement the new renderers. It is worth to mention that Godot promissed they would delay the long needed refactoring of its 3D renderer until Vulkan release, but now they say they wont be using it, favoring GL ES 3 instead. The other engines seems to be dealing with lack of man power (Urho3D leader left the work on hands of community, as he is not working on Vulkan renderer right now) and base code designed for older APIs, specifically, DirectX 9. Lot of work is required to adapt this code base, not only for Vulkan, but for DirectX 12 too. Well, nobody said that developing a game engine was easy. The advantages of Vulkan have been widely detailed. From engine point of view, it would centralize all renderers...