Messages

Ok doubtless this is just me being thick but I have made 0 progress with this game so far.

I have:

Spoiler

A screwdriver, a fuse and a passport

[close]

Otherwise I have acheived nothing!

Any hints?

Entries Yay!

Well, it's been another truly epic competition and I therefore declare the winner to be Ponch!

As it was a real journey and something that all of us will want to tell our grandchildren about, trophies are in the form of "I Was There!" T-Shirts.

1st place: Ponch


2nd place: Frito Master


3rd place: Anyone who witnessed this legendary colouring ball!


Thanks all and I look forward to seeing your new colouring ball Ponch!

OK, 1 day to go and no entries!

If anyone wants to enter you can pretty much win by doing anything at all in 2 seconds!

Trophies on hold then and I will try and come up with a better idea next time unless anyone is checking in with a lastminute.com entry.

Thanks for the advice and especially the paintover. It's amazing how such seemingly simple things make all the difference!

I will have another crack at this and see where I get to.

This is an unfinished background from an old project I was working on a couple of years ago before 2 knackered hard drives coming along at the same time meant I lost almost all of the work I had done.



However, having recently discovered this background (and you can blame Ponch for motivating me to get stuck back in to game making!) the thought occurs that I could use it as the basis for a background in another game I am knee deep in planning. The trouble is that now I look at it, the composition and perspective seem no good, especially the pavement. Clearly, if this is the case I may as well start from scratch rather than try to amend and complete the current version.

However, I am really no artist and even the above took me absolutely ages, as I tried to use detail to cover up lack of ability!

The question therefore is, is the background easily fixable? The grassy/playground bit would need amending/replacing anyway for the new game, but the basic shape of the background would be useful if it can easily be fixed up.

As you can probably tell I don't really know what i'm talking about art-wise(!) so any advice or tips would be welcome.

I had an unfortunate incident a good while ago with knackered hard drives on my laptop and desktop at the same time which meant I lost about 3 projects in varying stages of progress, one of which was potentially good enough to see the light of day. 

I have tried to begin one again and spent a very long time planning another game which could be good (at least by my standards!) but lack of time and anything resembling artistic talent mean it is very slow going.

Maybe one day...

...and if you've ever had a crappy office job take a look at Colin Simpson Leaves Employment. 

Couldn't possibly recommend that one but I will second the Barn Runnarz all day long as essential to anyone's AGS collection.

Inventory Items.

We're all used to combining them with one or more others to make something completely ridiculous which would never work in solving a puzzle! However, this is the land of adventure games and therefore the most tenuous combinations will be the only way to overcome the ridiculous obstacle of choice.

However, this one here really takes the biscuit!



Rules:

1. You must come up with a combination of 2 or more unrelated inventory items which have been somehow joined together to make a combined item which will solve a puzzle in a ridiculous way. Bonus points if you describe the puzzle and use of the item!
2. No limit on number of colours.
3. You may rotate and/or resize.
4. Have fun! (This is mandatory and we have ways of telling!).

Brilliant!

Looking forward to it and clearing space in my gaming schedule accordingly!

Yaay thanks all!

Sorry to hear things are tough at the moment Nicky, don't worry about trophies etc. Taking part + a smilie from the smilie queen tabata are their own reward!

I will try and get the next one started tonight.

What would happen if girls had apostrophes instead of periods?

They would be possessive and prone to contractions.

Ba-doom-tish!

Bump.

Ah! Always so simple when I see it, thanks very much CW.

I think my main trouble is that I haven't done anywhere near enough programming to think like a programmer sometimes.

I have a struct which is declared like this:

Code: AGS

struct pmoves{
  int value;
};

pmoves pmove[25];

(There is more of it, but this is the relevant bit for this question)

In the game each of pmove[1] - pmove[24] has a value of between 0-20, which is calculated on a number of factors within the game which change very frequently.

What I want is a function which will tell me which pmove has the highest value at any time. [in the event that there is more than one that shares the highest value, I just need it to return any one of them].

So far I have:

Code: AGS

function movechooser(){
  chosenmove = 0;
  choosemove = 1;
  while (choosemove <25){
    if (pmove[choosemove].value==1){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==2){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==3){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==4){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==5){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==6){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==7){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==8){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==9){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==10){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==11){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==12){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==13){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==14){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==15){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==16){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==17){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==18){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==19){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  choosemove=1;
  while (choosemove <25){
    if (pmove[choosemove].value==20){
      chosenmove=choosemove;
      choosemove=25;
    }
    choosemove++;
  }
  Display ("I have chosen move %d", chosenmove);
}

The logic (at least in my mind!) behind the above:

• Choosemove is a variable to allow me to sort through the 24 options.
  
• Chosenmove is a variable that I want to set to show me which of the pmove has the highest (or one of the highest) values.
  
• Therefore first I cycle through all pmove.value and as soon as I get to the first one with a value of 1 chosenmove is set to that pmove. This is then repeated for a value of 2 and so on all the way up until 20. Therefore chosenmove ends up being set to the first of the pmove with the highest value.
  

Whilst I haven’t finished testing it properly (it is difficult with respect to where it is in the game and is conditional on one or two other bits that aren't quite working!), I can’t believe this is anything like the best way to do it but I’m having a bit of a mental meltdown at the moment and could do with some pointers or help!

Besides my stupid idea of using 2 variables that look almost identical(!) how can I do this better?

Sometimes these just jump out at you!



No peace here guys.

Or no flying or birds or something!

Apple are even worse when it comes to audiobooks.

I recently stuck itunes on my laptop and authorised it as a second device. I downloaded my purchased music fine but when it came to audiobooks (of which I have a couple) it wouldn't let me. I complained, assuming it was an error, but they replied saying that you cannot download audiobooks more than once and therefore they would not put them back on my purchase history. As a "one off" they actually did let me re-download them onto the second device (and I expect they would let anyone who complains) but seriously, If my 1st device dies or I upgrade it at all I cannot re-download what I have already bought?

I have no love for Apple anyway and I think my new Galaxy S3 and a podcatcher app will be replacing my old ipod shortly.

Mods be chasin' this thread...



...but they can't catch it.

Specifically, every man has something we may call "internal circle" - a range of people he feels comfortable with: friends, parents (not always ).
When the person accomplishes certain job for the first time he definitely becomes excited, we all know this. When I made my first "game" with AGS I felt very excited too, although I was, I think, 25 or 26 years old already and had some experience in game making (including 3d games). What have made me NOT post my game here? I did had excitement - right, but it was that none of people here were my friends, and I did not feel like I can show them something that was definitely low quality without looking like an idiot.

That's interesting. I think for some people it can work the other way round. If you do produce something truly terrible and show it to your "real" friends then you possibly stand to lose face with them and maybe face some ridicule. If you share it with a load of "randomz" on teh interwebs then who cares? No one really knows you, and if it gets panned you can simply never visit the site again and ignore the embarassment! (I suppose the waters are muddied if you are well known and friendly with others on the forums).

Taking myself as an example, the only game I ever released was, perhaps not appalling, but certainly not that good. I was also in my late 20's at the time. I have been happy to have it released on the internet and downloaded by whoever comes across it, but have mentioned it to very few people in real life. I'm not really ashamed of it or anything but not that many of my real life friends play adventure games or have an interest in "retro style" games. Here is a place however where the one thing we all share (more or less) is a love of adventure games (whether creating or playing) and so hopefullty at least some people were able to enjoy my game at some level. Therefore somehow it is easier to release here and all those who thought it was rubbish have had the kindness simply not to mention it (for the most part!) or just gave up after 2 mins and forgot about it for ever.

If I show it to my "inner circle" they have to comment really, and as they know me it's more of a big thing. I think being told by them it was rubbish would be somehow worse than internet randoms.

Just a quick side question on your code Khris, if I may.

I follow it fine and it seems an elegant solution to the problem to my inexperienced eyes. If I had tried to do this (and been clever enough to work out the same solution) I would probably have done

Code: AGS

int border = 10;

rather than #define. Not in any way saying that would be better, but I wonder what the benefit of #define is? Is it simply better practice as the value of border will never change and therefore does not need to be a "variable" as such? Or is there something i'm missing?