Reedo

Reedo's Simple Side Battle System Ace Edition (RSSBSACE) Version 1.7b September 30, 2013 By Reedo References None. This is an original script by Reedo. Description This script is a recreation of the original RSSBS created for VX back at the end of 2009. The script has been completely reworked for ACE. RSSBSACE offers a simple, plug-and-play, side-view-battle-system with no additional resource requirements. This script is only a visual modification to the battle system and does not add any game-play mechanics. RSSBSACE is designed for a high-degree of compatibility with other scripts. Features This simple SBS provides a classic "FF"-style side-battle experience. This script will: Draw the party on the right side of the screen, facing left, using the actor graphic specified in the database and in a formation fitting the Ace battle background layout. Place a shadow on the ground beneath living actors. Show the actor's stepping animation on their turn and when acting, if able to take actions. Make the actor step toward the enemy when taking an action other than guarding. Show animations for all actor actions as defined in the database for the particular action being performed. Show animations for all enemy actions as defined in the database, or a default animation if none is defined (e.g. normal attack) Flash the actor red when they successfully receive a hostile action. Show dead actors as faded, whitened, and rotated to lay on their back. Make living actors perform a "victory dance" when the battle ends (they jump and spin). Optionally "mirror" enemy images to make them face to the right. Version 1.2 Make actors step back when guarding. Make actors start facing backward and jump when surprised. Make actors start facing down and flashing white on preemptive strike Version 1.6 Show weapon or skill icon as moving (swinging, punching, or pulsing) graphic during actions. (by popular demand!) Now compatible with "battle test" from within the database. Version 1.7 Additional options for weapon motion by weapon type. Ensures all animations play on RSSBSACE on-screen actors. As an additional feature, the script will force the game to attempt to load a tile-based battle background for any map type, not just maps using the field tile set. Some of the floor tiles in the other tile sets will work to generate a battle background, so this allows you to use tile-based backgrounds in more of your maps. Options There are a few options at the top of the script which can be modified to change the positioning and movement of the actors, specify the mirrored enemies, and disable the forced tile-based battle backgrounds. In most cases there will be no need to modify any of these options, other than the list of enemies to mirror. This option looks like: FLIP_ENEMY = [ 3, 4, 6, 7, 8, 10, 14, 16, 17, 18, 19, 21, 22, 24, 25, 27 ] And each number is simply the ID of the enemy to flip. This is the number preceding the enemy name in the Enemies tab of the database. Screen Shots (battle begins) (player attacks) (player is hit) (victory dance) Known Bugs None at this time. Please report any found. Requirements None. This is a stand-alone script. Installation Plug-and-Play Just insert a new script directly under Materials, name it RSSBSACE, and paste in the script code. For compatibility purposes it is typically best to insert RSSBSACE above all other scripts*. * If using Yanfly YEA Battle Engine, this script must be installed below the Yanfly script. Configuration The only configuration necessary will be to arrange the troops such that the enemies are on the left-hand side of the screen. Go into the Troops tab of the database, select each troop used in your game and drag the enemy images to arrange them to your liking on the left side of the screen. All other configuration is optional via the "User Options" section at the top of the script. Compatibility Should be compatible with most other scripts. Obviously any other script which also modifies the battle scene may not be compatible, but this should mostly relate to visuals such as the placement of animations. Any battle-addon which affect mechanics and not visuals should be compatible. The original RSSBS for VX was highly compatible with other scripts. This version follows a similar design pattern so I expect it to also be highly compatible with other scripts. A Note About YanFly Scripts I have not yet tried any of Miss YanFly's scripts for Ace, but I expect there may be some contention between our two scripts. Although I suppose it is equally likely that her script will simply overwrite mine and everything will occur with her settings while my actors appear on screen. We had a good deal of success between our scripts in the past so if this one turns out to have any issues I will do my best to set some time aside to correct my script and ensure as much compatibility with Miss YanFly's as possible. Update This script is now confirmed compatible with the Yanfly YEA Battle Engine. Script Here is the complete RSSBSACE script: Summary With this script you can quickly and easily show your party on screen during battle with animations and effects and no special configuration beyond rearranging the enemy layout in your troops. Comments and suggestions are welcome.

I didn't say it couldn't be done; but shrinking the icons won't look good, and the user would have to specify where the attachment points where at for each weapon to fit the "hand" of each character - and ideally you'd need the arm in its own layer. It all just becomes complex and deviates from the "Simple" part of the script. Most likely the other side view scripts you refer to use separate assets for attack animations; while this looks best, it does require a lot more extra assets and configuration (again, deviating from simple). And that's why multiple scripts exist... so you can choose the one that works best for your requirements.

Since this would be your own special customization that wouldn't apply for anyone else you might consider making it a script request. The first part should be fairly simple; the second though would require you to provide a larger image of your character instead of using the on-map image. It will be a few days before I can start working on scripts again and I have a backlog of work to do so I wouldn't expect to be able to get to a one-off request for a while. If you do a script request though, someone else may be able to help you more quickly.

@Swish: That's exactly how it is supposed to work. The weapon icons are no where near being scaled to the character so it would be unreasonable for the character to try to hold the weapon. The effect is modeled after FF3 per a request on the main thread.

This has already been mentioned in the thread. Its this dumb forum trying to interpret code as an email address. I'll post again using the insert code button and forget trying to use the broken /ruby tag. Or just go to the main Ace forum and get the code from there.

The script has been updated to version 1.7. This version adds additional options for weapon icon movement on screen, corrects a bug if an escape attempt failed, and corrects an issue with placement of animations providing compatibility with Yanfly's Ace Engine. See the main thread for additional details.

Sorry but no. Let me know what you find though

Well, that's not quite the issue... the script relies on a lot of existing functionality and a portion of it is located in the Game_Map. The answer was to provide the battle test with an instance of a map, so the script will use map #1 in your game (it doesn't really matter which map - any map will do). Its fixed now. - Bah, can't seem to make two posts in a row... they get merged... anyway - Ok folks, I've updated the script to add images of the character's weapon swinging when they attack, or a pulsing icon of the item or skill when they take those actions. Obviously this isn't going to look right for projectile weapons yet, so that will still have to be taken into consideration. But this should be a good start on the common request for action images. Please let me know if you find any issues.

The script has been updated to version 1.5 which now has the actors stepping as discussed. Initially the actors will be standing still. During command selection, the current actor will step if they are able to move. Also, an actor will step when they are executing their action or doing the victory dance. This was a little more involved to work into the script than I initially suspected so it is a permanent feature; the old way is not available via an option.

A large update has been made. The initial journal scene is ready for testing and the editor contains minor bug fixes and expanded help content.

Please follow current developments for this script at: http://forums.rpgmakerweb.com/index.php?/topic/18205-rsqs-reedos-simple-quest-system-beta/?p=175583 I will update this thread with the final post when the script is complete.

Hi Bastian, thanks for this I'm looking at the "active character" thing... perhaps making it so that the actor is only stepping when it is their turn (and they can take an action on the turn). I'll probably try to work in a couple options and let the designer decide which to use. This ties in with a comment made in the other forum so I'm definitely looking into it. I try to use as much existing functionality as possible; in this case the script is reusing the map actors. The existing methods for moving actors around the map take arguments in the form of number of tiles to move, not number of pixels to move. Since I'm reusing the existing movement code, those methods are thinking in terms of "map tiles" (32x32 pixel squares, or the grid that appears on the map designer) even though the battle scene doesn't actually utilize a grid. So while this could be changed to take pixel dimensions, I think it is acceptable to keep the grid coordinates. It may actually be easier for a non-scripter to think of moving "1.0" as the distance of 1 tile on the map (versus thinking of pixels and display resolutions). Due to the way that Ace generates its battle back images, there is only a very small area of space where actor can be placed to still appear "on the ground" and not be covered by the battle menu windows. To accommodate this, I had to squish all of the actors into a tight formation. So while it would still be easy enough to rearrange them into an angled line, that angle would be long and shallow because the area they have to stand in is not very high. The first actor would have to be moved to the left quite a bit to make enough room for everyone. I didn't think it would look good. But, since this is a pretty subjective thing, I'll see about adding an option so that the designer can choose either formation. To be honest I kinda skimped on the formation part compared to the old VX script... so maybe I should make it a little more feature-rich. Features are great so long as I can maintain the simplicity. That's always been the top benefit of RSSBS.

That is the goofy forum trying to interpret !@subject as part of an email address. I've edited the code in the post so you can copy it into your game again or just go to that line (and another one beneath it) and get rid of the "mailto:" that the forum inserted. You'd think the forum would be smart enough to not attempt to resolve any smileys or URLs in a code block... but it might be because of that custom [ruby] tag... that implementation probably needs to be modified to remove the auto conversions.

Updated script to correct bug when party attempted to escape battle. Added visual for escape (party turns and takes half a step).

@^^ ROFL good catch

Well that's a pretty serious error... that method should definitely exist on that object... You'll probably need to look at the other scripts you have installed. I would have to guess that one of them has issues, or is explicitly incompatible with any other script that uses $game_party.battle_members. Somehow that method has been removed, so something you've got is breaking it. (*I have to assume it is not an issue in this script, based on the error message; I haven't actually reviewed the script, but since it seems to work for everyone else there is a high probability that he problem is specific to your game configuration). -EDIT - Isn't there a support forum that is supposed to be used for issues like this? Or can people use both the support forum and the source thread? (question more for a mod/forum power user) -edit to my edit - lol I think I got confused with the other forum =P so never mind on this question