The file you define the screen function (if it can be called a function) on doesn't really matter, it can be done on screens.rpy or in idontevenknow.rpy
Whenever you want something clickable, you resort to imagebuttons. First, you need to define your screen, in screens.rpy for example, by doing something like:
Code:
screen houseIcons(displayBathroom,displayLivingroom):
if(displayBathroom):
imagebutton idle "bathroomicon.png" action Jump("labelwhereyouwanttojumpto")
if(displayLivingroom):
...
where displayBathroom/displayLivingroom are booleans (meaning they can be True or False)
You don't have to include these variables and if statements, it's just so you can have full control when you use it on your main script. The function has been created, and now you just need to show that screen by doing:
Code:
show screen houseIcons(True,False)
This is why using these variables (displayBathroom and displayLivingroom) can be a good idea: let's say the user is already in the living room. Then you can simply show screen houseIcons(True,False), so he's only able to see the bathroom icon. If he was in the bathroom, you'd do (False,True) and he'd only be able to see the living room icon, and you wouldn't need to create a separate screen function for each.
Anyway, I haven't tested the code and I haven't touched ren'py in a week or so, so I might have made a mistake or two. But yeah, that's the general idea. Hope it helped!