Determining the start and end frames of a run

This guide is for moderator use, but it can also be used by the runner to cross-reference the moderator's measurements.

# Start Frame

## First Actual Movement

For runs where time starts when the Prince *starts* moving, the starting frame is simply the first frame after the Prince has visibly begun to move. Note that idle animations and jumping in place do not count as movement.

The only exception to this - as explained in the rules - is if the Prince starts moving during the white screen when loading a save. In that case time starts when the Prince is *able to* move.

## First Potential Movement

### New Game

For runs where time starts when the Prince is *able to* move and are started from a new game, the starting frame is simply the first frame of visible gameplay after the starting cutscene finishes.

### Load Game

For runs where time starts when the Prince is *able to* move and are started by loading a save, determining the starting frame is not as straightforward. This is because time starts during a completely white screen so no cues in the video can be observed to determine the exact moment the Prince is able to move.

Instead, a cue from just before the run starts is used, and then a consistent offset is applied to determine the starting frame. Specifically, whatever is the first frame on which the loading screen starts fading to white, we add precisely 44 game frames at 60fps (or 22 game frames at 30fps), and that is the starting frame of the run. If the video framerate is different, then the number of frames should be adjusted accordingly. For example, for a console run that plays the game at 30fps but a video recorded at 120fps, the offset should be 88 video frames, which will translate to 22 game frames at 30fps. If there is any doubt about which of multiple frames should be considered the starting frame (for example if the video framerate is not an integer multiple of 30), then the earliest frame should be used.

Images 1-4 below demonstrate this:

- Image 1: 16:04_60 video time (16 seconds and 4 frames at 60fps) - loading screen hasn't started fading to white yet
- Image 2: 16:05_60 video time - loading screen still hasn't started fading to white
- Image 3: 16:06_60 video time - loading screen has begun to fade to white
- Image 4: 16:50_60 video time - starting frame of the run

![](/static/blob/1n83powz.jpg)![](/static/blob/3nvmwq8n.jpg)![](/static/blob/dz4w2rke.jpg)![](/static/blob/wzxj5lde.jpg)

In practice, this starting point is about 1-2 60fps frames before the Prince is *actually* able to move, but nonetheless we set this as the starting point of the run, as a matter of definition. This means that even if it could somehow be proven that for some individual run the Prince was not in fact *able to* move until some frames later, the start of the run will still be defined as this exact frame. In particular, this means that sound, a LiveSplit autosplitter, or any other deductions should not be used to determine the starting frame of the run.

If the game happens to lag during this 44 frame intermission, then the run start will still be defined as the end of this 44 frame intermission - even if the Prince is not able to move for perhaps even several seconds from that point. The way to reason about this is that the run in fact starts on the first frame where the loading screen fades to white, but it starts at a time of negative 44 frames instead of a zero time. So if the game happens to lag while the timer is still negative, the runner will lose time, but this is no different from the runner losing time if the game happens to lag after the timer has turned positive.

# End Frame

The ending frame is simply the first frame in which the cutscene that comes after the run is visibly on screen.

Epilogue All Frescos

1. [Water Tank 1](https://youtu.be/MvpcXxiR-0o?t=288)
    - Note that it is possible to acquire this fresco without it giving any visual or auditory indication that this was done, as shown [here](https://youtu.be/K1jhx0eEgd0).
    - Doing a wallrun to the left from that fissure and then spamming grind immediately seems to always get that fresco, even if there is no visual or auditory indication
    - So in practice, if the player performs a wallrun to the left from that fissure, it should just be assumed that they acquired the fresco, whether there was in-game indication of this or not.
2. [Water Tank 2](https://youtu.be/MvpcXxiR-0o?t=436)
3. [Hammam 1](https://youtu.be/MvpcXxiR-0o?t=700)
4. [Hammam 2](https://youtu.be/MvpcXxiR-0o?t=784)
5. [Garden 1](https://youtu.be/MvpcXxiR-0o?t=1100)
6. [Garden 2](https://youtu.be/MvpcXxiR-0o?t=1141)
7. [Tomb 1](https://youtu.be/MvpcXxiR-0o?t=1684)
8. [Tomb 2](https://youtu.be/MvpcXxiR-0o?t=1805)
9. [Ballroom 1](https://youtu.be/MvpcXxiR-0o?t=2482)
10. [Ballroom 2](https://youtu.be/MvpcXxiR-0o?t=2562)

Epilogue tutorial

https://www.twitch.tv/videos/401435767

Should be good and current. Covers optimal strats and a few backups, explained in as good depth as I could.

Exploits considered major glitches in No Major Glitches runs

This guide outlines all the major glitches that are prohibited in NMG, and gives advice for how to avoid getting your NMG run rejected.

Note that this is **not** a tutorial for how to perform any of the glitches.

For tricks labelled with an **"abuse"** clause, the trick itself is not considered a major glitch, but its abuse is. In practice, this means that the trick may be performed - even intentionally - as long as it is not abused.

**Prohibited major glitches:**

- Corner Clip **(abuse)** ([video](https://youtu.be/mVohXS8hlmc?si=pRNAHYu9O-10SX6L&t=171))
    - Here, abuse means clipping through a wall and staying on the other side of it, or otherwise getting some advantage on the other end of the wall, such as a light seed
    - Clipping through the wall and letting the animation finish, thus immediately popping back out again, is allowed - as long as there was no advantage to being behind the wall such as acquiring a light seed
- Overledge Clip **(abuse)** ([video 1](https://youtu.be/L_trzUIwWxg?si=HbIpvO1JJqYWPHyU&t=35), [video 2](https://youtu.be/sMMGGg2MAMU?si=Zk2jMiP2-bwKOD0K&t=6))
    - Here, abuse means clipping through a ceiling and staying on the other side of it, or otherwise getting some advantage on the other end of the collision, such as a light seed
    - Clipping through the ceiling and letting yourself fall or jumping straight back in-bounds again is allowed
- Jumping from a prohibited Airstep
    - An airstep is any state in which you can jump in an arbitrary direction just before falling
    - Notably, *getting* a prohibited airstep is allowed; it is specifically *jumping* from it that is prohibited
    - Previously, *all* airsteps were prohibited, but as of 18th May 2025, some airstep types are now allowed
    - List of *prohibited* Airsteps:
        - Deload Airsteps (jumping from collision that is no longer loaded) ([video](https://youtu.be/4XOFCX_XDks?si=f-XuLcxS2DdGGqAk&t=23))
        - Corruption Airstep ([video 1](https://youtu.be/bZdae4ciAWQ), [video 2](https://youtu.be/O7ThHfh0MhE?si=xduUlQN7RCeiSrh7&t=36))
            - However, [King's Gate Skip](https://youtu.be/Zx0uwkgqNN8) is allowed even if it has an explicit Corruption Airstep, since it is proven that exactly the same thing can easily be done [without an airstep](https://youtu.be/OEJS4yxYDlg), but it is difficult to distinguish which variant happened
        - Inverted Collision Airsteps ([video](https://youtu.be/nzF5QD9i9Bc?si=UmhDjohhDO3D2TOt&t=18))
            - In this game, collision is asymmetrical: that is, it behaves differently depending on which side you interact with the collision from; for example, approaching a wall from its "correct" side will stop you and prevent you from going through, however when approaching the same wall from the other side, you can simply jump through it; when collision is approached from the "wrong" side, this is referred to as *Inverted Collision* (generally this would be out of bounds); an *Inverted Collision Airstep* refers to getting an airstep state by interacting with inverted collision; this can mean interacting with a floor from below as shown in the video, but it can also mean interacting with a wall from the inverted side, a ceiling from above, or any diagonals in between; in order for an airstep to count as an *Inverted Collision Airstep*, the inverted collision has to be solely responsible for giving the player an airstep
            - Notably, the above three airstep types are commonly referred to as *Ultimate Glitch*
        - Ring Airstep ([video](https://youtu.be/nUGKX3m6jFE?si=dKWk-Y2-LecPfqIH&t=7))
    - List of *allowed* Airsteps:
        - Horizontal Wallrun Airstep ([video 1](https://youtu.be/UNhI76Zr9_A?si=3TbClb5QdhlSDAx7&t=345), [video 2](https://youtu.be/UNhI76Zr9_A?si=mTSDsF9waHj2O0n7&t=171), [video 3](https://youtu.be/L_trzUIwWxg?si=lO5wfi5MUdAlY_iZ&t=45))
            - Video 2 is commonly referred to as a *Slide Airstep*
            - Video 3 is technically not an airstep since we did not fall down, but it illustrates how an airstep there *could look* if the Prince simply went very slightly further and off the collision he is standing on
            - Notably, even though we are standing on inverted collision (i.e. standing on a ceiling), this does not count as an *Inverted Collision Airstep* since the wall itself is not inverted
            - In general, if any kind of horizontal wallrun animation is seen leading up to an airstep, this is a *Horizontal Wallrun Airstep* and is allowed
            - The start of video 3 shows an overledge clip which is not allowed
        - Vertical Wallrun Airstep ([video](https://youtu.be/fJV6Fhg8LOc?si=AQcMw2f1YPznXi3o&t=2491))
            - Similar to the *Horizontal Wallrun Airstep*, if any kind of vertical wallrun animation is seen leading up to an airstep, this is a *Vertical Wallrun Airstep* and is allowed
        - Fence Airstep ([video](https://youtu.be/fJV6Fhg8LOc?si=9PQvMgnAVf8S58I7&t=1632))
        - Overledge Airstep ([video](https://youtu.be/-ufc-Jvuuts?si=NAC-GpnZNKvs1MeF&t=11))
    - While these lists of prohibited and allowed airsteps aim to be exhaustive, in practice it is impossible to prove that they are; thus any airstep types that are not covered by these lists are neither allowed nor prohibited, but instead a decision will be made as and when they get discovered; if you find a new airstep type that is not on these lists, please do not assume that it will be allowed without consulting a moderator
- Virtual ledges/beams/fissures, including:
    - Getting an extension from an unsuccessful ledgewarp ([video](https://youtu.be/uOGNQdYki-o?si=XynCvAZdjFZbShNE&t=200))
    - Virtual fissure in the Windmills ([video](https://youtu.be/QzA3-0Pz49s))
        - *Note:* you can tell that it’s a virtual fissure because you cannot move up/down on it
        - On the other hand, [fissure 1](https://youtu.be/TV7uqfYFwmY) and [fissure 2](https://youtu.be/imyTEGaTH2c) are real and are allowed
        - In practice, this simply means that Windmills Skip 2 via the red plate is prohibited ([video](https://youtu.be/WdopsRZhVrQ))
- Ledgewarp ([video 1](https://youtu.be/uOGNQdYki-o?si=vYbLoUfKK136RfuH&t=19), [video 2](https://youtu.be/dGuAMUh_cvA?si=hvICIMUketMpInjd&t=40), [video 3](https://youtu.be/5ekkPcC_7wA?si=eIR-ZDUe6TsGQlw1&t=14))
- Ledgefall ([video 1](https://youtu.be/Xll2fub4ARY?si=gcPXKBwA-i0TU0Hw&t=11), [video 2](https://youtu.be/yP_Qckv2X-M), [video 3](https://youtu.be/hHr8IAWKsnk), [video 4](https://youtu.be/M7K_QuTG_aQ), [video 5](https://youtu.be/dGuAMUh_cvA?si=ttWu5naUBSanI2Wt&t=74), [video 6](https://youtu.be/YEUEeVbgvG4))
    - (In video 6, the ledgefall allowed us to skip a stagger; [here](https://youtu.be/Ot8rtH3N3zw?si=uSrUdIir0o5w-8GM&t=369) is the same movement without a ledgefall for reference)
    - The ledgefall is prohibited even if no advantage is gained from it, however as per the escape clause in the rules, if you do it by accident and gain no or minimal advantage, your run may still be accepted
- Horizontal Airwalk, including:
    - Airwalking outside the bounds of a beam ([video 1](https://youtu.be/DO8IyiEJFdE?si=EUQv1KhyYcrMYBCR&t=54), [video 2](https://youtu.be/DO8IyiEJFdE?si=X2T2JIPn64YY-clA&t=256))
        - *Note:* getting into an airwalk state and then moving only within the bounds of the beam, as shown [here](https://youtu.be/q9Ew20yBGms), is allowed
    - Snapping back to the corner of a beam after getting into an airwalk state ([video](https://youtu.be/7T6XBXL4rDg))
- Vertical Airwalk outside the bounds of a fissure ([video](https://youtu.be/BgwAB1D2Rww?si=u6EyXYco9f1t8xKf&t=8))
    - This vertical airwalk is achieved by grabbing that fissure from an angle
    - *Note:* getting into a vertical airwalk state and then moving only within the bounds of the fissure is allowed, as long as this is not abused to achieve something that would otherwise not be possible from that fissure

- Elika Clip ([video](https://youtu.be/e6nnUIGDfQ0?si=7Qlikz7sCrYoxBT9))
- Airsink ([video](https://youtu.be/awdgy7EveqA?si=VFN8fQbJtXvP7suC))
- c storage **(abuse)**, including:
    - Entering the first fight in Warrior’s Fortress while being near corruption ([video](https://youtu.be/9MmyARC8FtE?si=V4hxqhaq3JhOtwHp&t=45))
        - If you do this by accident (can easily happen), the best way to get rid of your c storage is by reloading the game after the fight, as shown [here](https://youtu.be/yowQI864Ia4?si=MxWMcfJe7KUliwvW&t=1178), and your run will remain valid (it’s about 1 second slower than not reloading the game)
    - Entering the final phase of the Alchemist fight in the Observatory while being near corruption ([video](https://youtu.be/uJJuKMM7Pfs?si=8zLRF-edVqBu91OP))
    - Fast travelling to a different level while in gas ([video](https://youtu.be/FPqV8OkW8x8?si=uAGCBfsdPGroF-yt))
    - *Tip:* If you do any of these by accident, your biggest enemy is not the moderator, but the game; abusing this glitch typically involves deathwarping somewhere very far away, so in practice this is a runkiller anyway, as shown [here](https://youtu.be/ArTBgfm9ASk?si=RsQJAB4QRJf2auHq&t=5859)
- Blue Mirror ([video](https://youtu.be/tK8PbtGNVLI))

**Other notes:**

- As of 8th September 2024, First Fight Skip via AI Break is *allowed* ([video](https://youtu.be/rTyilLlKt9Y?si=j3-gSSGhigG2q9hO&t=524))
- As of 18th May 2025, the Drop Glitch is *allowed* ([video](https://youtu.be/KmEw0za96qg?si=O6Yun1Zq5P5WAiFo&t=182))
- As of 18th May 2025, certain Airstep types that were previously prohibited are now *allowed* (see list above)
- As of 18th May 2025, Dashing from a Combat Airstep is *allowed* ([video](https://youtu.be/XIfks_lGw5o?si=Yo_M3oLLdcDsehwJ&t=11))

If you have any doubts about whether a trick is prohibited in NMG, please consult a moderator.

Getting the reset camera function for PoP:2008 on keyboard (by GMP)

1.) Download and install the program - https://sourceforge.net/projects/vjoy-controller/files/latest/download

2.) Go to 'Settings --> IO Devices'.

https://i.postimg.cc/J4fhK2bc/EO6IOrc.png

3.) Go to the 'Virtual' tab and click 'Setup --> Xbox 360 Gamepad'.

https://i.postimg.cc/3x2xqF1M/X7qFDcQ.png

4.) If you see the 'Install' button active, then click install. You might be prompted to reboot your PC.

5.) If you see the 'Install' button greyed out, then click 'Configurate'. You should see a 'Plug In' option. Click it. Your window will look something like this:

https://i.postimg.cc/0Nxy1KXz/yDfu4vc.png

6.) If nothing happens when click 'Plug In', click uninstall and re-install the virtual bus so that its compatible with this program. You may have to reboot your PC a couple of times in the process.

7.) Once you are done, you should see a 'vXbox 1' device in the 'Virtual' tab. Your device is now ready. Its time to bind the required control to your keyboard.

8.) Go to 'Settings --> Controls'. Then press 'Bind --> Create'.

https://i.postimg.cc/jjXdxqBZ/MrZdtRj.png

9.) Create the following bind and click 'OK'. The keyboard key can be anything of your choice, I have chosen 'X' here as that is the default one in the other PoP games.

https://i.postimg.cc/XJYNpSb3/1SCnCmU.png

10.) Create another bind like so, (make sure to have the same keyboard key for both the binds):

https://i.postimg.cc/WzD2wGzH/fk5NLZt.png

11.) Once you are done, your binds should look like this:

https://i.postimg.cc/rsvqnDtF/XuVMZ9k.png

12.) Now there is one final step. In the main window, go to 'Main --> Run'

https://i.postimg.cc/mZqZ256f/HIwny9e.png

The joystick image in the application should turn green like this:

https://i.postimg.cc/ncDFsG6s/TwyWtcq.png

Thats it, now you can use the reset camera function in the game without even having a controller plugged in to your PC.

How to play Prince of Persia in windowed mode (using dxwnd)

- Download "dxwnd" from http://sourceforge.net/projects/dxwnd/ unpack it and start dxwnd.exe

- Right-click on the white space in dxwnd and select "Add". Make sure "Path:" links to the PrinceofPersia_Launcher.exe; after selecting that .exe the path should look like that C:\Program Files (x86)\Steam\Steamapps\common\Prince of Persia\PrinceofPersia_Launcher.EXE, this obviously differs if you play the GOG version or if you installed the game somewhere else. Similarly, make sure "Launch:" points to the same EXE. 
Picture of dxwnd for reference:

![](/static/blob/rz25pmdz.png)

- Set your window size at the bottom, e.g. 1280x720. This should be the same as your resolution in the game config (see below).

![](/static/blob/kzwr6pre.png)

- If you don't want a dxwnd banner to appear every time you launch the game, tick "No banner". You can keep the rest of the settings as default.

- Go to the Video tab and under Screen resolution select HD (16:9) if you are playing the game in a 16:9 ratio (e.g. 1280/720 = 16/9 = 1.78)

![](/static/blob/qzp7ov1z.png)

- Go to the Mouse tab and turn mouse clipper off

![](/static/blob/3ekxm5kn.png)

- Click "Ok"
- Now start the game through dxwnd or through Steam. The game should now open in a window.

P.S. If the game still starts in fullscreen, the universal fix is to launch dxwnd as admin.

[edited by Smath on 25/07/2024]

Load chunks that this game is divided into

# **Overview**

![](/static/blob/kzwry5ye.png)



# **Internal Names of Each Chunk**

https://docs.google.com/spreadsheets/d/1XQr8yRIOTDr_pLRy5_L-IeMYa6UlgSMMyYOaiHoK7DA/edit?usp=sharing

Setting Up the Autosplitter

1.) Setup Livesplit: http://livesplit.github.io/downloads/

2.) Right click anywhere in Livesplit and choose **Open Splits -> From File...**
https://i.imgur.com/MZNnn1B.png

3.) Open one of the splits files found in the **Resources** tab of this site (for the lazy: https://www.speedrun.com/splits/SoTSplits_y3b6y.rar )

4.) Right click anywhere in Livesplit and choose **Edit Splits**
https://i.imgur.com/Gfn4QAk.png

5.) Underneath the **Attemps** box ensure that the **Activate** button is clicked. 
https://i.imgur.com/mb2p54f.png

6.) Enjoy. The script auto-starts, auto-splits, and auto-detects category based on your splits file. 





Side Notes: The name of each split is unimportant. If making your own splits, you need to ensure you have the number of splits the script is expecting, and that the category and subcategory (found under the 'Additional Info' tab) are set correctly. If you discover a bug please notify me (Samabam#8840) on Discord so I can fix it.

Tutorials/Strats

Various Tutorial and/or Strat playlists by Community Memebers:

Smathlax Tutorial: https://www.youtube.com/playlist?list=PLZawIL4qSego-u1G9-44PZI-Z-BJb-9is

Smathlax Strats: https://www.youtube.com/playlist?list=PLZawIL4qSegrR96eXDjfVv_ssXPgRzpXo

Smathlax various unlisted videos: https://www.youtube.com/playlist?list=PLZawIL4qSegons77JDa_OMOucsHL0lqW3

Samabam Tutorial: https://www.youtube.com/playlist?list=PLZHs-k4KfS0d3jEgDz8VTDDiyF7bp7Lp4

Samabam Strats: https://www.youtube.com/playlist?list=PLZHs-k4KfS0c2bBTzL8XHWHA_1luegA5y

Vynneve: https://www.youtube.com/playlist?list=PLyqX56SrF2nMtv8nLzw4jZugXtPZq6b-J

Drep: https://www.youtube.com/playlist?list=PL1Jn1IBY_0Aa85Ql9WHBCY0TnhA3DvBhc

GMP compilation: https://www.youtube.com/@GMPranav/playlists?view=50&shelf_id=7 ("2k8 stuff" at the bottom)

Updating Autosplitters (Pull Requests)

1. First step, make a github.com account.

2. Find the asl script you want to update. (This should be listed in Resources here on src).

3. Click on the edit pencil seen here:
![](/static/blob/xz0p68el.webp)

4. Add your desired changes and click Commit Changes.

5. Now travel to the Pull Request tab and click "New pull request"
![](/static/blob/kzw02qeq.webp)

6. Click "Create pull request" to send your changes to the owner for review.

In the event a script owner leaves the community, upload your script to your own github account. Copy a link to the raw file and make a pull request of the autosplitters code, placing your raw link where the former script owner's used to be.
https://github.com/LiveSplit/LiveSplit.AutoSplitters/blob/master/LiveSplit.AutoSplitters.xml

Working out in-game time for runs with cinematic cutscenes

As per the rules, runners are allowed to delete certain cinematic cutscenes, which saves them some time. If a run is done without deleting the cutscenes, the final runtime should subtract the amount lost due to having the cutscenes from the gross run time.

This guide can be used to calculate how much time should be subtracted. Note that if you are a runner and you submit a run without deleting the cinematic cutscenes, you are not expected to perform this calculation yourself, as a mod will do it for you. However this guide can be used to cross-reference the mod's calculations.

The time difference between deleting and not deleting each cutscene is as follows:

- **[Desert Exit Vision](https://youtu.be/S0vBwIpKhYw?si=RDPomFqizLRo3Q22&t=3731)**: 10.550s
- **[Plate 2 Exit Vision](https://youtu.be/S0vBwIpKhYw?si=jpf6aDlY8pzbPF5k&t=3435)**: 19.100s
- **[Plate 3 Exit Vision](https://youtu.be/S0vBwIpKhYw?si=5-i_9aFOGqrCkKWC&t=3603)**: 2.400s
- **[Plate 4 Exit Vision](https://youtu.be/S0vBwIpKhYw?si=3poXqmStGjCpwUE-&t=6914)**: 11.683s
- **[Resurrection Vision](https://youtu.be/S0vBwIpKhYw?si=HWGiSWpIM0rEClgm&t=8288)**: 5.450s
- **Total:** 49.183s

If a run skips any cutscenes or watches them more than once, the appropriate timings should be added together. For example, if a runner who hasn't deleted the cinematic cutscenes skips the desert exit vision, watches the plate 2 exit vision twice (perhaps by mistake due to saving/reloading taking them back to before they had watched it), and watches all other cinematic cutscenes once, then the time that should be subtracted from their run is as follows: 19.100s + 19.100s + 2.400s + 11.683s + 5.450s = 57.733s.

Raw data and source material from which these numbers were derived:

```
source video with cutscenes: https://youtu.be/S0vBwIpKhYw?si=N8yW7CjNrE-YPY8i
source video without cutscenes: https://youtu.be/fJV6Fhg8LOc?si=KwiYrKYw5Ahc4dg2

vision end counts as first non-black frame of following cutscene
delta is rounded in the negative direction to the nearest frame (60fps)

desert exit vision:
https://youtu.be/S0vBwIpKhYw?si=RDPomFqizLRo3Q22&t=3731
3762.757 - 3735.026 = 27.731
3607.050 - 3589.863 = 17.187
delta = 17.187 - 27.731 = -10.550

plate 2 exit vision:
https://youtu.be/S0vBwIpKhYw?si=jpf6aDlY8pzbPF5k&t=3435
3466.257 - 3443.173 = 23.084
3323.901 - 3319.916 = 3.985
delta = 3.985 - 23.084 = -19.100

plate 3 exit vision:
https://youtu.be/S0vBwIpKhYw?si=5-i_9aFOGqrCkKWC&t=3603
3640.502 - 3610.037 = 30.465
3495.668 - 3467.598 = 28.07
delta = 28.07 - 30.465 = -2.400

plate 4 exit vision:
https://youtu.be/S0vBwIpKhYw?si=3poXqmStGjCpwUE-&t=6914
6940.738 - 6921.141 = 19.597
6662.029 - 6654.103 = 7.926
delta = 7.926 - 19.597 = -11.683

resurrection vision:
https://youtu.be/S0vBwIpKhYw?si=HWGiSWpIM0rEClgm&t=8288
8330.134 - 8296.608 = 33.526
8004.697 - 7976.605 = 28.092
delta = 28.092 - 33.526 = -5.450

total delta = -49.183
```

toca

Vynneve

EmeraldAly

Samabam

Smathlax

Prince of Persia 2008

Xbox 360

drepfawx

Standard

No Major Glitches

Any% Hacked

Hacked

Any%

All Frescos

Gameplay Restrictions

Ruleset

Drop Glitch

Completion Requirements

As you may have heard Twitch has announced a [hard 100‑hour cap](https://help.twitch.tv/s/article/video-on-demand?language=en_US#storage) on every channel’s combined Highlights starting from 19 May 2025. As a result, effective yesterday (21 April 2025) runs with a Twitch video as submission VOD 

Имя	Автор
Determining the start and end frames of a run	Smathlax 2 months ago
Epilogue All Frescos	Smathlax 14 days ago
Epilogue tutorial	EmeraldAly 6 years ago
Exploits considered major glitches in No Major Glitches runs	Smathlax 1 month ago
Getting the reset camera function for PoP:2008 on keyboard (by GMP)	toca 2 years ago
How to play Prince of Persia in windowed mode (using dxwnd)	Samabam 6 years ago
Load chunks that this game is divided into	GMP 10 months ago
Setting Up the Autosplitter	Samabam 6 years ago
Tutorials/Strats	Vynneve 3 years ago
Updating Autosplitters (Pull Requests)	Samabam 5 years ago
Working out in-game time for runs with cinematic cutscenes	Smathlax 10 months ago