or i can just use it as normal variable and set some value...
for some reason it did not work
Sprite.new(some_viewport)) or without a viewport (Sprite.new). When you don't, the Sprite's Z-value is compared to the viewports' Z-values, NOT the sprites contained within those viewports. Initially, it too has a Z-value of 0. But the rules of order dictate that the most recently created Sprite is drawn on top of everything else of the same Z-value, hence why your picture was always above the character (and everything else drawn to @viewport1). It wasn't until you made it less than 0 that it would be below @viewport1; but now this puts it below ALL THE SPRITES on @viewport1.attr_reader , like this:class Spriteset_Map
attr_reader :viewport1
endclass Scene_Map
attr_reader :spriteset
endvp = SceneManager.scene.spriteset.viewport1
$game_variables[30] = Sprite.new(vp)
$game_variables[30] = nil
$game_variables[30] = Sprite.new(SceneManager.scene.spriteset.viewport1)
#$game_variables[30].viewport = SceneManager.scene.spriteset.viewport1
$game_variables[30].bitmap = Bitmap.new(544,416)
$game_variables[30].bitmap.fill_rect(0, 0, 544, 416, Color.new(255,0,0,255))
#$game_variables[30].z = 0
$game_variables[30].x = 0
$game_variables[30].y = 0
This normally means you have code duplicated somewhere, but could also mean that whatever you did is causing the code to loop back onto itself.
$my_sprite = Sprite.newThe common issue is usually a duplicated script. See if you have them.
yes, I've been warned about this several times already.
It is just general good practice, there is a chance that you might forget why and ended up causing problems you don't know.
Specifically, in this case, it is not.
Specifically, in your case, you're reading a number. You have to look up the variable name to know what it is for. Imagine that you just name your global variable, which would even more readable than just game variable number 30, "what it is? I had to look up"
yes, you can just change the name to $elevator_sprite of course.
in this case it is inconvenient for me personally - I prefer to copy and paste lines from events from different locations, simply by changing the event number in the new script. otherwise I will need to change the variable names completely ...
In this case, you can define
For individual pixel color, you can use .set_pixel(x,y,Color.new(255,255,255))
for some reason it doesn't work - pixels don't change color:
xx=1
yy=1
while xx < 160
yy=1
while yy < 416
# if $game_variables[30].bitmap.get_pixel(xx, yy) == Color.new(255,0,0,255)
$game_variables[30].bitmap.set_pixel(xx, yy, Color.new(0,200,0,150))
# end
if yy == 32
yy = 383
end
yy += 1
end
xx += 1
endnope. I needed to make the background transparent, leaving the image of the objects intact. it turned out that I was capturing the picture before the screen was completely faded out. therefore the colors were different ...
class Skill_Requirements
def initialize(actor)
@requirements = Array.new(&data_skills.length)
@actor = actor
@requirements[150] = @actor.fire>5 && @actor.fire_ratio>0.5 #breaks on this line
end
end
class Game_Actor < Game_Battler
attr_accessor :fire
attr_accessor :fire_ratio
def setup(actor_id)
@fire=0
@fire_ratio=0
@skill_requirements = Skill_Requirements.new(actor)
end
def learn_skill(skill_id)
unless skill_learn?($data_skills[skill_id]) && skill_requirements.meets_requirement(skill_id)!=false
@skills.push(skill_id)
@skills.sort!
end
end
Thanks for the info, I didn't delete the rest of the code in setup(), I simply didn't include it in my post so that you would have less to read through.
