ZSR Forums
July 25, 2024, 01:29:15 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: ZSR Forums are back - read only!
   Home   Help Search Members Login Register  
Pages: [1]
Author Topic: Improving the Wrong Warp pages  (Read 7503 times)
Ultimate Mega Guay

Posts: 901

Wrong warp expert

« on: July 30, 2013, 09:41:42 AM »

So recently I've been trying to improve the wrong warp section on the site. I've managed to put out a more complete explanation on what I know about wrong warping, added a table that shows what scenes have a fixed cutscene that they'll play when wrong warped to, and reworked the Entrance Index Table (now just entrance table) to simplify the table a bit, and added in the human readable descriptions for all the entrances that Ocarinabot uses.


I don't like the name "Warps by scene" but I don't really know of a better name to call it though. Also, is anything a bit confusing / excessive on  either page that can should be fixed?

Also, the next page I plan on working on tomorrow is either the common wrong warps page or the wrong warp page.


The common wrong warps page really needs explanations for setting up things like Ganondoor and ww to GTG, so if anyone has any good tutorials to link or somebody write up a tutorial that'd be cool.

Edit: When I work this out, fix links

« Last Edit: January 11, 2014, 11:12:58 AM by mzxrules » Logged

Quote from:  Leigh Rogers
This is art because the music is classical music, and the graphics are done with a pen. The story is something about a woman. I could not understand much of this to be honest, which makes it even more likely to be an art.
Site Editor
Special Guay

Posts: 269

WWW Email
« Reply #1 on: July 30, 2013, 04:05:23 PM »

Out of curiosity, why are there pages about cutscene skips under the Wrong Warp drop-down menu? I know some CS skips involving death result in a wrong warp, but unless the pages are focusing specifically on those wrong warps (which is what the Common Wrong Warps page is for, I presume) shouldn't they be moved to a page that is specifically designated for cutscene skips?

Rescue Tetra before FF1: is new to me. Did you just find this out?
Site Editor
Special Guay

Posts: 276

« Reply #2 on: August 26, 2013, 08:52:18 AM »

It seems pointless to put Forest, Water, Shadow, and Spirit CS skips on separate pages for each. They are the same glitch, and it clutters the wrong warp page (they're hardly even wrong warps to begin with). Also, those pages seem to explain the CS skips in terms of their setups, which seems weird to me since there are multiple setups for different situations, and setups are subject to change or improve. Would it not be better to organize the pages more like:

-explain what the glitch is, what it does, and a general, brief description of how it works
-explain how you can use death, timers, or FW
-explain that doing a CS skip from certain dungeons creates a wrong warp effect (link to wrong warp page)
-this may not be necessary and could probably be omitted, but explain in more detail what has to be done to get the glitch to work (must let a timer run out just as the blue warp is done animating)
-these should be written in bullet point format, rather than a paragraph
-should include multiple setups, especially if some have advantages over others (i.e. timer CS skips don't require low health, and you can collect the heart from the dungeon boss)
-gives a full technical explanation of the glitch in much greater detail

Much of this format could be applied to non-wrong warp pages as well, like the "Bottle on B" page. I'm not a fan of how that page is laid out. It doesn't very well explain bottle duplication over B (is there even a bottle dupe page on ZSR?), and the bottom of the page doesn't seem like it belongs on the bottle B page. It's simply explaining methods of bottle duplication.
« Last Edit: August 26, 2013, 11:25:34 AM by nathanisbored » Logged
Pages: [1]
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.20 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!