Ok, it tried a new p command right after my block tests if Shift is pressed and still nothing. that means that my entire class that aliases scene_item is not working...
Place your p command before and after your alias statement. Different text of course.
If it executes before but not after your alias, then it has something to do with the method you're using. If it executes both print statements, then your method is running through all the statements.
Sorry if I cut in without reading the whole thread. I'm answering to the initial question here. When an inherited class defines a method that exists in the base class, it can use the reserved word super to call the base class version of the method. Aliasing isn't necessary if you can use this technique in your code.
i have tried super and i tried using p at different points. simply put, none of my methods are being used, though the class is being called just fine. I placed a p command outside the methods and the game displayed it. so this just will NOT work unless it is actually pasted into Scene_item, evidently. I dont understand. I thought alias could take an existing method and add to it without editing the script directly... I figured super would call the original code in the super classes method of the same name, and then run the new code.... Maybe i just dont get it
ok, so I played around with changing the color of the title HP in Window_BattleStatus so that when in battle, 'HP' is shown green. this was just a simple way to try to alias methods, though Im not sure if this is done correctly.
This DOES change the Name of 'HP', but I am curious if this would be no-no for compatibility? Essentially, I re-wrote def refresh so that it calls my method draw_colored_hp instead of draw_actor_hp.
Basically, in terms of compatibility and/or scripting ettiquette, is this acceptable?
Man, I suck at this!
Code:
HP_COLOR = Color.new(128, 255, 128, 255) # Green
# this constant is just here to make it configurable, even though
# it could be just placed below...
class Window_BattleStatus
# I doubt if I even need the alias, as the new refresh method
# directly calls the color edit method.
alias draw_colored_hp draw_actor_hp
def draw_colored_hp(actor, x, y, width = 144)
draw_actor_hp(actor, x, y, width = 144)
self.contents.font.color = HP_COLOR
self.contents.draw_text(x, y, 32, 32, $data_system.words.hp)
# This is to change the color of 'HP' or whatever the game
# calls it. As this is a test, I am just
# trying to see if this is acceptable practice.
end
def refresh
# This method directly calls the color edit method, so I don't
# think I need the alias above. However, if I do not change
# the refresh method to call my method, then mine never gets
# called, alias or not... I don't understand the right way to
# use alias maybe?
for i in 0...$game_party.actors.size
actor = $game_party.actors
actor_x = i * 160 + 4
draw_actor_name(actor, actor_x, 0)
draw_colored_hp(actor, actor_x, 32, 120) #changed from draw_actor_hp
draw_actor_sp(actor, actor_x, 64, 120)
if @level_up_flags
self.contents.font.color = normal_color
self.contents.draw_text(actor_x, 96, 120, 32, "LEVEL UP!")
else
draw_actor_state(actor, actor_x, 96)
end
By compatibility standards, it is a no-no. However, thanks for noting it and asking. We do prefer to use alias whenever possible. BUT... if RPGMaker's database editor does not allow you to change words like STR, DEX, HP, Gold, and the like, what choice DO you have?
When you make a script, it would be good to let anyone using it know what methods you rewrote. That way they would know what's up if they experience a problem.
I prefer to add a configuration section in my scripts to allow the end user (ie you) to be able to change my custom texts... if needed. Using a config section is easy enough. Working on making a good one... practice practice practice.
EDIT: *DerVVulfman now looks at the script*
EDIT 2: Remember how we talked about inheritance and that one script inherits the methods from another?
Window_Battlestatus inherits the draw_HP command from Window_Base... the class that defined it. However, if you have your own 'draw_actor_hp' in the Window_Battlestatus class, it only affects that class. Your menus and all other HP drawing systems will still use the default one.
You coulda just use the whole thingie. ^_^
Code:
HP_COLOR = Color.new(128, 255, 128, 255) # Green
# this constant is just here to make it configurable, even though
# it could be just placed below...
#==============================================================================
# ** Window_BattleStatus
#------------------------------------------------------------------------------
# This window displays the status of all party members on the battle screen.
#==============================================================================
class Window_BattleStatus < Window_Base
#--------------------------------------------------------------------------
# * Draw HP
# actor : actor
# x : draw spot x-coordinate
# y : draw spot y-coordinate
# width : draw spot width
#--------------------------------------------------------------------------
def draw_actor_hp(actor, x, y, width = 144)
# Draw "HP" text string
self.contents.font.color = HP_COLOR
self.contents.draw_text(x, y, 32, 32, $data_system.words.hp)
# Calculate if there is draw space for MaxHP
if width - 32 >= 108
hp_x = x + width - 108
flag = true
elsif width - 32 >= 48
hp_x = x + width - 48
flag = false
end
# Draw HP
self.contents.font.color = actor.hp == 0 ? knockout_color :
actor.hp <= actor.maxhp / 4 ? crisis_color : normal_color
self.contents.draw_text(hp_x, y, 48, 32, actor.hp.to_s, 2)
# Draw MaxHP
if flag
self.contents.font.color = normal_color
self.contents.draw_text(hp_x + 48, y, 12, 32, "/", 1)
self.contents.draw_text(hp_x + 60, y, 48, 32, actor.maxhp.to_s)
end
end
end
I figured it out. My problem was how I was aliasing the methods. I wasnt calling the old method correctly, but now that I learned, I have adapted my script. In fact, it has allowed me to finish my first script which I will post here shortly.
Ah, be forewarned about aliases. They are tricky devils.
Picture an method like this:
Code:
def method_one(x)
return_val = x + 3
return x
end
It adds 3 to what is entered. And then returns it. Aliasing this should be like this...
Code:
alias new_method_one method_one
def method_one(x)
value_new = new_method_one(x)
value_new += 40
return value_new
end
This new alias retrieves the value gained from the original method, and then adds 40 to it before returning it. This way, you can alter values that are generated and returned by methods.
Another thing that you might be careful: don't use aliases with methods that exists only on the parent classes.
#Wrong
Code:
class Parent_Class
def method(*args)
#anything
end
end
class Child_Class < Parent_Class
alias old_method method
def method(*args)
old_method(*args)
#anything
end
end
This will return the stack level too deep error if you press F12.
Instead use the super
Code:
class Parent_Class
def method(*args)
#anything
end
end
class Child_Class < Parent_Class
def method(*args)
super(*args)
#anything
end
end
Ah, so is that the culprit of the dreaded F12 glitch? When I encounter and narrow the offending method, I've been wrapping them in an if...end block that Seph showed me years ago.
