It will be long, because there's not much right.
Firstly,
You must be registered to see the links
is probably not what you should use here.
It change Ren'Py's state, from "in game" to "in main menu". While it's not technically speaking a problem, it's not recommended to use it for in game features ; what your stats menu and relation screens are.
Secondly,
You must be registered to see the links
is depreciated since years.
You should use
You must be registered to see the links
instead. It would give you more flexibility.
Thirdly, the
text statement should not be inside the
imagemap.
While it accept it, what is surprising,
imagemap should limits to its effective children. The
text statements should be in a regular box block, like
vbox,
hbox or
frame by example.
Fourthly, it's not really convenient, in terms of User Interface design, to have this "click then return" pattern.
You should design your "relationship" screen to include the stats. Then, the player just have to click on the girls icon to see her stats, then on another icon to see the stats for another girl, without having to change screen.
Fifthly, you exit the "relationship" screen, returning to the game flow.
This is really confusing since it initially come from "stats" screen... What is this screen exactly, how is it displayed, and why don't you return to it ?
Sixthly, the
() is missing in the screen declaration.
You must be registered to see the links
. Without it, the screen will not benefit from some optimizations.
In the end, your code should looks like something near to this:
Python:
init python:
# /!\ Assuming, from the code you shown, that "stats" is just here to
# open the relationship menu. /!\
# Add the screen as overlay, for it to always appear on top of the screen
# content, unless Ren'Py is in "main menu" state.
config.overlay_screens.append( "stats" )
# A single button that will open/close the relationship menu anytime the
# player want to see it.
screen stats():
imagebutton:
idle "openRelationshipIcon_idle.png"
hover "openRelationshipIcon_hover.png"
# Used as explicit example, but should be:
# auto "openRelationshipIcon_%s.png"
# The positions are arbitrary, taken directly from you code. They
# are here purely for the example.
xpos 1616
ypos 21
# One click open the "relationship" screen, another close it.
action ToggleScreen( "relationship" )
screen relationship():
# Ensure that a click outside of a button will not make the game advance.
modal True
# Store for which character the screen should show informations.
# By default /None/.
default characterSelected = None
# The icon button for Hope. Clicking on it will display the stats for
# her, and automatically remove the previously shown stats if there is.
imagebutton:
idle "hopeRelationIcon_idle.png"
hover "hopeRelationIcon_hover.png"
# Used as explicit example, but should be
# auto "hopeRelationIcon_%s.png"
# The positions are arbitrary, taken directly from you code. They
# are here purely for the example.
xpos 1538
ypos 84
# The player want to see the informations for "hope"
action SetScreenVariable( "characterSelected", "hope" )
# The icon button for Harper. Clicking on it will display the stats for
# her, and automatically remove the previously shown stats if there is.
imagebutton:
idle "harperRelationIcon_idle.png"
hover "harperRelationIcon_hover.png"
# Used as explicit example, but should be
# auto "harperRelationIcon_%s.png"
# The positions are arbitrary, taken directly from you code. They
# are here purely for the example.
xpos 1209
ypos 79
# The player want to see the informations for "harper"
action SetScreenVariable( "characterSelected", "harper" )
# There's no need to a return button since the screen is closed
# from "stats".
# Frame where the information are displayed, if there's information
# to display. It's important to put this in a frame to ensure that the
# possible background will not overflow.
frame:
# The frame is placed below the buttons for each character.
ypos 500
# If a character is selected...
if characterSelected:
# include it's screen in order to show the information.
# The /expression/ keyword permit to build the name of the screen
# in real time. Here, it's the value stored into the /characterSelected/
# variable.
use expression characterSelected
# If there's not character selected...
else:
# display a blank screen.
# It's just an example, you can perfectly not use the /else/ part at
# all, and let the screen blank.
add "blank stats.png"
# The screen to include that will show Hope stats.
screen hope():
# All children (here /add/ and /grid/) will be positioned starting from
# the top left corner.
fixed:
# Image to show as background.
add "stats hope.png"
# Two rows of two columns.
grid 2 2:
# Centered in the display zone for the example, but you
# put it wherever you want it to be.
xalign 0.5
yalign 0.5
# No need to position them, the grid will do it for you, including
# the vertical alignment.
text "Beatrix Affection : "
text "[Beatrix_affection] "
text "Hope Affection : "
text "[Hope_affection] "
# The screen to include that will show Harper stats.
screen harper():
fixed:
add "stats harper.png"
grid 2 2:
xalign 0.5
yalign 0.5
text "Liana Affection : "
text "[Liana_affection] "
text "Harper Affection : "
text "[Harper_affection] "
Have been used, in addition to what have been linked previously:
The
You must be registered to see the links
screen property.
The
You must be registered to see the links
configuration value.
The
You must be registered to see the links
screen action.
The
You must be registered to see the links
and
You must be registered to see the links
screen control statements.
The
You must be registered to see the links
,
You must be registered to see the links
,
You must be registered to see the links
and
You must be registered to see the links
screen statements.
