• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.

Archived

This topic is now archived and is closed to further replies.

ZoomBoy

Event Processing for AI

4 posts in this topic

In a previous thread here I talked about creating a messaging system. For that I'll need In my RPG I've got 2 event types to pass to my message system. One is for the story events(Binky has returned the Golden Shovel to the Royal Foo) and the other is for Action events(during Map movement and combat)
class StoryEvent : class totplist
{
//	char KeyName[40];   // EventName
//	int  KeyCode;       // EventCode
//	char Key2ndName[40];// MapInfo
//	int  KeySourceCode; // Sender
//	int  UPriority;     // UPriority
//	int  ObjType;       // ObjType
//	int  nID;           // nID

};

class ActionEvent : class totplist
{
//	char KeyName[40];   // EventName
//	int  KeyCode;       // EventCode
//	char Key2ndName[40];// Misc info
//	int  KeySourceCode; // Sender
//	int  UPriority;     // UPriority
//	int  ObjType;       // ObjType
//	int  nID;           // nID
	XPos, YPos;			// Where it emanates from
	Range;				// Effective Range
	Duration;			// How long it lasts
	Target;				// Who receives it 
}

Looking closer they seem to be related but do different things. Am I missing any other variables? In relation to Story Events I was looking in Planescape:Torment's quest.txt [init] questcount=125 [0] title=37696 descAssigned=39732 descCompleted=39733 assignedChecks=1 aVar1=Pharod aValue1=0 aCondition1=EQ completeChecks=1 cVar1=Pharod cValue1=0 cCondition1=GT [1] title=39734 descAssigned=39735 .... ZoomBoy Developing a 2D RPG with skills, weapons, and adventure. See my character editor, Tile editor, diary, 3D Art resources at Check out my web-site Edited by - ZoomBoy on 5/26/00 9:03:18 PM Edited by - ZoomBoy on 5/26/00 9:04:27 PM
0

Share this post


Link to post
Share on other sites
Ya the major difference between them(Story vs. Action event/msgs) is putting together the antecedents or necessary conditions for their completion.

With Action messages, they go onto a queue or list and all the current jobs are sorted by priority.

With Story events I need to keep track of them from map to map. Also there are things they need to have and jobs/events to do before a lone event is completed. Maybe a queue needs to be created.

hmmmmmmmmm

ZoomBoy
Developing a 2D RPG with skills, weapons, and adventure.
See my character editor, Tile editor, diary, 3D Art resources at
Check out my web-site
0

Share this post


Link to post
Share on other sites
I think I''ll just do the Action events only until I figure out a way to Sory event checking

ZoomBoy
Developing a 2D RPG with skills, weapons, and adventure.
See my character editor, Tile editor, diary, 3D Art resources at
Check out my web-site
0

Share this post


Link to post
Share on other sites
Probably not relevant, but just a thought: to check whether something is completed, you could have some sort of recursion:


bool Event::IsCompleted()
{
for (all events that must be completed before this)
{
// If any one of them is not done yet, this one
// cannot be done either, so return false
if (!prevEvent.IsCompleted())
return false;
}

if (other requirements not met)
return false;
else
return true;
}

So if every event stores a list of events that must be completed beforehand, you can still just make a single call to Event::IsCompleted() for any given event and that recursively checks all the events it depends on automatically.
0

Share this post


Link to post
Share on other sites
Excellent thought. I had been considering defaulting to a
function called Waiting() that when there was nothing left to do would still do visual and aural checks


ZoomBoy
0

Share this post


Link to post
Share on other sites