TJ Blakely | Xenoblade Chronicles Definitive Edition New Game Speedrun in 5:20:52 @TJBlakely | Uploaded September 2020 | Updated October 2024, 9 hours ago.
Date recorded: Friday, August 19, 2020
Timing starts on selecting "New Game" and ends on killing blow on final boss.
Accepted XC2 Money
Date recorded: Friday, August 19, 2020
Timing starts on selecting "New Game" and ends on killing blow on final boss.
Accepted XC2 Money
![[N64] Banjo-Kongzooie [v1.0] 100% Speedrun in 11:58](https://i.ytimg.com/vi/gBOFGrKhAl4/hqdefault.jpg "[N64] Banjo-Kongzooie [v1.0] 100% Speedrun in 11:58
PB as of 4/9/2023. Played on original N64 Hardware via EverDrive 64.
This was done on the Day 1 patch of Banjo-Kongzooie Revamped!
On 3/20/2023, GloriousLiar released the new revamped patch for Banjo-Kongzooie. You can watch GloriousLiars trailer for Banjo-Kongzooie here: https://www.youtube.com/watch?v=kHHnXSOh1Zs
100% in this romhack, much like other romhacks that GloriousLiar has released, includes filling out the Totals screen, which can be seen inside of Banjos House.
The totals are as follows:
5 Banana Coins
15 Jiggies (Golden Bananas)
250 Coloured Bananas
Things that I skip in this run:
The Dive Barrel Training Barrel, found in Mumbos Skull. The move is not displayed on the Totals screen, nor is it necessary to collect everything.
This was a near perfect run. I have no complaints. I wanted sub 12, and now Ive gotten it.
I may be done with running this romhack for now. This was by far the most important time for me to achieve, and now that Ive gotten it I think Im happy with my contributions to getting more eyes on Banjo-Kongzooie.")
![[Seizure Warning] Alternative Source Array Warps](https://i.ytimg.com/vi/i3Y9HO2BfpQ/hqdefault.jpg "[Seizure Warning] Alternative Source Array Warps
Name not final. This is the only proper name I can think of right now that accurately explains whats happening without coming into conflict with what is already known (ie: origin warps can be done on vines, trees, poles, etc. calling this vine warping, though accurate, is not always true.)
Since Vines are contained in the Object Model 1 Array, they have 2 bone array structures, just like your character. As you likely know, weve already been able to take advantage of this in terms of Telegrab and Tree/Polewarping. Under certain circumstances, these 2 arrays can be vastly different instead of (very close to) the same, which they are normally meant to be.
When Object Model 1 Array Objects are loaded, they only have 1 of their bone arrays populated, the other bone array is populated on the 2nd visual frame when they are loaded. By having TBS/Void (Instrument, Tag Barrel, Pause Cancel) active, we can prevent objects from having their second array populated when we load them by entering their range + having them on camera.
An example of the bone arrays of a vine in Training Grounds:
Array 1:
Stored X1: 0
Stored Y1: 0
Stored Z1: 0
Array 2:
Stored X2: 1673
Stored Y2: 300
Stored Z2: 1190
Note how one of the arrays is zeroed out. This is a result of having (Pause Cancel) Void active. The model is never actually shown, so the bone arrays never update. The largest effect of this is jumping on the vine will cause your character to warp to each of the Vines Bone Arrays, alternating each visual frame, which is why you get the visuals that you see in the video.
Jumping or dropping off the vine can send you to different locations, just like with Tree/Polewarping. The difference here is that the X and Z of both locations are taken from the Vines Bone Array (depending on what frame you leave the vine), and the Y value is taken from your characters Current Location.
One of the stranger things about this is how your characters Y Value is changing each visual frame while on the Vine. Its either normal (where your character actually is on the vine) or it becomes a number between the range of -76.25 and -80 inclusive. This negative Y value is directly influenced by how far you have climbed up the vine. We dont currently know why it always falls between those numbers and nothing about that range is very apparent at the time of writing.
We also dont currently know why the camera takes the path that it does. Observation shows its roughly the same path everytime, influenced by where you start the warp.")
