Please login or register.

Login with username, password and session length
Advanced search  

News:

Forum rules - please read before posting, it can save you a lot of time.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Akusa

Pages: [1]
1
Game design / Gameplay Evolution
« on: February 20, 2009, 02:39:10 AM »
Hi there. I was thinking about how to advance some typical gameplay elements of the adventure genre.
The first thing i was thinking "today adventures need comfort". So i did some research and found some typical gameplay elements i want to see in every new click&point game and should be some kind of standart gameplay element.

1) fast travel - double clicking on a room exit and get instantly teleported.
2) hint system - shows all interactive objects in the room that will be important, like exits or items etc.
3) action menu/action coin - already standart in wintermute. But still very interesting, i think this gameplay element was invented by LucasArts in CMI and is the final result of reducing its verbal system to its basis. Sierra and other companies already where using a similar system but it was a very annoying "click right for the next verb", where you had to scroll through all minus one button if you are unlucky. LucasArts fixed this issue with its action coin and im a little bit disappointed that this feature is still missing in most commercial games.

Then i was thinking about gameplay elements that are still a typical problem with adventure games. One thing is the annoying standart sentence "i cant do this!"
Games like A Vampyre Story try to solve this with funny dialogs. So instead of getting "i cant do this!" or "that does not make sense!" you get the sentence "Oh hello little door. How are you doing?".
That is ok for a game that uses humor but it has some disadvantages:
1) it requires much work to write for every object a funny phrase
2) while maybe funny it does not resolve the problem that it is still a "you cant do this"-answer
3) funny dialog does not work in serious games like horror or mystery adventures.

So i was looking for a way to reduce this. While i dont know how you could solve this problem for items, at least i came up with an idea to prevent the player from stupid interactions:
simply deactivate the button in the action coin.

It should be obvious that the player cant talk to his desk or chair. So why should the player get the option to talk with it? By deactivating unused interactions you not only reduce frustration for the gamer itself, you also dont have to think about an unique answer why you cant talk to a ventilation system or use a street sign.

So i wanted to ask if someone had a similar or maybe completely other ideas how to advance the point&click adventure gameplay interaction?

2
Technical forum / strange behaviour if the Sleep function
« on: February 10, 2009, 12:15:15 PM »
hi, i discovered yesterday a strange behaviour of my sleep function.
Till yesterday, this code worked correctly:

Code: [Select]
method ShowPort(PortraitName, Place, Slide)
{
if (loc_Portrait!=null)
{
Game.UnloadObject(loc_Portrait);
}
if ((Place != 1) && (Place != 2) && (Place != 3))
{
Place = 2;
}
loc_Portrait = Game.LoadWindow("windows\Portrait.window");
loc_Picture = loc_Portrait.GetControl("Picture");
loc_Picture.Text = "IM ACTIVE!";
loc_Picture.SetImage(PortraitName);
NO_CONTROL = true;
if (Slide == true)
{
if (Place == 1)
{
for (var j=0; j<128; j=j+1)
{
loc_Portrait.SkipTo(-256+(4*j), 768);
Sleep(2);
}
}
if (Place == 2)
{
loc_Portrait.SkipTo(512, 768);
}
if (Place == 3)
{
for (var i=0; i<128; i=i+1)
{
loc_Portrait.SkipTo(1290-(4*i), 768);
Sleep(2);
}
}
}
NO_CONTROL = false;
}

But since yesterday my sleep function doesn't work correct anymore. As you maybe see, this script changes the position of the window every 2 milliseconds 128 times. strangely this worked till yesterday but now it looks like i can enter any low sleep values but it always takes arround 2-3 seconds for this loop to complete. using larger values are working fine, for example 1000ms but it looks like it doesnt matter if i say Sleep(2) or Sleep(15).....  :-\

[EDIT:] Strangly enough, after i posted it, i tryed it a second time and now it works again. But then i closed the Wintermute Project Manager, and now the problem returned ???

Pages: [1]

Page created in 0.08 seconds with 22 queries.