fceux/web/help/OverviewofIncludedScripts.html

131 lines
6.2 KiB
HTML

<html>
<head>
<title>Overview of Included Scripts</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="generator" content="HelpNDoc Personal Edition 3.8.0.560">
<link type="text/css" rel="stylesheet" media="all" href="css/reset.css" />
<link type="text/css" rel="stylesheet" media="all" href="css/base.css" />
<link type="text/css" rel="stylesheet" media="all" href="css/hnd.css" />
<!--[if lte IE 8]>
<link type="text/css" rel="stylesheet" media="all" href="css/ielte8.css" />
<![endif]-->
<style type="text/css">
#topic_header
{
background-color: #EFEFEF;
}
</style>
<script type="text/javascript" src="js/jquery.min.js"></script>
<script type="text/javascript" src="js/hnd.js"></script>
<script type="text/javascript">
$(document).ready(function()
{
if (top.frames.length == 0)
{
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
top.location.href = "fceux.html?" + sTopicUrl;
}
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
{
top.FrameTOC.SelectTocItem("OverviewofIncludedScripts");
}
});
</script>
</head>
<body>
<div id="topic_header">
<div id="topic_header_content">
<h1>Overview of Included Scripts</h1>
<div id="topic_breadcrumb">
<a href="LuaScripting.html">Lua Scripting</a> &rsaquo;&rsaquo; </div>
</div>
<div id="topic_header_nav">
<a href="LuaScripting.html"><img src="img/arrow_up.png" alt="Parent"/></a>
<a href="LuaBot.html"><img src="img/arrow_left.png" alt="Previous"/></a>
<a href="FAQGuides.html"><img src="img/arrow_right.png" alt="Next"/></a>
</div>
<div class="clear"></div>
</div>
<div id="topic_content">
<p></p>
<p>(written by FatRatKnight)</p>
<p><br/></p>
<p><span class="rvts17">Overview of Included Scripts</span></p>
<p><br/></p>
<p>Many users of FCEUX do not investigate the <span class="rvts32">luaScripts</span> folder, or, for that matter, ignore lua scripting altogether. The purpose of this text is to let users know that knowing how to <span class="rvts29">create</span> lua scripts is not a requirement in <span class="rvts29">using</span> them. Indeed, there are several scripts that, if you just load them, will explain themselves enough that you don't need to know how to program at all in order to use them. Besides, they shouldn't need to be re-programmed anyway if you are to use them, for if they needed programming experience just to be used, their existence is largely defeated by that very fact!</p>
<p><br/></p>
<p>FCEUX itself is a program that you load. Our amazing programmers did all the work already so you don't need to program up your own FCEUX to run it, do you? The same can be said of these scripts.</p>
<p><br/></p>
<p>So, open the <span class="rvts32">luaScripts</span> folder and actually take the time to look at some of these scripts. You may use a text-editing program to open these if you so wish.</p>
<p><br/></p>
<p><br/></p>
<p><span class="rvts36">General Purpose scripts:</span></p>
<p>These may be used with any game freely. Else, the "General" part of General Purpose doesn't apply.</p>
<p><br/></p>
<ul style="text-indent: 0px; margin-left: 24px; list-style-position: outside;">
<li>Mutlitrack2.lua &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp;Tracks future input that FCEUX promptly loses on state-load, for <a class="rvts18" href="ToolAssistedSpeedruns.html">TAS</a></li>
<li>Subtitler.lua &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp;For easier use of FCEUX's built-in subtitles for <a class="rvts18" href="fm2.html">.fm2</a> files</li>
<li>Rewinder.lua &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp;A way to rewind backwards by pressing a button</li>
<li>Sprites.lua &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp;Sprite debugging highlights all sprites on screen, with mouse hover to inspect.</li>
</ul>
<p><br/></p>
<p><br/></p>
<p><span class="rvts36">Game Specific scripts:</span></p>
<p>These scripts are built specifically for certain games. Attempting to run them while you've loaded another ROM will likely cause undesired results. The meaning of "undesired results" in this case are things like crashing the game, causing it to glitch in other ways, or having nonsense numbers and pixels show up.</p>
<p><br/></p>
<ul style="text-indent: 0px; margin-left: 24px; list-style-position: outside;">
<li>BugsBunnyBirthdayBlowout.lua</li>
<li>Excitingbike.lua</li>
<li>Excitingbike-speedometeronly.lua</li>
<li>Galaxian.lua</li>
<li>Gradius-BulletHell.lua</li>
<li>Machrider.lua</li>
<li>MegamanII-LaserEyes.lua</li>
<li>PunchOutChallenge.lua</li>
<li>PunchOutStats.lua</li>
<li>PunchOutTraining.lua</li>
<li>SMB2U.lua</li>
<li>SMB3-RainbowRiding.lua</li>
<li>SMB-AreaScrambler.lua</li>
<li>SMB-CompetitionRecorder.lua</li>
<li>SMB-HitBoxes.lua</li>
<li>SMB-Jetpack.lua</li>
<li>SMB-Lives&amp;HPDisplay.lua</li>
<li>SMB-Mouse.lua</li>
<li>SMB-Snow.lua</li>
<li>TeenageMutantNinjaTurtles.lua</li>
<li>tetris.lua</li>
</ul>
<p><br/></p>
<p><br/></p>
<p><br/></p>
<p><span class="rvts36">Auxiliary Functions scripts:</span></p>
<p>These scripts exist to make the life of programmers easier. As such, if you don't program, you may skip over these scripts. These should not be run by themselves, for they themselves probably don't have any programming to do any work usefully. It's like giving yourself a clip of bullets with no gun to use.</p>
<p><br/></p>
<ul style="text-indent: 0px; margin-left: 24px; list-style-position: outside;">
<li>FRKfunctions.lua &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp;To aid with input.get, display, and registers</li>
<li>x_functions.lua</li>
<li>shapedefs.lua &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp;Contains a few shape-drawing functions</li>
</ul>
<p></p>
<p class="rvps2"><span class="rvts13">Created with the Personal Edition of HelpNDoc: </span><a class="rvts14" href="http://www.helpndoc.com/help-authoring-tool">Single source CHM, PDF, DOC and HTML Help creation</a></p>
</div>
<div id="topic_footer">
<div id="topic_footer_content">
2016</div>
</div>
</body>
</html>