Moving Actors' Battle Position

[Geoff The Dragon Slayer]

I'm like 75% Percent complete with my battle system but I need help, Moving the Actors' battle position they are too high up on the screen,

Like So:

See how it seems like they are floating in the sky and standing on the wood?

How do I make it so that they are on the grass in idle stance and not just when they're attacking?

 

[Shaz]

Obviously you are using a custom script. Please provide a link to it, so we have an idea of what system you are using.


And, of course, where "on the grass" is will depend on the battleback you are using. If you change them around depending on the enemy troop, what looks right on one may not look right on another.

 

[Geoff The Dragon Slayer]

I'm sorry I meant to put that in the topic I' using Galv's Animated battler script.

http://galvs-scripts.com/galvs-animated-battlers/

 

[ellcar]

o boy miss read

 

[Geoff The Dragon Slayer]

OH I feel so stupid, Rereading the scripts I see where the place to change this settings is it's an X,Y offset any idea on how I need to set this to get them where I want them?

Edit: Oh man, it says not to touch the actor positions.

 

[Shaz]

No, it's not the offsets. It's this:

#------------------------------------------------------------------------------#  ACTOR_POSITIONS = [ # don't touch#------------------------------------------------------------------------------##  Set x,y locations of your actors on the battle screen#------------------------------------------------------------------------------#     [440,150],   # Party member 1 [x,y]    [460,180],   # Party member 2 [x,y]    [480,210],   # Party member 3 [x,y]    [500,260],   # Party member 4 [x,y] #------------------------------------------------------------------------------#  ] #don't touch#------------------------------------------------------------------------------#

I imagine you would just adjust those values (specifically, the 'y' or second value of each pair). The larger the number, the lower on the screen they will be. It looks like the grass starts about half way down, so if you're not using any scripts to resize the screen, you might try making them 208 or higher, remembering that the screen height is 416, and taking into account the space taken by the hud. If you're using a script to resize the screen to 640x480, you'd probably want your first y value to be a bit higher than 240, and the others all slightly higher than the previous one.

 

[Geoff The Dragon Slayer]

Once I changed that settin the actors started doing wierd and they're not in they're Idle stance anymore.

 

[Shaz]

What did you change? Show me the new code.


The "don't touch" just refers to the first line and the last line. Not the actor position settings themselves.


If they're not in the "idle" stance anymore, I suspect you've changed more than just what's in that section.

 

[Geoff The Dragon Slayer]

#------------------------------------------------------------------------------# ACTOR_POSITIONS = [ # don't touch#------------------------------------------------------------------------------## Set x,y locations of your actors on the battle screen#------------------------------------------------------------------------------# [440,240], # Party member 1 [x,y] [460,250], # Party member 2 [x,y] [480,260], # Party member 3 [x,y] [500,270], # Party member 4 [x,y] #------------------------------------------------------------------------------# ] #don't touch#------------------------------------------------------------------------------I made little changes on the y axis

 

[Shaz]

Just as an experiment, change them back to what they were and see if they're back in the idle stance and if the "weird things" stop. What sort of weird things were they doing?


Have you made any other changes to the script, or is it exactly as shown in the link apart from the position changes above?


Also, are you actually playing your game, or testing through the Battle Test function? If the latter, are you saving your changes in the editor first (not just hitting OK or Apply in the scripts, but actually saving the project)?

 

[Geoff The Dragon Slayer]

The weirdness continues (The weirdness is the actors are attacking when they're supposed to be idle)

Nope no changes.

 

[Shaz]

And was it all working properly before, with the exception of the actor locations? Have you made any changes to your database notes/tags? Delete your whole script, then copy/paste from the original again and see if the problems go away. If they do, I would suspect you HAVE made other changes to the script and just don't remember them (it happens more often than you'd like to imagine). If they continue to happen, then I'd be looking at how your notes/tags are set up.


In either case, I doubt very much that changing the y location of the actors had anything at all to do with it.

 

[Engr. Adiktuzmiko]

Yeah get the original script and try to recall your set-up of the database because I think it's quite clear that you actually did modify more than the actor positions

 

[Geoff The Dragon Slayer]

Yeah get the original script and try to recall your set-up of the database because I think it's quite clear that you actually did modify more than the actor positions

As previously stated I did not change anything other than the y,

I will copy the script once again but from the demo this time I may have neglected to copy something or copied something extra.

 

[Engr. Adiktuzmiko]

which will only make sense if after changing it back resulted to it being fixed but since you said:

The weirdness continues (The weirdness is the actors are attacking when they're supposed to be idle)


Nope no changes.

then it's clearly a case of you did something extra which you forgot (or didn't realized you actually changed something else while looking for the parts)... we've encountered a lot of people who did that already, you're not the first, so no worries...


also, since you didn't answer Shaz' last question

Also, are you actually playing your game, or testing through the Battle Test function? If the latter, are you saving your changes in the editor first (not just hitting OK or Apply in the scripts, but actually saving the project)?

 

[Geoff The Dragon Slayer]

Also, are you actually playing your game, or testing through the Battle Test function? If the latter, are you saving your changes in the editor first (not just hitting OK or Apply in the scripts, but actually saving the project)?

I am battle testing hmm... I will play the game.

 

[Engr. Adiktuzmiko]

If you're running battle tests, make sure to hit save first...

 

[Shaz]

Yep. When you PLAY the game, it asks you to save your edits beforehand, so any script changes will be saved and applied. But when you battle test, it doesn't automatically save and it doesn't ask you to, so any battle scripts are the last-saved version. Your changes would not have been seen if you didn't manually save.


That still doesn't indicate why the weirdness happened. If you're absolutely certain you didn't change scripts (and as much as you say you didn't, there have been enough people who have sworn the same thing who, in the end, actually DID change their scripts, that I just can't rule out out the possibility), then there must be something going on in the actor/skill/whatever notes. I looked through the script for any reference to variables and switches, which is usually the cause for 'weirdness' with some scripts, but couldn't find any.


The thing is ... if it WAS working, and it's not now, then the problem is with something you've changed between those two times. If it's not the scripts, then it's the database itself, or the particular characters you're using, or something like that.


How much work have you actually done on this? Have you JUST added the script or have you done all the note-tag setup as well?

 

[Geoff The Dragon Slayer]

The Problem I referred to as "weirdness" has ceased,

Thank you both for your quick replies and valiant effort in helping me with my problem

I finally Got it to work again thank you.

 

[Shaz]

It would be really interesting to compare the current version of your script with the version that produced the 'weirdness'.


Did you get all the y-positions working properly too?