You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to be able to launch a fight instantly wherever we are, so we can test new fight setup without having to walk around or move to the monster location.
The dev tool should be a nice place to put it.
The different parameters would be:
The ID of the monster
The level of the monster
The battlefield ID ? Not the most useful but could allow to test some corner cases of the AI that launch action depending of the battlefield.
I don't see needs for others parameters
Thank you !
The text was updated successfully, but these errors were encountered:
HobbitDur
changed the title
Dev tool: Launch instant battle to defined monster (at specific level)
Dev tool: Launch instant battle to fight monster (at specific level)
Sep 7, 2024
HobbitDur
changed the title
Dev tool: Launch instant battle to fight monster (at specific level)
[FF8] Dev tool: Launch instant battle to fight monster (at specific level)
Sep 7, 2024
julianxhokaxhiu
changed the title
[FF8] Dev tool: Launch instant battle to fight monster (at specific level)
[ FF8 ] Dev tool: Launch instant battle to fight monster (at specific level)
Sep 8, 2024
I've been thinking about this but we've implemented something similar in The Test Room and I think we can manage the same on FF8. And it's totally doable outside of FFNx. Since this doesn't exist for FF7, I'd prefer not to add it for 8, as it would be much harder to manage all the states to jump between battles ( internally ) rather than using field code like we did in the Test Room.
The idea is to be able to launch a fight instantly wherever we are, so we can test new fight setup without having to walk around or move to the monster location.
The dev tool should be a nice place to put it.
The different parameters would be:
I don't see needs for others parameters
Thank you !
The text was updated successfully, but these errors were encountered: