Messages

Sorry for the necro, as you know I've coded a plugin yay, I'd like to share it's code - some of it is kind of hard coded (I can't seem to figure out a way not to have it so), so I'm not sure it's gonna be useful to others - to make it portable, is there a way I can ensure that on my own? Again, I don't mind sharing it at all.

Somewhere between blurry one and bottom right

It's that time of the year again, and I've been looking to that post from Gurok, about the tune competition and I think we should bring it back. Make it monthly deadlines. So 12 runs of it. Inspiration is very weird and themes are a bit hard to follow if they are strict. So I'm suggesting we go very abstract and open-ended. We can pick 8 feelings (since those are the months left) and make these as the themes. That way anyone that can compose isn't restricted by genres or minutes or anything like that.

My suggestion is to start with "LOVE" as first theme. Love has many expressions and that doesn't tie anyone to any genre in any way. Thoughts? Is anyone really interested in something like this?

This has to be the first year i forget mods birthday. I FEEL LIKE SUCH A FUCKHEAD. Happy belated, m0ds <3

Alright, so, if anyone wants to take my spot, please do, I don't have an idea for a movie right now, so, plz take my spot by force and post an image.

Konstantine, or however that keanu reeves movie is written.

Replied to put this on the top.

[I see room_a(), room_b() etc. in the room script. What is that? How does it work?]

I see room_a(), room_b() etc. in the room script. What is that? How does it work?

These are room interaction event functions. The engine calls them when there is some room interaction running. They have the same meaning as global event functions like game_start(), repeatedly_execute(), interface_click() etc.

Room interactions:

Walk off left
occurs when the player character walks off the left edge of the screen.
Walk off right
occurs when the player walks off the right edge of the screen.
Walk off bottom
occurs when the player character walks off the bottom edge of the screen.
Walk off top
occurs when the player character walks off the top edge of the screen.
First time enters room
occurs the first time the player enters the room. This event occurs AFTER the screen has faded in, so it allows you to display a message describing the scene.
Player enters room (before fadein)
occurs just after the room is loaded into memory. This event occurs every time the player enters the screen, and it happens BEFORE the screen has faded in, which allows you to change object graphics and do other things to the screen which the player won't notice.
NOTE: This event is ONLY meant for adjusting things such as object and character placement. Do NOT use this event for any sort of automated intro to the room - use the "Enters Room After Fade In" event for that instead.
Repeatedly execute (for this room)
occurs repeatedly on every interpreter cycle. The normal game speed is 40 cycles per second, so this event occurs about every 25 milliseconds.
Player enters room (after fadein)
occurs every time the player enters the room, AFTER the screen has faded-in. Suitable for displaying text descriptions and so on, that you want the player to see.
Player leaves room
occurs when the player leaves the screen, just before the screen fades out.

How it works:

When you goto the room interaction editor and add a new interaction then choose RunScript option AGS adds appropriate function for the current room so you could place the code in to decide what you want to be happen when the interaction is running. You may notice the comment line inside of each event function telling what interaction the function is for.

Example:

1. Go to interaction editor
2. Choose interaction: Player enters room (after fadein)
3. Set RunScript option for this interaction
4.
   function room_a() {
   // script for room: Player enters room (after fadein)
     player.Animate(...);
     player.Walk(100, 200, eBlock);
     ...
     ...
     etc.
   }

So now each time the player has entered the room (after fadein) AGS will animate the player character and move him to the specified co-ordinates.

A Word of warning:

You should never place or delete these functions manually. Instead goto the interaction editor and remove appropriate interaction (AGS takes care itself on deleting such functions).
Why is it so? Because when you add new interaction AGS adds an event function as well and links it with the added interaction.
That means two things:
1. If you open script editor (room) and just place room_*() functions manually AGS will not be able to call them unless the appropriate interaction has been specified first. This is why you can't just copy the whole script code from one room and paste it into the new one. You should create interactions first.
2. If someone posted a script like this:
function room_a() {
  cGuy.Walk(...);
  ...
  ...
  etc.
}

you shouldn't just grab & paste it into the room. Even if you have room_a() function in yours script. The reason it should be avoided is that the event function name is NOT connected with the interaction equally for all rooms but depends on on the order the interactions have been added.
What I mean is this:

Interaction editor > Add Interaction > Room: Player enters room (after fadein); RunScript;
Result: function room_a() has been added.

Interaction editor > Add Interaction > Room: Player enters room (before fadein); RunScript;
Result: function room_b() has been added.

Interaction editor > Add Interaction > Room: Player leaves screen; RunScript;
Result: function room_c() has been added.

So in the room script we have:

//room script
function room_a() {
// script for room: Player enters room (after fadein)
}

function room_b() {
// script for room: Player enters room (before fadein)
}

function room_c() {
// script for room: Player leaves room
}

...but changing the order interactions would be added in:

Interaction editor > Add Interaction > Room: Player leaves room; RunScript;
Result: function room_a() has been added.

Interaction editor > Add Interaction > Room: Player enters room (after fadein); RunScript;
Result: function room_b() has been added.

Interaction editor > Add Interaction > Room: Player enters room (before fadein); RunScript;
Result: function room_c() has been added.

... we'll get in the room script:

//room script
function room_a() {
// script for room: Player leaves room
}

function room_b() {
// script for room: Player enters room (after fadein)
}

function room_c() {
// script for room: Player enters room (before fadein)
}

See the difference? The functions have other names.

Btw, there are not only room interactions but hotspot, objects etc. so seeing something like function hospot1_a() {} is also possible.

-

Oops, a bit long post. hope it's not confusing and helps you. If you have any related questions just ask.

-Cheers




What exactly are arrays and structs, and how do you define/use them?

As of AGS v2.71 arrays and structs are officially supported, and are also documented in the manual:
  Manual -> Scripting -> Script language keywords -> Arrays / struct

With arrays, you can store several values in one variable, so to speak.
So instead of doing

Code: ags

// main global script

int weapon1_cost; // define variables available from all functions in the global script
int weapon2_cost;
int weapon3_cost;

function game_start {

  weapon1_cost = 60;
  weapon2_cost = 20;
  weapon3_cost = 40;

}

export weapon1_cost; // export variables to make them available in room scripts
export weapon2_cost;
export weapon3_cost;

Code: ags

// main script header

import int weapon1_cost; // import global script variables to make them available in room scripts
import int weapon2_cost;
import int weapon3_cost;

you can do

Code: ags

// main global script

int weapon_cost[3]; // define array with a dimension/size of 3

function game_start {

  weapon_cost[0] = 60;
  weapon_cost[1] = 20;
  weapon_cost[2] = 40;

}

export weapon_cost; // export array to make it available in room scripts

Code: ags

// main script header

import int weapon_cost[3]; // import array to make it available in room scripts

Note that the array's index (the number by which you access it) starts at 0 and ends at arraysize - 1.
In the past, accessing an array outside these bounds could cause weird things to happen. Although AGS has been improved with better array bounds checking since then, you should be careful to avoid any problems.

Now, with structs, you can do this (AGS v2.71 and up, see below for older versions):

Code: ags

// main global script

myWeaponStruct weapon1; // make variables from the struct defined in the script header (see below)
myWeaponStruct weapon2;
myWeaponStruct weapon3;

function game_start {

  weapon1.cost = 60;
  weapon1.power = 30;
  weapon1.description = "Mace";

  weapon2.cost = 20;
  weapon2.power = 10;
  weapon2.description = "Dagger";

  weapon3.cost = 40;
  weapon3.power = 20;
  weapon3.description = "Sword";

}

export weapon1; // export variables to make them available in room scripts
export weapon2;
export weapon3;

Code: ags

// main script header

struct myWeaponStruct {
  int cost;
  int power;
  String description; // Note: "String", not "string"
};

import myWeaponStruct weapon1; // import variables to make them available in room scripts
import myWeaponStruct weapon2;
import myWeaponStruct weapon3;

You can also combine structs and arrays like this:

Code: ags

// main global script

myWeaponStruct weapons[3];

function game_start {

  weapons[0].cost = 60;
  weapons[0].power = 30;
  weapons[0].description = "Mace";

  weapons[1].cost = 20;
  weapons[1].power = 10;
  weapons[1].description = "Dagger";

  weapons[2].cost = 40;
  weapons[2].power = 20;
  weapons[2].description = "Sword";

}

export weapons;

Code: ags

// main script header

struct myWeaponStruct {
  int cost;
  int power;
  String description;
};

import myWeaponStruct weapons[3];

For AGS v2.70 and below:

You can't make arrays from string variables and the new String type doesn't exist in AGS v2.70 and below.
Here's a workaround to do the above in older AGS versions:

Code: ags

// main global script

myWeaponStruct weapon1; // make variables from the struct defined in the script header (see below)
myWeaponStruct weapon2;
myWeaponStruct weapon3;

function game_start {

  weapon1.cost = 60;
  weapon1.power = 30;
  StrCopy(weapon1.description, "Mace");

  weapon2.cost = 20;
  weapon2.power = 10;
  StrCopy(weapon2.description, "Dagger");

  weapon3.cost = 40;
  weapon3.power = 20;
  StrCopy(weapon3.description, "Sword");

}

export weapon1; // export variables to make them available in room scripts
export weapon2;
export weapon3;

Code: ags

// main script header

struct myWeaponStruct {
  int cost;
  int power;
  char description[200]; // instead of "string description;"
};

import myWeaponStruct weapon1; // import variables to make them available in room scripts
import myWeaponStruct weapon2;
import myWeaponStruct weapon3;

You can also combine structs and arrays like this:

Code: ags

// main global script

myWeaponStruct weapons[3];

function game_start {

  weapons[0].cost = 60;
  weapons[0].power = 30;
  StrCopy(weapons[0].description, "Mace");

  weapons[1].cost = 20;
  weapons[1].power = 10;
  StrCopy(weapons[1].description, "Dagger");

  weapons[2].cost = 40;
  weapons[2].power = 20;
  StrCopy(weapons[2].description, "Sword");

}

export weapons;

Code: ags

// main script header

struct myWeaponStruct {
  int cost;
  int power;
  char description[200];
};

import myWeaponStruct weapons[3];

Edit:
- Updated with AGS v2.71's String type
- Changed "item" to "weapon" to avoid confusion with inventory items

@yamipanda: Yep, well, perhaps few of your friends would get you, but i was like "OH A BROKEN SWORD T-SHIRT!" ^_^

Unfolding Spider - one of my favourite games EVER!:)

There's a great fellow!!!!


Alright, cat, if anyone else doesn't mind I will write one in a few days, perhaps Grim also wants to write one, we share the same love for this, i recall.

http://www.adventuregamestudio.co.uk/site/games/game/1481/

The unfolding spider, if not yet appearing in the pick of the month. Willing to write a teaser as well.

Nightfable, i can tell you that you are totally not a noob. You were a lot active when i first joined the forum, so it's always nice to see you, even though you are on and off these past 7-8 years.

Particle system manager by jerakeen does those things. Ideally, just use what I used for Dakota, and all my other games, hardcoded rain.

You guys :DDDDDDDDDDDDD

Thankies!

Happy birthday m0ds, ill always love you for the McCarthy Ronirods.

Okay, here follows a teaser if whoever is in charge and Ponch of course approves of it.

Initially a parody of Blade Runner, as it progresses it forms into something else entirely. Ponch released a few episodic short games, before releasing Barn Runner: Forever Friday Part 1, showing that the universe was already well-fleshed. Words and sentiments, can't describe the craftsmanship that Ponch will always deny, if ever attributed concerning the story elements resolving around the Barn Runner Universe. As Pythagoras once said "The beginning is half of the whole", and this holds true for the Armageddon Eclair. Sci-fi dystopian neo-noir 80s retro good-cop vs bad-cop boogie dance anti-hero SAGA; or Barn Runner.

Fourthed. I mean Barn Runner wins all. May I write the teaser for it? It would be of greatest honor.

[Primordia, Cat Lady and Downfall]

Hello,

My name is James Spanos, but everyone around here calls me Dualnames. Anyhow, I've worked on many projects mostly excelling in coding,
including Primordia


, Cat Lady and Downfall, creating innovative ways for you to present your story and improve your game design.
Besides AGS I'm also working on several other engines, so if what you want is outside AGS, don't hesitate.

If you want to work on something serious and with prospect, do contact me either via Private Message or via E-mail (ledzepforever@gmail.com

I'm suggesting Educating Adventures of Girl & Rabbit. If seconded I can write a short teaser for it.

And.... http://duals.agser.me/Modules/FOG_v1.0.rar

Sorry, I've missed to update this one. Thanks for pointing it out.