I'm going to guess here, because I only see 1 obvious error.
(You've typo'd
imag as
imagen in a couple of places).
Firstly,
class and
screen only create frameworks to be used later.
My guess is that your
label Inventario: appears exactly as you've written it above. Somewhere at the top of your script and before
label start:. Unless you have a
jump Inventario as part of your active game code, it will never be executed.
I'm guessing the original author of the inventory code intended it more as a "this code goes in the main game script" rather than a literal label called "Inventario".
Similarly,
$ inventory = Inventory() is something I'd normally only expect to be executed once. It is effectively create a variable
inventory based upon
class Inventory(). The line after it appears to be creating a new item, for the game to use later - I'd expect a lot of these "items" beyond just this one.
Then whilst I'd expect both the inventory setup and loading the items to only take place once - the
call screen Invty() is something I'd expect to happen a lot more often, and definitely as part of the main code after
label start:.
Before I reply what I think the answer might be... just a bit of background about variable creation.
define creates a variable that is not saved as part of the save game files. Their values are not expected to change while the game is running and the RenPy author has strongly suggested bad things can and will happen if you ignore this advice.
default creates a variable that is saved as part of the save game files. Loading a save file, will overwrite any values currently stored by the game with the values that are part of the save file.
define is therefore used for static variables and
default is used for player variables.
Some older code (before
default was added to RenPy) used to initialize variables during the
init: processes. 99% of the time, it's just old code that has been copy/pasted by developers who didn't know any better.
In the case of your inventory and items, I would expect "items" to be static variables and "Inventory" to be a player controlled variable.
The only exception I can imagine, would be if you wanted to alter the cost of items while the game is running. It would create headaches, because it would require the item list to be saved too - and therefore loading old save files might effectively remove items from the game.
So based on that background... I think what you want is:
Python:
init python:
# class
class item():
def __init__(self, name, imag="", cost=0):
self.name = name
self.imag = imag
self.cost = cost
class Inventory():
def __init__(self, money=10):
self.money = money
self.items = []
def add(self, item):
self.items.append(item)
def drop(self, item):
self.items.remove(item)
def buy(self, item):
if self.money >= item.cost:
self.items.append(item)
self.money -= item.cost
# screen
screen Invty:
add "fondos/Invt.png"
modal True
hbox :
grid 5 4:
for item in Inventory:
imagebutton auto "icons/Moc_ico_%s.png" action [Hide("Invty"), Return(None)]
default inventory = Inventory()
define obj1 = item("objeto1", imag="icon/obj/icoTest.png", cost=0)
define obj2 = item("objeto2", "icon/obj/icoTest.png", 0) # technically you don't need the names,
# since the parameters are already in the correct order.
define obj3 = item("objeto3", "icon/obj/icoTest.png", 0)
define obj4 = item("objeto4", "icon/obj/icoTest.png", 0)
#etc
label start:
scene black with fade
"*** START ***"
call screen Invty # just for testing purposes until it's used for "real" later. (Should currently be empty)
$ inventory.add (obj1)
$ inventory.add (obj2)
call screen Invty # more testing... shows 2 items now.
# the rest of the game...
I've not tested this code, and it's only a guess on my part that you've not got a
jump Inventario anywhere.
As a side note, it's usual to only use Capitialization for class names and lowercase almost everywhere else. I've not changed anything here, because (a) it will still work and (b) I didn't want to introduce any new typos. But if you're still at the very early stages, it might be a bad habit you can break now rather than causing problems later. That's the screen names, labels, even image filenames.
