Florida, USAYes you would, but being consistent in all cases was the theme for our rules.
GENERAL
Emulation via Xenia for Xbox 360 is allowed.
Posted runs achieved date will use the same date as the videos upload date.
Runs must be played in real time. Using Xenia's time scalar feature to alter the speed of runs is prohibited. Having an FPS counter viewable in your recording is recommended to help resolve discrepancies, but not required.
The community edition of Goldeneye XBLA is permitted. It is advised to not use this version unless necessary. Runs may be rejected if any notable advantage or difference is discovered at any point during the run, including after the upload date.
Advantage examples include; altered guard/enemy pathing or animations, lower health on enemies/NPCs, faster doors, objective skips of any kind, geometry differences, differences in loading of walls/doors/objects/items, or any other difference that leads to a time save.
Differences in text on screen/visual differences that are purely aesthetic are permitted.
Runs that use the community edition must be labeled as such in the video title (CE or Community Edition) and follow all rules present in the original version.
VIDEO AND AUDIO
Video source is from either capture card or capturing software (OBS, Xsplit, Action, Shadowplay, twitch vods or highlights, etc).
Video resolution is at least 480p and frame rate is at least 25 FPS with no excessive stuttering, slowdowns, or frame drops at any point during gameplay.
If runs appear spliced in any way due to frame drops or slowdowns/speedups, the run will be rejected.
In-game sound effects are audible on the video and are not significantly delayed more-so than normal Xenia emulation. Music can be on or off.
The end screen must be shown long enough to tell what the final time is. The end time must display for at least one frame.
The video must not be too dark or too bright to see the run clearly. Please be careful adjusting the gamma setting as this can alter visual clarity.
Recordings of runs must include the first frame of the opening cut scene (black screen fading in) or be continued onward from the in-game menu.
INPUTS
Any method which automatically sends inputs is banned.
You cannot use any other input method (mousewheel, touchpad, controller shaking, or gyro based inputting) to assign any sequence of in game actions to a single human input.
No macros or scripts are permitted, where 'macros or scripts' includes any method of assigning a sequence of inputs to a single button/key.
Re-binding inputs or assigning different simultaneous inputs to the same button/key is allowed (e.g. LS-Up + Dpad-Up bound to a single button/key or RT + Y to a single button or key to backswitch).
Binding mousewheel up and/or down to one inputtable action (e.g. fire) is allowed.
Mouse & Keyboard runs should have ge_always_allow_inputs set to false to disable camera movement, firing, or any other actions during cutscenes.
Camera movement during an ending cutscene is permitted, however it is NOT allowed during an opening cutscene.
WARPS
Using (whether accidental or not) low FPS/excessive lag/PC performance drops/graphical style changes to warp through ladders, boxes, doors, walls, cracks, guards or any other obstacle is banned in the default category.
If a warp occurs this way, then the player should go back to where they were before the warp so there isn't any advantage accidentally gained. This applies to both RTA speedruns and individual level runs.
Everyone uses a aiming cursor so yeah its allowed, you can use a dot in any way you like.
Swapping between graphics is allowed but be careful as it can cause lag spikes and can impact if a run is accepted or not if tons of frames are lost etc. Most players don't swap between them for this reason.
You can use any version you like.
