文件列表:

Unreal-Aim (0, 2004-12-23)
Unreal-Aim\doc (0, 2004-12-23)
Unreal-Aim\doc\license.txt (14923, 2004-07-07)
Unreal-Aim\src (0, 2004-12-23)
Unreal-Aim\src\Dialog.rc (1536, 2004-12-22)
Unreal-Aim\src\HLS.cpp (1289, 2004-04-17)
Unreal-Aim\src\HLS.h (355, 2004-12-18)
Unreal-Aim\src\icon.ico (3262, 2004-12-20)
Unreal-Aim\src\image.bmp (51536, 2004-12-22)
Unreal-Aim\src\Main.cpp (21668, 2004-12-23)
Unreal-Aim\src\Main.h (283, 2004-12-20)
Unreal-Aim\src\Resource.h (856, 2004-12-19)
Unreal-Aim\src\ScanProcess.cpp (3089, 2004-12-22)
Unreal-Aim\src\ScanProcess.h (2292, 2004-12-22)
Unreal-Aim\src\Settings.cpp (3873, 2004-12-19)
Unreal-Aim\src\Settings.h (188, 2004-12-18)
Unreal-Aim\src\Structs.h (1754, 2004-12-22)

____________________________ | | | Unreal-Aim v1.03 readme | | http://unreal-aim.sf.net | |____________________________| -= Table of Contents =- 1: Unreal-Aim 1.0: What is it? 1.0.0: Description 1.0.1: Licensing 1.1: Requirements 1.1.0: Computer 1.1.1: Game 1.2: Releases 1.2.0: Change Log 1.2.1: Planned 1.3: More Info 1.3.0: Websites 1.3.1: Suggestions (feedback) 1.3.2: Contact Information 2: Usage 2.0: Basic Usage 2.0.0: How to use Unreal-Aim 2.0.1: Hotkeys 2.1: Settings 2.1.0: Game Resolution 2.1.1: Hotkey Prefix 2.1.2: Targeted Color 2.1.3: Sensitivity 2.1.4: Scan Size 2.1.5: Scan Resolution 2.1.6: Scan/Fire Speed 2.1.7: Mouse Fire Button 2.2: Adjusting mouse sensitivities for overshooting/undershooting 2.3: Skins & Textures 2.3.0: How to change them 2.3.1: What to change on them 2.3.2: What to change them to 2.4: Calibration Mode 2.4.0: What it is 2.4.1: Why it's useful 2.4.2: How to use it 2.5: Ethical Use & Disclaimer 3: Notes 3.0: Documentation 3.0.0: Readme 3.0.1: License 3.0.2: FAQ 3.1: Translations 3.1.0: Current Translations 3.1.1: Future Translations 3.2: Advantages of Color Sensitive Aimbots 3.3: The history behind Unreal-Aim 4: Credits & Thanks NOTE: You can jump to a particular section by pressing Ctrl+F (or selecting Find from the menu) and typing in the name and/or numbering of the section you want to jump to. -= The Readme =- 1: Unreal-Aim This is the readme for Unreal-Aim v1.03. Please read it in its entirety. Note that sometimes Unreal-Aim is also referred to as "the aimbot" or "the bot". I am not talking about a separate program unless otherwise specified. 1.0: What is it? Unreal-Aim is what is known as a "Color Sensitive Aimbot", CSA for short. It is an Open Source project freely available for download from its project page at SourceForge. It is designed to work with First Person Shooter (FPS) games only. 1.0.0: Description Unreal-Aim, like all other CSAs, works by searching the screen for certain colors, targeting them via the mouse, and firing. It works only if the user is able to modify the textures of the players in the game by either changing the files locally or "hooking" them with another program. See section "2.3: Skins & Textures" for more details on this. 1.0.1: Licensing Unreal-Aim is released under the GNU General Public License. You should have received a copy of it contained within the same compressed archive as this readme, named license.txt. In accordance with the terms set forth by the GNU GPL, Unreal-Aim's source code is freely available for download to anyone. Binaries are also provided as a means of faster distribution to those who are not interested in the source code, but would like to use Unreal-Aim all the same. 1.1: Requirements Unreal-Aim has separate requirements for the computer and the FPS game being played. See below for details. 1.1.0: Computer Unreal-Aim requires such a minimal amount disk space, it's not worth mentioning. However, the processing requirements are a different story. Unreal-Aim can require such a tiny amount of processing power it's virtually unnoticeable, or it can require so much that your computer slows down to a crawl. It all depends on the settings you choose, so choose them wisely. See section "2.1: Settings" for more details about the various settings and their effects on processing speed. 1.1.1: Game To work with a particular FPS game, the bot has only one requirement. You have to be able to edit or hook the skins/textures of players in the game you wish to use Unreal-Aim in. This is described in more detail in section "2.3: Skins & Textures". 1.2: Releases As with most programs, Unreal-Aim has multiple releases, and will continue to have releases as long as the authors feel it is necessary or that there is room for improvement. At the time of this readme's writing, the current release is v1.03, but future releases could come out at any time without notice. The best place to check for the latest release is the website. See section "1.3.0: Websites" for more information. 1.2.0: Change Log Unreal-Aim has gone through many changes since its initial build, v1.00. Here is a log of the changes that have taken place. Note that for v1.03, Qoole has joined the development team, and changes that have been made will contain the name of the member responsible for them in brackets. v1.00: (Private) Original build. No changes were made to the source. v1.01: (Private) Support for many more resolutions was added. More color choices were added in order to allow for adjustment of the sensitivity of the aimbot. You can now get as close as you want to a target without the aimbot locking up your computer (before aimbot lagged or froze the computer when too many pixels were targeted). A major increase speed and a slight decrease in memory were achieved, resulting in the aimbot being able to run MUCH more efficiently than before. Scan process has been optimized to use less processing power and less memory. This is the main reason for the drastic increase in speed mentioned on the previous line. The aimbot will now center the mouse over the targeted pixels, then fire, rather than centering on each targeted pixel and firing. New Option: Scan Area - Allows you to set the size of the area you want to scan. New Option: Scan Resolution - Allows you to set the resolution of the scanned pixels in the scanned area. New Option: Scan/Fire Speed - Allows you to set how often the aimbot scans the screen and fires at targets. New Option: Mouse Fire Button - Allows you to set which button on the mouse the aimbot will fire. v1.02: (First Public Release - July 11, 2004) Minor bug fixes. More efficient memory use. New Option: Hotkey - Alt + F2 toggles "calibration mode" on/off. New Option: Hotkey - Alt + F3 resets calibration to origin (0, 0) [calibration mode must be on]. New Option: Hotkey - Alt + allows you to calibrate the aimbot [calibration mode must be on]. v1.03: (Second Public Release - December 24, 2004) New banner. [RedDeath] Now saves settings to unreal-aim.ini. [Qoole] Sensitivity moved to a separate combobox. [RedDeath] Many more sensitivity levels added. [RedDeath] Sensitivity in now calculated correctly. Note that because of this, sensitivity is now listed as a "NEW" settings feature, since technically in v1.02 sensitivity was not truly a sensitivity adjustment. [RedDeath] Hotkey prefix can now be changed to Alt, Ctrl, or Shift. [RedDeath & Qoole] Hotkey change: Calibration mode on/off is now (HK Prefix) + F9, and reset calibration is now (HK Prefix) + F10. [RedDeath] New Hotkeys: You can now cycle targeted colors by pressing (HK Prefix) + F2, cycle sensitivities with (HK Prefix) + F3, cycle scan sizes with (HK Prefix) + F5, cycle scan resolution with (HK Prefix) + F6, cycle scan/fire speed with (HK Prefix) + F7, and cycle mouse fire buttons with (HK Prefix) + F8. [Qoole] Default change: Calibration mode is now off by default instead of on. [RedDeath] New, higher resolutions added. [Qoole & RedDeath] Maximize window option removed. [RedDeath] Three more targetable colors added. [RedDeath] "None" option added to mouse fire button. [RedDeath] New optimization reduces a lot of redundant processing. [RedDeath] Calibration mode can no longer be turned on/off while the aimbot is off. [RedDeath] Calibration code reorganized. [RedDeath] Scan speed setting now produces an (almost) linear change in speed between settings. Speeds were adjusted as a result. [RedDeath] Scan is no longer a 1:1 ratio. It now matches the ratio of the screen. [RedDeath] Scan size can now be set to "full" and "smallest". [RedDeath] Scan resolution now varies not only with a change of game resolution but also with a change of scan size. [RedDeath] Many more scan resolutions added. [RedDeath & Qoole] Title bar now displays the status of the aimbot (ACTIVE/INACTIVE). [Qoole] Better hotkey numbering and new code for unregistering hotkeys. [RedDeath] 1.2.1: Planned As I stated earlier, future releases are planned and the Unreal-Aim team will continue to release as long as improvements can be made. Some things planned for the next release are: Make the aimbot work in RGB mode instead of HLS mode, or allow the user to set which mode it should work in. Optimize the scan process some more. Better anti-recoil support (no longer use calibration mode for anti-recoil). Allow a mouse button to be used to turn the aimbot on/off if the user should desire to turn the bot on/off in such a way (clicking down the set mouse button turns the aimbot on, and releasing it would turn it off). Allow the aimbot to aim for several colors at once. Allow users to set the speed at which the cursor is pointed toward the target. Add a slight delay to be set between moving the mouse towards a target and firing the mouse. Add "advanced mouse sensitivity calibration" support (allowing Windows mouse sensitivity and game mouse sensitivity to vary independently of one another and still have the aimbot aim accurately). 1.3: More Info Here you can find information on the website, how to send feedback, and how to contact the developers currently working on Unreal-Aim about anything else. 1.3.0: Websites The website is the place to go for news updates, releases, screenshots, FAQs, and a whole lot more. The site is hosted for free thanks to sourceforge, who also hosts the project files and a related project page. Unreal-Aim's site: http://unreal-aim.sf.net -OR- http://unreal-aim.sourceforge.net Unreal-Aim's forum: http://unreal-aim.zapto.org Unreal-Aim's project page for downloading releases: http://sourceforge.net/projects/unreal-aim SourceForge's home page: http://sourceforge.net 1.3.1: Suggestions (feedback) As with other programs, Unreal-Aim can't grow without feedback from its users. However, I ask that you do a few things before immediately sending feedback. First, get to know the aimbot, try different textures/skins, and tweak the settings. Secondly, don't post/email suggestions that have already been mentioned in the "1.2.1: Planned" section of the readme. Lastly, make sure that your suggestion would benefit everyone if implemented, not just yourself. If you meet all these requests, please don't hesitate to send an email, or better yet, post it at the forum (see "1.3.0: Websites"). Check the "1.3.2: Contact Information" section below if you'd prefer to email us. 1.3.2: Contact Information You can reach the members of the team at the following addresses. Note that addresses may change over time, so the best place to find them is at the contact page on the Unreal-Aim website. Also, see the paragraph just below the address to see who your email should be addressed to. RedDeath: yoitsmeremember@users.sourceforge.net Qoole: ua@qoole.zapto.org leflon: leflon@users.sourceforge.net Emails should be sent to all members that relate to the topic of the email. The positions of each member are listed below. Please send translators only translation related questions or criticism and not project related questions/suggestions. RedDeath: website & project admin, project development, forum admin, testing, promotion Qoole: project development, forum admin, testing, promotion leflon: translation (english -> german) 2: Usage This section describes how to use Unreal-Aim to its maximum potential. Read the entire section for the best results. 2.0: Basic Usage The basics. Without it, you'll have a lot of trouble using the aimbot. Be sure to read BOTH parts of this section before attempting to use the aimbot. 2.0.0: How to use Unreal-Aim Once you have edited the skins/textures (section "2.3: Skins & Textures"), simply run unreal-aim.exe, choose your settings, then use the hotkeys in the game to control the aimbot. You can find a list of hotkeys in the section below this one, titled "2.0.1: Hotkeys". Also, be sure to check out the "2.1: Settings" section for settings suggestions. 2.0.1: Hotkeys NEW: Unreal-Aim v1.03 allows you to set the "Hotkey Prefix" to whatever best suits your needs. Replace [HK Prefix] with whatever you have selected in the "Hotkey Prefix" combobox. See section "2.1.1: Hotkey Prefix" for more information. Toggle Unreal-Aim on/off: [HK Prefix] + F1 Cycle Targeted Color: [HK Prefix] + F2 Cycle Sensitivity: [HK Prefix] + F3 (Note: No hotkey bound to F4) Cycle Scan Size: [HK Prefix] + F5 Cycle Scan Resolution: [HK Prefix] + F6 Cycle Scan/Fire Speed: [HK Prefix] + F7 Cycle Mouse Fire Button: [HK Prefix] + F8 Toggle Calibration mode: [HK Prefix] + F9 Reset Calibration mode: [HK Prefix] + F10 Calibration Mode hotkeys: Calibrate left: [HK Prefix] + Left Calibrate right: [HK Prefix] + Right Calibrate up: [HK Prefix] + Up Calibrate down: [HK Prefix] + Down There are two issues I'd like to address here. Number one, why was "[HK Prefix] + F4" skipped? [HK Prefix] + F4 was skipped because, if the [HK Prefix] is "Alt", then the resulting hotkey would be "Alt + F4". Sound familiar? It's a common hotkey used to close programs, and to avoid any issues [HK Prefix] + F4 was skipped. Secondly, calibration mode is explained in section "2.4: Calibration Mode", so if you're curious (or even if you're not) it's worth a read. 2.1: Settings NEW: Unreal-Aim v1.03 saves settings in a configuration file (unreal-aim.ini) for your convenience. If you would like to revert to the default settings, simply close Unreal-Aim, delete "unreal-aim.ini", and restart Unreal-Aim (unreal-aim.exe). The settings should have returned to their defaults. Pay close attention when setting these, as they can be the difference between 80% accuracy and 0% accuracy. 2.1.0: Game Resolution (UPDATED) This is the most straight-forward setting on Unreal-Aim. Set it to the same resolution that the first person shooter game runs at. This setting does not affect the processing power required by Unreal-Aim. 2.1.1: Hotkey Prefix (NEW) This setting allows you to set the [HK Prefix] for the hotkeys described in "2.0.1: Hotkeys". It's recommended that you don't set this to something used in the game, as you might accidentally trigger a game-related action unintentionally. This setting does not affect the processing power required by Unreal-Aim. 2.1.2: Targeted Color (UPDATED) This allows you to set which color the aimbot looks for on the screen. Set it to whatever color you changed the skin/textures to. See "2.3: Skins & Textures" for more information. Also remember that you can cycle through the different available colors using the hotkey [HK Prefix] + F2. Cycling colors is useful for switching teams without exiting the game. This setting does not affect the processing power required by Unreal-Aim. 2.1.3: Sensitivity (NEW) This is a difficult setting to adjust at first. I recommend starting off with it set to "Medium" and then adjusting it during gameplay with the hotkey [HK Prefix] + F3. Cycling through sensitivities is useful not only for fine tuning during gameplay, but also when you go from a map that might require high sensitivity (due to low light) to a map that requires low sensitivity (because it is better lit), and vice-versa. This setting does not affect the processing power required by Unreal-Aim. 2.1.4: Scan Size (UPDATED) This option sets the size of the scanned screen area. Set it to small if you don't want to be detected or if you're worried about the aimbot "locking on" to the wrong objects. Set it to large (or even full) if you want it to spin you around quickly to face the enemy. Scan sizes can be cycled with the [HK Prefix] + F5 hotkey. NOTE: Full is *not* recommended for several reasons. First and foremost, if your Heads Up Display (HUD) is the same color as the as the targeted color, the bot might pick it up as a target and that would make the bot useless. Also, since the scanned area is so large, the scan resolution will be lowered as a result. And if you set the scanned resolution up to counteract the effect, you will really slow down your PC. The scan sizes are as follows (lengthwise, NOT area-wise): Smallest 6.250% of the screen Small 12.50% of the screen Medium 25.00% of the screen Large 50.00% of the screen Full 100.0% of the screen This setting does not affect the processing power required by Unreal-Aim. 2.1.5: Scan Resolution (UPDATED) This is probably the most difficult setting to adjust. First, make sure you have the scan size set to what you want (resolution for a given setting goes down as the scan size goes up). Next try the bot out at a reasonable resolution and see how it behaves. I recommend trying out scan resolutions both higher and lower than the one you like, as you might like a slightly higher or slightly lower one even more. The general rule of thumb is don't set the resolution any higher than it needs to be. Scan resolution can be cycled with the [HK Prefix] + F6 hotkey. This setting has a major effect on the processing power required by Unreal-Aim. 2.1.6: Scan/Fire Speed (UPDATED) This is another difficult setting to adjust. However, in v1.03 it is slightly easier to adjust thanks to the fact that the scans/sec difference is now linear. Most of the time you'll want to set this to one of the slower values, unless you have a lot of recoil or a fully automatic weapon. Scan/fire speed can be cycled with the [HK Prefix] + F7 hotkey. Note that this setting adjusts how often the screen is scanned AND how often the mouse button will be clicked (assuming "2.1.7: Mouse Fire Button" is not set to "None"). The scan speeds are as follows: Slowest 2.000 times/sec Slow 4.000 times/sec Medium 5.***8 times/sec Fast 8.000 times/sec Fastest 10.00 times/sec This setting has a major effect on the processing power required by Unreal-Aim. 2.1.7: Mouse Fire Button (UPDATED) Mouse Fire Button is useful to set which button you want Unreal-Aim to fire when it detects an enemy. Since some FPS games have multiple fire modes on a single weapon (a primary mode and an alternate fire), this allows you to set it to any of three mouse buttons. Also, should you wish to manually fire on detected targets for one reason or another, this can be set to "none", in which case the aimbot will not fire for you and instead just center on targets. This is useful for fully automatic weapons and weapons that require time to charge up. Mouse Fire Button can be cycled with the [HK Prefix] + F8 hotkey. This setting does not affect the processing power required by Unreal-Aim. 2.2: Adjusting mouse sensitivitie ... ...

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：