#Does anyone know which file Yisuno added/changed to implement his new camera mod?

32 messages · Page 1 of 1 (latest)

eternal sierra
#

I'm trying to figure out what he added/changed to make the cameras do what they do.
Not really looking for a complex explanation on how he did it, I really just want to know where I can find the file that he worked with to make it happen.
I will say that BattleWaitCameraData.json inside of battle_masterdatas seems to be overwritten by something he added? Unless it just never did anything in the first place, but I doubt that. Edits seem to have no impact in game, so I'm assuming his mod just overwrites the original waiting camera system completely.

I would like to edit the data to experiment with the new cameras, so any push in the right direction would be appreciated. ✌️

spiral palm
#

I can’t guarantee that he will respond but I can ping @frozen orchid to see if he’s able to give you some insight.

eternal sierra
#

I think I might have tracked it down to the btlv folder inside of Battle.

New question, how in the ever living **** did Yisuno edit all this data without passing of old age?
It's like 1200 ambiguously named files, each filled with a .json that would take a day to edit to completion. 💀

spiral palm
eternal sierra
# spiral palm Oh I can answer that one: Yisuno is based.

lmao facts,

Tbh I have two guesses, this mod was made with an external program, or perhaps it was imported and edited from one of the gamecube games maybe?

Or actually, maybe each file is a duplicate with a different name and they were just to huge for me to catch on while reading them.

frozen orchid
#

Go on, keep guessing, this is fun to hear

eternal sierra
#

😭

#

im unpacking the most recently modified hoping to figure something out

frozen orchid
#

Those files of your screenshot are the sequences of my new tracking cameras btw

eternal sierra
#

I haven't gotten through looking at them all, but so far 1045, 1067, and 1056 seem to have a monobehavior file that might be almost identical?
I'm seeing things like fov and references to how you get the pokemon to play its cry and attack animation during the camera waiting.

#

I'm hoping that I might be able to achieve more zoomed out camera shots while still maintaining the camera tracking on the mons

frozen orchid
#

Easiest thing would be changing the FOV from 34 to a higher number

#

The other way is... not fun at all lmao

eternal sierra
#

lol I bet, I'm assuming every monobehavior on these will need to be adjusted to have the matching FOV?

frozen orchid
#

Yup, you need to change all the files listed in "BattleWaitCameraData"

eternal sierra
#

ooooo that clears up a lot for me

frozen orchid
#

Since each file refers to a different Pokemon + attack animation

eternal sierra
#

does BattleWaitCameraData's info get overwritten by your new files btw?

#

I notice it has editable FOV and stuff, but doesnt seem to do anything when changed.

frozen orchid
#

And there's also for single and double battles as well

frozen orchid
#

And yeah the data in there does nothing afaik

eternal sierra
#

I sure do hope that these monobehaviors will be mostly copy/pastable lol, testing for the right FOV distance number is gonna be hell otherwise.

frozen orchid
#

They're basically the same script, just different animations and Pokemon to point at

spiral palm
#

Ought to be able to find and replace the FOV on all of them in one go right?

eternal sierra
#

Yeah that's what I'm thinking, I just need to make sure that I catch all the differences between each of them. If I miss one little thing in the middle or something, then it could break it I imagine.

#

I'll have to single out the FOV changes in one script, and then the copy/paste almost the whole edited version to the others.

#

There's also some random stuff in japanese that I need to make sure is the same between each one.

eternal sierra
#

So each file refers to a different Pokemon and attack... Is it separated by Pokemon size I would assume?

If so, is there a quick way to identify what file goes to which Pokemon size type?

#

And if I'm off the mark on that, then what exactly is each file targeting if not size differences and battletype?

eternal sierra
#

90 FOV looking a bit silly tbh lol

#

makes it further but in motion everything looks a bit stretched out, maybe it's the drastic switch from the default FOV into 90 back and forth everytime you attack