43 replies to this topic

[talonstart]

First step im working on is, setting up a command to open a object bag and closing it with the same key.

Any help would be great.

I have gotten this to open it.. i have tried a true false statement.. as well. but seems to ether work once and not open again
or stay open. .

if (keyboard_check(ord('B')))
{
instance_create(x,y,obj_bag)
}

Any proper code would be greate. Thanks!

[Jack Indie Box]

well i dont quite know what you mean. but ill assume you just want to change the state of an object, as i dont know what the bag is or for.

first improvement, eithere use keyboard_check_pressed or use the built in event for key pressed (which would be less versitile);

if(keyboard_check_pressed(ord('B')))
{
obj_bag.state=obj_bag.state*-1;//this will toggle between 1 and -1 which you then can use in the obj to drag the relevent image and run specifc code in either state
}

just make sure you set the original state to 1 or -1 in the bag's create event.

if you give better details i can help more

[talonstart]

sure sure...

well lets see.. (its just and obj_bag) .. so far, nothings in it, just creating the object to appear on the screen.
once the object appears, i just want to press b again, and object disappears. removes itself from the screen.. kinda like
and rpg inventory open close.

might need a little more example.

Edited by talonstart, 03 May 2012 - 12:51 PM.

[talonstart]

now i have succeeded in making it like this where the obj is always in room but invisible.

//Menu Controll

if keyboard_check_pressed(ord('B')) && obj_bag.visible = false
{
obj_bag.visible = true
}
else
if keyboard_check_pressed(ord('B')) && obj_bag.visible = true
{
obj_bag.visible = false
}

This works.. but donno how well that will do. in another room if i transfered.. .. so trying to figure best option here

[Jack Indie Box]

if its an inventory i wouldnt do it as a separate object, put it as a state in your object or controller obj.

but if you did it your way and wanted it to completely go away use with(obj_bag){instance_destroy();}

if you do it in your player that means you can easily make it so you cant walk around and stuff when the inventory is open or other things, like change what the controls do.

just only draw the object if the bag is visible (use if statement), if you didnt know, if you draw in a draw event the default drawing turns off for your object (eg. player will disapear if you were just using default drawing of it's sprite) to turn it back on use draw_self(); asuming you have a modern game maker

[talonstart]

i have pro...

Think you can conjure up me an example.. not having a good day today in mind thoughts.. ?

[Jack Indie Box]

i currently only have 8.1 installed so you wouldnt be able to open the file.

but anyways i would need to know nearly exactly what you wanted to achieve, its quite an easy thing, to do an inventory but there are many types

[talonstart]

im 8.1 .. I have 8 / 8.1 and / studio beta

You can do it..

Just simply looking for what you mean state... a simple press button on off type or deal.. so i can understand it more by feel

[talonstart]

im not creating any special game, but upping my knowledge.
i have never made inventory, so im taking my time step by step ..

i have read some tutorials.. but they make me confused.. soo i do one part at a time..
my goal is, a diablo style menu system.. so i can pick up an item, it places it in inventory, from inventoy i can equip it to an armor place, armor shows, stats +, and unequiped goes back to inventory, stats de-gen.

thats my goal in this lesson...

[Jack Indie Box]

ok well by state i just used the "offical" name for what you should be trying to achieve. most modern games are programmed using state machines, a state machine is basically a few states an object or game could be in. ie. for game, could be in menu-room_start-running-changing_room-loose_state-game_over

for they could be anything. and when you were in each state(just a variable named something like state, which stores its current state) would run code specific to that state eg. you dont need to have the same code acessible on a menu to what you need when the gameplay is actually running. so you put 2 different sets of codes inside the "if" or "switch" statement


so for our player object we would have:

//*create event*
state="start";

//put your other create code here


//*step event*
switch (state)
{
    case "start": {
    //put any start up code for the object
    }; break;
    case "running": {
    //put all normal gameplay code
    }; break;
    case "bag": {
    //put bag code
    }; break;
    case "dead": {
    //put any dead code
    }; break;
    default: //put some backup code if your switch statement doesnt work;
}


//*draw event*
switch (state)
{
    case "start": {
    //draw start up code
    }; break;
    case "running": {
    //draw player gameplay
    }; break;
    case "bag": {
    //draw inventory
    }; break;
    case "dead": {
    //draw death state
    }; break;
    default: //put some backup code if your switch statement doesnt work;
}

and then when you press B you just need to toggle the state to and from bag

you may want to use a state switch statement on other code areas like keyboard events or anything else

if you really need a full example i may have the time


ps. sorry if any of my code layout is wrong i just mocked it up

Edited by Jack Indie Box, 03 May 2012 - 01:39 PM.

[talonstart]

the code making some sense, but a full example would be nice, so i can see the work that is implying.. ill then reference it so i remember.
while you do that ima test it out.


so far this is my code.. maybe you can correct it properly for what im doing.

Player Create

//STATS
max_hp = 100
myhp = 100
def = 50

//gold
gold = 100

//Equipment

//Warn Plate
plateA = false
plateon = 0

player steps
// i understand im using the old way, i will change it when necessary

if keyboard_check(ord('A')) x-=2.8
if keyboard_check(ord('D')) x+=2.8
if keyboard_check(ord('W')) y-=2.8
if keyboard_check(ord('S')) y+=2.8
else

if (keyboard_check(ord('W')))
{
sprite_index = walksp_up
}
if (keyboard_check(ord('A')))
{
sprite_index = walksp_left
}
if (keyboard_check(ord('D')))
{
sprite_index = walksp_right
}
if (keyboard_check(ord('S')))
{
sprite_index = walksp_down
}
else
if keyboard_check(ord('W')) && keyboard_check(ord('D'))
{
sprite_index = walksp_upright
}

if keyboard_check(ord('W')) && keyboard_check(ord('A'))
{
sprite_index = walksp_upleft
}

if keyboard_check(ord('S')) && keyboard_check(ord('A'))
{
sprite_index = walksp_downleft
}

if keyboard_check(ord('S')) && keyboard_check(ord('D'))
{
sprite_index = walksp_downright
}


if keyboard_check_released(ord('W'))
{
sprite_index = standsp_1
}
if keyboard_check_released(ord('A'))
{
sprite_index = standsp_1
}
if keyboard_check_released(ord('D'))
{
sprite_index = standsp_1
}
if keyboard_check_released(ord('S'))
{
sprite_index = standsp_1
}


//Menu Controll : dis regard this... was my own test.

if keyboard_check_pressed(ord('B')) && obj_bag.visible = false
{
obj_bag.visible = true
}
else
if keyboard_check_pressed(ord('B')) && obj_bag.visible = true
{
obj_bag.visible = false
}

draw event

draw_self()

//Equipment
//worn metal plate
if object0.plateA = true
{
draw_sprite(spr_armor,0,object0.x,object0.y)
}

if object0.plateA = true && object0.plateon = 0
{
object0.def += 5
object0.plateon = 1
}

gmk8.1 file maybe you can re-set it properly to what your saying. for less work
Download rpg testing - inventory window.gm81 from Host-A

Edited by talonstart, 03 May 2012 - 01:51 PM.

[Jack Indie Box]

im sure you can implement this yourself, if you get stuck i will help but you really dont need an example of how to create a state, i mocked up a switch statement.

just swap references of obj_bag.visible for the variable state

then instead of checking if its true or false or changing it to true or false, set it to "running" or "bag" and check for those values.

also in your file there is no controller object. its a good idea to have one to run code that is not specific to the player. like i said also a global game state in the controller object is a good idea so you know if its gameplay, loose state, highscore.......

you wont learn much if i write it all for you. if you dont understand state machines(im not the best explainer) just google it. there are a few types but it is pretty industry standard

[talonstart]

dont need you to write it.. I got good concept. just my mind been on nuclear fallout, for awhile, and desided to break and learn a few new things.. that im not use to doing
..

Obj_controller.. is possible.. i know what you mean there. I usually run a controller in one room upon load then switch out to the main room...
ima attempt to create like what you said.. and read more.. of course ..

[talonstart]

switch (state)
{
    case "start": {
    //put any start up code for the object
    }; break;
    case "running": {
    //put all normal gameplay code
    }; break;
    case "bag": {
    //put bag code
    }; break;
    case "dead": {
    //put any dead code
    }; break;
    default: //put some backup code if your switch statement doesnt work;
}

Care to break this down for me a bit more.. i see the comments..
but example what would i want for a startup code... or running... i see bag what would i or u do for a bag code (would that be the keyboard check).. case dead.. im little lost..

maybe if you put like (an example into that).. thats probably all i need to understand.


So far i created a obj_controller.

i created in a create event state = "start"

im in my steps..

now im trying to break down what your doing

[Jack Indie Box]

switch (state)

{

    case "start": {

    //this state for player is only needed if you want to run something at the start of the player being made, other than the create event of the object. so you probs dont need

    }; break;

    case "running": {

    //i named it running but could be called normalgameplay or anyhting. put all step event code that you want to happen when the player is in this state. ie. when he is allive but not using inventory or interacting with a npc or something. you can add more states just by adding another case "something":{ and the rest of the code};break;

    }; break;

    case "bag": {

    //if you want the player to select items in the bad or something pu the code for it here, this state also will mean the player wont run around whilst hes dealing with his inventory unless YOU want him to.

    }; break;

    case "dead": {

    //put any code for when hes dead like a death sprite or respawning or whateva, it varies from game to game

    }; break;

    default: //put some backup code if your switch statement doesnt work;

}

[talonstart]

Im reading upon states... gah what a head ache..

is there a way to destroy_instance from another object.. . gml..

like obj_bag.instance_destroy()...

that be a use full thing for me..

I figured i can create scripts

bag()

im starting to figure it out slowly.. just need to find a good tutorial on how its working, Most of the tuts i run into is just over crowed with crap i dont wanna learn.

[Jack Indie Box]

with(object){instance_destroy();}

[talonstart]

gah im still so lost on this...

i checked out some other tuts of states.. but im not having any luck with this..

[Jack Indie Box]

i think your thinking too hard on this, its really simple


state machines just split up your code automatically(based on the state) allowing only relevant code for that state to run.

just implement that switch statement in everywhere where you run code specific for states. and you can switch states when needed by changing the variable state's value to what state you want it to be. which could be due to a key press(like the bag example) a collision, after an amount of time or any other interaction.

i cant help you with the theory any more nor am i going to code it all for you. but is one section of your code doesnt work ill help.

sorry if this isnt what you want

[talonstart]

its what i need.. my brain is just farting..

just trying to figure out how its suppose to work...

like for example.. (where would i put the keyboard command) , and how will it close the bag....

The code you wrote makes sense, just i havnt ever done this before, so im trying to peice it together.