Boss Transformation Turn Reset (FEATURE COMPLETE)

● ARCHIVED · READ-ONLY
Started by ZeroBreak 11 posts View original ↗
  1. Not sure if anyone's ever done this before or if this is the right place to ask but hear me out.

    I just finished testing the endgame of my project's main story (up to the rollcall and before the second quest prompt, assuming no k-code skip-ahead). What I'm asking now is about extending it to where once the real bad guy is exposed and summoned (in the vein of the bridge from Grandmaster Hargon into Sydo Malroth back in DQ2) that when said perpetrator does a phase shift (Psaros style from DQ4) it automatically terminates orders and goes back to issuance (again, like Psaros in DQ4 when his head and arms literally get blown away).

    Any idea on how to do this without forcing battle cycle so that it's 100% seamless?
  2. No takers yet?

    I can always elevate to script requests or equivalent if necessary so ask away!
  3. you should know that we expect people to wait for 72 hours instead of only half a day before bumping, because no one gets paid here for helping anyone and you'll have to wait until we have time to help.

    That said, your description is effectively unreadable and most likely most people can't even guess what you want.
    "like <unknown game xy>" is a bad description because only people who played the same games as you did could understand it - and a lot of the people helping here don't have the time to play every game around.

    Give a better description - preferably with screenshots of the troop events used so far, and we can help.
  4. Sorry I wasn't specific and apologies for the quick trigger.

    Anyway, the general idea is to end processing when the boss does its phase shift during the final showdown so that instead of the next actor in sequence laying it down on the immediate after transformation occurs you have to reissue commands as if the whole thing was just getting started. The difference is that I want it to be 100% seamless in presentation, so abort battle processing between quarters, halftime etc. will not be accepted for this. That being said, the effect still has to play out as if it's a new battle sequence and not further continuation of the active conflict such that even if another actor is waiting to cut loose then it goes into the end-turn phase considering that everyone has already done their part for building things up into the moment.

    I did try doing it the hard way by using forced actions to defend cycle at the time of phase shift processing. Unfortunately, it only served to soft-lock the game and had to be abandoned like STAT.
  5. that still doesn't help.
    What is a "phase shift" in developer terms?
    How do you trigger the boss transformation?
    And what is your exact problem with "abort battle"?

    We can't help if you don't describe what you want in the terms how the RM battleengine works.
  6. By phase shift I mean the boss transformation (which is done using the built-in mechanism for simplicity in a troop event based on your opponent's HP when measured at at 75%, 50% etc.). And abort battle means exactly that - setting an abort battle call in the respective troop event. The issue with the latter would be that you make like you're gonna run the hell outta Dodge when in reality you're simply going into the next quarter/half/etc., which by consequence is not the intended behaviour in terms of presentation.
  7. again, please show us screenshots of the troop events.
    That is where you have to create your effect, and your descriptions are not enough to see what you've already done there.

    I'm guessing that you want to abandon battleturn instead of aborting battle, and do that several times depending on enemy transformations that you triggered in troop events.
    That depends on us to know what exactly you did with those troop events, otherwise there is no way (it's already difficult because the default turns don't have a function for that).
    And if you have any plugin that changes the turn behaviour of your battles from default, you need to give us links to the websites of those plugins as well.
  8. I'll prepare a visual record of what I initially did by lunch hour, but again it's relatively easy to simply explain as what I did was to attempt the use of forced actions as a workaround. In the event that a script will also help out here I'm going to search accordingly, and if so I'd be willing to defer to relevant continuance under the respective department (like for script requests, if that's what it takes).

    EDIT: And here it is. Note that crew and enemy profiles and related indices are edited from view under asset, IP and concept protection laws and requirements as this is obviously classified as a work in progress. Also, skill slot two is used here because it's the default slot for defence and therefore what I initially thought would be enough to do it.

    vouUhRg.png

    EDIT 2: As an alternative I think I'll try this with a one-by-one as opposed to the usual all-at-once plan of attack.
  9. there is no transform command on that screenshot, so we still have absolutely no idea of what the event does.
    and no, force-action to the guard skill does not do what you want, mostly because force action creates an additional action for that actor without removing the existing preselected actions.

    my suggestion would be to add a state to all actors that makes the actors unable to act (restriction) for the reminder of the turn (duration = 1~1), preferably a state without messages, and test that.
  10. Messages aren't exactly a concern as I'm using Yanfly Battle Core, however based on crew reactions I think I've got it. Not sure if there's a workaround for whomever got last hit staying in forward step upon time of deferral (assuming side view perspective) but otherwise I'd say it works.

    EDIT: Also noticed that for the workaround to function properly it has to apply to your own crew as likewise with the opposing troop spawn, meaning that if you set one and not the other - and the enemy hasn't yet played its hand - then you're still gonna be hit regardless. And that's no fun to deal with, for obvious reasons.

    EDIT 2: Barring improvements to my approach here I'm gonna mark this as feature complete. Thanks again, @Andar!
  11. [closed]IgnoreMe[/closed]