|
|
| (Nie pokazano 10 pośrednich wersji utworzonych przez tego samego użytkownika) |
| Linia 1: |
Linia 1: |
| {{Budowa}} | | <noinclude>{{Budowa}}</noinclude> |
| | | {{#invoke: Sprite | link |
| Jesteś teraz na stronie brudnopisu użytkownika [[Użytkownik:VaderVCD|VaderVCD]]. Możesz przejrzeć moje zapiski.
| | | data = BiomeSprite |
| | |
| Jeśli ta strona jest pusta, to znaczy, że aktualnie nie pracuję nad większą edycją/nową stroną.
| |
| | |
| = Minecraft Launcher =
| |
| {{infobox | |
| |title=Minecraft launcher | |
| |defaultimagesize=292px
| |
| |image=2016Launcher.png | |
| |rows=
| |
| {{infobox row|Current version|{{v|launcher=1}}}}
| |
| {{infobox row|Platforms|{{OS|Windows|macOS|Linux}}}}
| |
| }} | | }} |
| The '''''Minecraft'' launcher''' is the login and downloader front-end to the stand-alone client. It is responsible for downloading the main Java packages, including '''[[minecraft.jar]]''', which holds the code and resources of the game such as textures, and [http://lwjgl.org LWJGL]. It also acts somewhat like a basic and easily bypassable copy-restriction by forcing the user to login to a paid account when running for the first time. It is possible to use the launcher to run versions of ''[[Minecraft]]'' from nearly any era, however some versions are still not included on the launcher, such as [[Indev]], [[Minecraft 2.0]] and any of the [[Beta 1.9-pre1|Beta 1.9 pre-releases]]. The current launcher is the sixth launcher for ''Minecraft'', and the second that was built to automatically update itself.
| |
|
| |
| == Launch ==
| |
| [[File:2016LauncherLogin.png|right|thumb|The login screen for launchers without previously logged-in users.]]
| |
| Every time the launcher is executed, it checks a specific directory where ''Minecraft'' stores its files called [[.minecraft]]. It checks a file called "launcher_profiles.json" for login credentials. If the file does not exist, is corrupt, or no user is logged in, the user must login with a valid premium account, otherwise the user will be directed to play the Demo version or purchase the game.
| |
|
| |
| When logging in, the launcher will first try to verify the login. If a valid "launcher_profiles.json" file exists but there is no Internet connection, the launcher will offer a "Play offline" mode if a player was logged in when it was last closed. If the connection is successful, the launcher will then, depending on profile options, compare the latest version in the latest "versions" directory to the latest version reported by the server. If the selected version does not exist or the latest installed version is outdated when "Use latest version" is selected in the profile, the launcher will download all ''Minecraft'' components and Java binary files. It will also synchronize everything in the Assets folder (see [[Resource pack]]).
| |
|
| |
| Finally, upon a successful update or installation, the launcher will execute the Minecraft jar (via "javaw.exe", Oracle's Java Virtual Machine executable.) It is possible however for there to be missing ".jar" files, in which case the launcher will attempt to replace the missing files automatically but will stop if there is no connection.
| |
|
| |
| Currently, the ''Minecraft'' launcher supports 57 languages.
| |
| {{-}}
| |
|
| |
| == Features ==
| |
| {{anchor|Version Control}}
| |
| <!--The anchor for the Version Control page. Please move this with the version control information or update that page if this one splits.-->
| |
| === Launcher ===
| |
| * Manage multiple profiles (stored in "launcher_profiles.json"). Each profile can control:
| |
| ** Game version. Includes access to outdated development builds and previous releases. You can also add older/custom versions manually.<ref>{{tweet|dinner|344164561701724160}}</ref>
| |
| ** Mojang account used to play the game
| |
| ** Command line arguments for Java (such as heap size)
| |
| ** Game Directory (where the game files are saved on disk)
| |
| ** Edit profile pictures or custom made ones
| |
| * The launcher doesn't store your password locally. Instead of this, it uses a 'refresh token'
| |
| * The launcher supports multiple instances (as the game also does)
| |
| * Automatic updates for launcher
| |
| * Ability to update libraries, such as [[LWJGL]]
| |
| * Offline mode. (The first time launch requires an Internet connection to download required resources)
| |
| * 57 Languages avaliable
| |
| * Crashes can be reported to Mojang, through [[Hopper (crash utility)|Hopper]]
| |
| * Crashes are indexed through a database for information on how to fix the issue
| |
| * Launcher Settings
| |
| * Switching Accounts or logging off
| |
| * Changing Skins
| |
| * Downloads servers on versions
| |
| * Help button
| |
| * Shows you the launcher version information when you click the launcher version
| |
|
| |
| === Time Machine ===
| |
| [[File:HowtoOldVersion2016.png|thumb|300x300px|A profile with Alpha and Beta versions enabled]]
| |
| The Minecraft launcher has the ability to play old [[Alpha]] and [[Beta]] versions of the game. Currently, snapshots, Alpha, Beta, and all Release versions are available to play. Four [[Pre-classic]] versions, four [[Classic]] versions, and an [[Infdev]] version are already added under the names "old-alpha version".<ref>{{tweet|dinner|364762596387205120}}</ref>
| |
| However, [[Indev]] is still missing.
| |
|
| |
| [https://docs.google.com/spreadsheets/d/12SQkNnsYK_vANPcdn7FKrFn5RHcneAfOYmjoNYMpHzQ/pubhtml Progress] *note: as of 1.10.2
| |
|
| |
| To enable the old versions either click the "Launch Options" then turn the "Historical Versions" on then open your profile or make a new one, next select any of Alpha/Beta versions on the Version box then click "Save" button.
| |
|
| |
| However, these versions are very out of date and may be unstable. Any bugs, glitches, missing features, or crashes that result from instability will never be resolved as only later versions are supported. Mojang strongly recommends that you play them in separate directories than your other saves to avoid corruption.<ref>https://help.mojang.com/customer/portal/articles/1475923-changing-game-versions</ref>
| |
| {{-}}
| |
|
| |
| === Skins ===
| |
| [[File:ChangingSkinLauncher.png|thumb|Skin options in the launcher]]
| |
| You can change or add your custom skin within the Minecraft Launcher. To change or add your skin click the "Skins" button, then click the "Browse" button to navigate through your file system for your skin file. The file must have a resolution of 64×64 in order for the launcher to accept it as a skin file. Additionally, the skin file must be in a <code>.png</code> format. After you have found the skin file, click the "Save" button to confirm your in-game skin.
| |
| * You can reset your skin to the Steve or Alex defaults by clicking "Click to reset".
| |
| * You can choose between player models - either Classic (Steve) or Slim (Alex).
| |
|
| |
| === Profiles ===
| |
| When you open the launcher for first time, it creates a profile that selects the latest version of Minecraft - it cannot be removed.
| |
|
| |
| However, you may create a game profile of your own in the launcher. Click on the "Launch Options" button, then click "Add New" to create one. After this, name your profile as you want it. If you leave it, it will be named "Unnamed Configuration". Then, optionally, select a profile picture from the launcher or a custom one. However, it must be a 128×128 <code>.png</code> picture. Select the version you wish to play, and click "Save" to confirm your profile. If you want to edit a profile, just click it. The same applies if you wish to delete a profile. Simply click the profile you want to delete and then click the "Delete [X]" button to remove it.
| |
| * [[File:2016LauncherProfileSettings.png|thumb|Profile settings in the launcher]]You can download server versions by clicking "Download Server".
| |
| * If you want to resize the game, turn "Resolution" on to change the game window size.
| |
| * You can turn "Advanced Settings" on to show more profile options.
| |
| * If you want to change the <code>.minecraft</code> file path, turn the on the "Game directory" option. Now, navigate to the folder where you wish to relocate the <code>.minecraft</code> folder. You can also open the Minecraft profile by clicking the green arrow-shaped "Go to folder" button.
| |
| * If you turned "Snapshot Versions" on, it creates a "Latest Snapshot" profile automatically.
| |
| * You can manually set a [http://logging.apache.org/log4j/2.x/manual/configuration.html logging configuration] (see [http://wiki.vg/Debugging the Debugging article on wiki.vg] for more info)
| |
|
| |
| == Command Line usage ==
| |
| MinecraftDev.jar (all systems): <code>java -cp Minecraft.jar net.minecraft.bootstrap.Bootstrap <username> <server:port></code>.
| |
|
| |
| Beginning with the launcher released with [[1.6.1|Minecraft 1.6.1]], there are other commands for the launcher. These can be seen by running <code>java -jar Minecraft.jar -help</code>.
| |
|
| |
| The new (2.0) launcher has a command-line parameter to change the working directory from <code>.minecraft</code> to any directory of the user's choice: <code>Minecraft_staging.exe --workDir "D:\Users\Administrator\AppData\Roaming\.minecraft"</code>. This is especially helpful for users who would like to keep their <code>.minecraft</code> folder off a certain drive, for example, their solid-state drive. The <code>--workDir</code> parameter is available for Windows, Linux, and macOS.
| |
|
| |
| {{-}}
| |
|
| |
| ==History==
| |
| {{History|alpha}}
| |
| {{History||1.0.0|Initial release. In this version users can choose not only the current version but also [[Infdev]].
| |
| |The client requires an internet connection on the first run and for updates, but after that the game supports playing offline.
| |
| |Command line arguments are accepted to launch the game. Using the format <code>java -cp Minecraft.jar net.minecraft.LauncherFrame ''username'' ''password''</code> will allow login without joining a server, while the format <code>java -cp minecraft.jar net.minecraft.LauncherFrame ''username'' ''password'' ''serveraddress'':''portnumber''</code> allows joining a server.}}
| |
| {{History||1.2.2|Command line arguments format changed.}}
| |
| {{History|beta}}
| |
| {{History||1.3|Released in February 21, 2011.<ref>http://notch.tumblr.com/post/3428176687/server-downtime-and-a-new-launcher</ref> A technical sneak preview was published by Notch on February 18, 2011.<ref>{{tweet|notch|38621269331025921}}</ref>Added capability of automatic login to the game and/or server by command line arguments.|Added smarter update system that only updates changed files, prompts the user to update, allows HTTPS logins for a more secure connection, and offers general UI improvements.
| |
| |Link to the ''Minecraft'' install directory for easy access.
| |
| |Add ''Force Update'' button under the ''Options'' dialog.
| |
| |The launcher also featured an inline "changelog" via a [http://mcupdate.tumblr.com/ Tumblr] called [[MCUpdate]], and supports command-line arguments.<ref>http://mcupdate.tumblr.com/post/3427294253/welcome-to-the-new-minecraft-launcher</ref>|Added the new Minecraft logo.|Added official links, community links and Mojang on Twitter links.|}}
| |
| {{History|release}}
| |
| {{History||1.2.1|Properly selects 64-bit Java installations for Mac OS X users.<ref>http://www.mojang.com/2012/03/minecraft-1-2-is-out/</ref>}}
| |
| {{History||1.3.2|Added ability to launch [[demo mode]] for non-premium users.}}
| |
| {{History||1.6.1|snap=13w16a|New launcher added. See launcher history below.}}
| |
| {{History|foot}}
| |
|
| |
| == Gallery ==
| |
| <gallery>
| |
| File:AlphaLauncher.png|The first ''Minecraft'' launcher.
| |
| File:Launcher-1.0.png|The second ''Minecraft'' launcher. You can see old ''Minecraft'' logo.
| |
| File:Oldlauncher2.png|The third ''Minecraft'' launcher.
| |
| File:Oldlauncher3.png|The fourth ''Minecraft'' launcher.
| |
| File:Launcher-1.6.png|The fifth ''Minecraft'' launcher version 1.6.
| |
| File:2016Launcher.png|The sixth and current Minecraft launcher version 2.0.
| |
| File:Minecraft Launcher-Launcher Log.png|The ''Launcher Log'' tab after the Launcher starts
| |
| File:1.6DevLauncher Local Version Editer (NYI).png|The ''Local Version Editor (NYI)'' tab (replaced by Time Machine)
| |
| File:Launcher Outdated.png|Error message that is displayed if a development launcher is outdated
| |
| File:Used_Newer_Launcher.png|Error message that is displayed if you open an old launcher after using the 2.0 launcher
| |
| File:2016LauncherProfileIcons.png|Profile icons selection from launcher.
| |
| File:2016LauncherOfflineMode.png|Launcher in offline mode
| |
| File:2016LauncherHelp.png|The Help page
| |
| File:GameCrashinNewLauncher.jpg|Game crash
| |
| File:GameisAlreadyRunninginNewLauncher.jpg|Launcher warns you to run another minecraft if you ran it already
| |
| </gallery>
| |
|
| |
| == Trivia ==
| |
| <div style="float:right">{{animate|Launcher Creeper face.png;Launcher Creeper face.png;Launcher shrug emoji.png;Launcher shrug emoji.png|120px}}</div>
| |
| * In the top left corner a barely visible button can be found which randomly shows either a Creeper face or a shrug meme ¯\_(ツ)_/¯. It glows white when clicked, but has no use at all
| |
| ** The Creeper face as well as the meme were used for the language selection menu during the beta phase of the launcher, but when a globe was added instead both were simply moved downwards to be kept as an Easter egg
| |
| * If you stay long enough on the "Play" button, random mobs will appear on the right side of the window.
| |
|
| |
| == References ==
| |
| {{reflist}}
| |
|
| |
| == See also ==
| |
| * [[Programs and Editors]]
| |
|
| |
| {{minecraft}}
| |
|
| |
|
| |
| [[de:Minecraft Launcher]]
| |
| [[es:Ejecutable de Minecraft]]
| |
| [[fr:Launcher]]
| |
| [[pt-br:Minecraft launcher]]
| |
| [[ja:Minecraftランチャー]]
| |
| [[nl:Minecraft launcher]]
| |
| [[ru:Лаунчер]]
| |
| [[zh:启动器]]
| |
|
| |
| = Funkcje =
| |
| {{exclusive|java}}
| |
|
| |
| '''Functions''' allow players to run lists of [[commands]] using text files with the extension <code>.mcfunction</code>. It is recommended to use UTF-8 (without BOM) encoding on function files to prevent any problems.
| |
|
| |
| == Usage ==
| |
|
| |
| To utilize functions, the text files must first be placed into a top-level folder within <code>[[.minecraft]]/saves/[WORLD_NAME]/data/functions</code>. The name of this top-level folder will be the namespace used when running functions inside this folder. Functions can also be placed into subfolders within the folder.
| |
|
| |
| For example, running the function <code>custom:example/test</code> will refer to the file located at <code>functions/custom/example/test.mcfunction</code>. If the namespace is left out when trying to call a function, it will default to the <code>minecraft:</code> namespace. Using a custom namespace is recommended in order to prevent unintended behavior in the case of future additions to the default namespace.<ref>{{tweet|dinnerbone|877427768715341824|Until vanilla adds something with the same name, then it won't work for you! Or if someone else has to work with your stuff, then confusing!|June 21, 2017}}</ref>
| |
|
| |
| Functions, being text files, are easily modifiable and less likely than [[command block]]s to induce lag when used in large quantities. If a function is modified or added, using the {{cmd|reload}} command will reload the function files from disk. This allows ''Minecraft'' to recognize any changes to the function files, without the need to quit and re-enter the world.
| |
|
| |
| Upon successfully running a function, a message will display in the [[chat]]: ''Executed [amount] command(s) from function '[function file directory]'''. The successful output of the commands inside a function cannot be measured with a [[comparator]] (although the same effect could be accomplished with the use of {{cmd|stats}} and {{cmd|scoreboard}} commands).
| |
|
| |
| === Function syntax ===
| |
|
| |
| [[File:TestingFunctions.png|thumb|right|250px|Testing the function system. Three {{cmd|tellraw}} messages and one {{cmd|give}} command were used in this simple function.]]
| |
|
| |
| Within the <code>.mcfunction</code> file, one valid command is placed per line, without the usual forward slash (<code>/</code>). Players can add comments within the function text file by preceding them with a <code>#</code>.
| |
|
| |
| Individual commands in functions can be longer than the 32 500 character limit in command blocks but the total number of commands run inside a function will still obey {{cmd|gamerule maxCommandChainLength}}, which is 65 536 commands by default; any commands beyond this limit will be ignored.
| |
|
| |
| === Running a function ===
| |
|
| |
| Functions will run all of their commands in a single [[tick]] and functions called from within other functions will also run their commands in the same tick as their parent.
| |
|
| |
| Position changes that happen within a function will not affect the [[Commands#Tilde_notation|relative coordinates]] used in other commands within that function (or within its child functions) until the next iteration, regardless of the order of commands. The {{cmd|execute}} command circumvents this.
| |
|
| |
| For example:
| |
|
| |
| tp @s ~ ~5 ~
| |
| setblock ~ ~-1 ~ emerald_block
| |
| execute @s ~ ~ ~ setblock ~ ~-1 ~ diamond_block
| |
|
| |
| When called through a player this function will teleport that player 5 blocks up, place an [[emerald block]] one block below their original position ''before'' the teleport, and place a [[diamond block]] one block below their new position ''after'' the teleport. This behavior does not affect position arguments within selectors, which will always test for the current position at the time of execution.
| |
|
| |
| There are several methods of running a function file in-game:
| |
|
| |
| ==== Commands ====
| |
|
| |
| ;{{cmd|function}}
| |
| * Allows players to run a function once.
| |
| * The commands in the function are run through the [[entity]] or command block that ran the {{cmd|function}} command.
| |
| * The optional arguments <code>if</code> and <code>unless</code> will make the function only run when the <code>selector</code> was found or not found in the world respectively.
| |
| * Usage: {{cmd|function|...}}
| |
|
| |
| ;{{cmd|gamerule|gameLoopFunction}}
| |
| * Runs a function every tick.
| |
| * The commands in the function are run through the server.
| |
| ** The coordinates from which the "server" executes commands are (0, 0, 0).
| |
| * If multiple functions need to be looped, it is possible to insert function commands into this looped function file, put function commands in those functions, etc.
| |
| * Usage: <code>/gamerule gameLoopFunction <''namespace:path/to/function/file''></code>
| |
|
| |
| ==== Advancements ====
| |
|
| |
| [[Advancements]] can run a function once as a reward for completing them. The commands in the function are run through the player who completed the advancement.
| |
|
| |
| Reward functions are called within advancement [[JSON]] files using the following format:
| |
|
| |
| {
| |
| "rewards": {
| |
| "function": "namespace:path/to/function/file"
| |
| }
| |
| }
| |
|
| |
| == History ==
| |
|
| |
| {{History|release}}
| |
| {{History||1.12|snap=pre1|Added functions.}}
| |
| {{History|||snap=pre3|Commands are no longer allowed to begin with a / (forward slash)|Comments can now only be preceded with #; using // is no longer allowed}}
| |
| {{History|||snap=pre4|Added new arguments to the {{cmd|function}} command: <code>[if{{!}}unless] [selector]</code>}}
| |
| {{History|||snap=pre6|Skipped functions (when a conditional fails) are now considered failures when used in commands.}}
| |
| {{History|foot}}
| |
|
| |
| == Issues ==
| |
|
| |
| {{Issue list}}
| |
|
| |
| == References ==
| |
|
| |
| {{reflist}}
| |
|
| |
| {{Minecraft}}
| |
|
| |
| [[de:Funktion]]
| |
| [[fr:Fonctions]]
| |
| [[ja:関数]]
| |
| [[ru:Функция]]
| |
| [[zh:函数]]
| |
