• How Do I Use The Act5 Command Line Parameter For Macro

Downloading command-line tools is not available in Xcode for macOS 10.9. How can I install them on my machine? In macOS 10.9 and later, the Downloads pane of Xcode Preferences does not support downloading command-line tools.

How do I pass parameters from the command line to my build file? Use properties. Using ant -Dname=value lets you define values for properties on the Ant command line. A command line parameter isn't that difficult to understand. It's simply a command that enables or disables certain features of the game while the program begins. The most common command line parameter is -console.

Use any of the following methods to install command-line tools on your system:. Install Xcode If Xcode is installed on your machine, then there is no need to install them. Xcode comes bundled with all your command-line tools. MacOS 10.9 and later includes shims or wrapper executables. These shims, installed in /usr/bin, can map any tool included in /usr/bin to the corresponding one inside Xcode. Xcrun is one of such shims, which allows you to find or run any tool inside Xcode from the command line. Use it to invoke any tool within Xcode from the command line as shown in Listing 1.

Listing 1 Using xcrun to run dwarfdump in the Terminal application. $ xcrun dwarfdump -uuid MySample.app/MySample UUID: AD019F0E-1318-3F9F-92B6-9F95FBEBBE6F (armv7) MySample.app/MySample UUID: BB59C973-06AC-388F-8EC1-FA3701C9E264 (arm64) MySample.app/MySample.

Download the Command Line Tools package from the Developer website The Command Line Tools package is available for download on the page. Log in with your Apple ID, then search and download the Command Line Tools package appropriate for your machine such as macOS 10.12 as shown in Figure 1. Figure 1 Download page for the Command Line Tools package. How do I build my projects from the command line? Xcodebuild is a command-line tool that allows you to perform build, query, analyze, test, and archive operations on your Xcode projects and workspaces from the command line. It operates on one or more targets contained in your project, or a scheme contained in your project or workspace. Xcodebuild provides several options for performing these operations as seen its.

Xcodebuild saves the output of your commands in the locations defined in the pane of your Xcode application, by default. See below for various xcodebuild usage. Be sure to navigate to the directory containing your project or workspace in Terminal before running any of the following commands. To list all schemes in your workspace, run the following command in Terminal. $ xcodebuild -target iOS -xcconfig configuration.xcconfig Build settings from configuration file 'configuration.xcconfig': IPHONEOSDEPLOYMENTTARGET = 10 SWIFTTREATWARNINGSASERRORS = YES BUILD TARGET watchOS Extension OF PROJECT MyProject WITH THE DEFAULT CONFIGURATION (Debug). BUILD TARGET watchOS App OF PROJECT MyProject WITH THE DEFAULT CONFIGURATION (Debug).

BUILD TARGET iOS OF PROJECT MyProject WITH THE DEFAULT CONFIGURATION (Debug). To change the output locations of your xcodebuild command, use the SYMROOT (Build Products Path) and DSTROOT (Installation Build Products Location) build settings that respectively specify a location for your debug products and.dSYM files and one for your released products. See for more information about these build settings. Listing 8 Setting up a location for iOS' debug app version. Xcodebuild test-without-building -xctestrun.xctestrun -destination -only-testing: -skip-testing: The test action requires specifying a scheme and a destination.

See for more information about build-for-testing and test-without-building actions. The -workspace option allows you to specify the name of your workspace. Use this option when your scheme is contained in an Xcode workspace. The -project option allows you to specify the name of your Xcode project. Use this option when your scheme is contained in an Xcode project. It is required when there are multiple Xcode projects in the same directory and optional, otherwise.

The -destination option allows you to specify a destination for your unit tests. It takes an argument, which describes the device, simulator, or Mac to use as a destination. It consists of a set of comma-separated key=value pairs, which are dependent upon the the device, simulator, or Mac being used. The -only-testing and -skip-testing options, which are optional, allow you to run only a specific test and to skip a test, respectively.

They take an argument, which specifies the test to be executed or excluded. Test-identifier's format is as follows. Table 2 Supported keys for iOS and tvOS apps. Key Description Value platform The supported destination for your unit tests.

IOS (for iOS apps) tvOS (for tvOS apps) name The full name of your device to be used for your unit tests. The name of your device as displayed in the Devices Organizer in Xcode. Id The identifier of your device to be used for your unit tests. See Locate a device identifier for more information about getting your device identifier. The name and id keys are intergeably used with platform, which is a required key as seen in Listing 11 and Listing 12.

Listing 11 Tests the iOS scheme on a device identified by 965058a1c30d845d0dcec81cd6b908650a0d701c. $ xcodebuild test -workspace MyApplication.xcworkspace -scheme iOSApp -destination 'platform=iOS,name=iPhone'. BUILD TARGET iOSApp OF PROJECT iOSApp WITH CONFIGURATION Debug. BUILD TARGET iOSAppTests OF PROJECT iOSApp WITH CONFIGURATION Debug. BUILD TARGET iOSAppUITests OF PROJECT iOSApp WITH CONFIGURATION Debug. Test Suite 'All tests' started at. Test Suite 'iOSAppTests.xctest' started at.

Test Suite 'SecondTestClass' started at. Test Case '-iOSAppTests.SecondTestClass testExampleA' started. Test Case '-iOSAppTests.SecondTestClass testExampleB' started.

Test Suite 'SecondTestClass' passed at. Test Suite 'iOSAppTests' started at. Test Case '-iOSAppTests.iOSAppTests testExample' started.

Test Case '-iOSAppTests.iOSAppTests testPerformanceExample' started. Test Suite 'iOSAppTests' passed at. Test Suite 'iOSAppUITests.xctest' started at. Test Suite 'iOSAppUITests' started at. Test Case '-iOSAppUITests.iOSAppUITests testLabels' started.

Test Case '-iOSAppUITests.iOSAppUITests testToolbar' started. TEST SUCCEEDED. Listing 13 Do not test iOSAppUITests on an iPhone. $ xcodebuild test -workspace MyApplication.xcworkspace -scheme iOSApp -destination 'platform=iOS,name=iPhone' -only-testing:iOSAppTests/SecondTestClass/testExampleB. BUILD TARGET iOSApp OF PROJECT iOSApp WITH CONFIGURATION Debug. BUILD TARGET iOSAppTests OF PROJECT iOSApp WITH CONFIGURATION Debug.

BUILD TARGET iOSAppUITests OF PROJECT iOSApp WITH CONFIGURATION Debug. Test Suite 'Selected tests' started at. Test Suite 'iOSAppTests.xctest' started at. Test Suite 'SecondTestClass' started at. Test Case '-iOSAppTests.SecondTestClass testExampleB' started.

Test Case '-iOSAppTests.SecondTestClass testExampleB' passed (0.007 seconds). Test Suite 'SecondTestClass' passed at. TEST SUCCEEDED.

For iOS Simulator and tvOS Simulator apps, destinationspecifier supports the platform, name, id, and OS keys as seen in. Table 3 Supported keys for iOS Simulator and tvOS Simulator apps. Key Description Value platform The supported destination for your unit tests. IOS Simulator (iOS apps) tvOS Simulator (tvOS apps) name The full name of the simulator (iOS simulator for iOS apps and tvOS Simulator for tvOS apps) to be used for your unit tests and as displayed in the run destination of your Xcode project. The name of your device as displayed in the Devices Organizer in Xcode. Id The identifier of your device to be used for your unit tests.

See Locate a device identifier for more information about getting your device identifier. OS The version of iOS or tvOS to simulate such as 9.0 or the string latest to indicate the most recent version of iOS supported by your version of Xcode. An iOS version, tvOS version, or latest The name and id keys are intergeably used with platform, which is a required key as shown in Listing 15 and Listing 16. The OS key is optional. Listing 15 Tests the iOS scheme on an iPad Pro (12.9 inch) with iOS 10.2 in the Simulator. Xcodebuild build-for-testing -scheme tvOS -destination 'platform=tvOS Simulator,id=D6FA2C2A-E297-406A-AA22-624B4834ACB2' build-for-testing generates an xctestrun file, which is saved in the derived data folder.

See 's man page for more information about xctestrun files. xcodebuild provides the test-without-building action for Xcode's Product Perform Action Test Without Building feature. Test-without-building requires that you specify either a scheme or an xctestrun file.

Usage when using a scheme. $ xcodebuild -help Usage: xcodebuild -project -target.alltargets -configuration -arch. Available keys for -exportOptionsPlist: compileBitcode: Bool. EmbedOnDemandResourcesAssetPacksInBundle: Bool.

Manifest: Dictionary. Method: String. OnDemandResourcesAssetPacksBaseURL: String. TeamID: String.

Thinning: String. UploadBitcode: Bool. UploadSymbols: Bool. See Figure 3 for a sample file that contains some options for the -exportOptionsPlist flag. Figure 3 Plist file with a list of options for the -exportOptionsPlist flag.

Document Revision History Date Notes 2017-06-19 Updated the 'How do I run unit tests from the command line?' Added the 'How do I implement the Build For Testing and Test Without Building features from the command line?'

And 'What keys can I pass to the exportOptionsPlist flag?' Updated the 'How do I run unit tests from the command line?'

Added the 'How do I implement the Build For Testing and Test Without Building features from the command line?' And 'What keys can I pass to the exportOptionsPlist flag?' 2014-05-21 New document that provides answers to frequently asked questions about command-line tools.

Contents. Communication Commands All of these work in chat channels and in game. /ignore (player): Squelches messages from this player. /friends: (or /f) This displays help instructions on how to use the various friends commands. (See more on friends commands below.).

/msg (player): Sends a private message. /msg (character name): Sends a private message. /msg.(accountname): Sends a message to any character logged on from that account.

/msg (D2 ): Allows messages to be sent between the realms: USWest, USEast, Asia, or Europe. /d2notify: Diablo II: Toggle channel enter/leave notifications.

/reply replies to the last message sent. /squelch (player): Ignore messages from this player.

/unsquelch (player): Turns off squelch for this player. /unignore (player): Turns off squelch for this player. /users: Displays all number of users, games and channels on the server.

/w (player): Sends a private message. /who (channel): Lists all the characters in a given channel. /whoami: Displays your account information to you.

/whois (player): Displays that players info to you. /whisper (player): Sends a private message.

Chat, Private Channel, and Op Commands Commands that only work in chat. Some only work for channel ops in private channels. /ban (player): Ban specified player. (Channel Ops only.). /channel (channel): Join selected channel. /clan (your name): Create a private clan channel with your name as the title. /designate (username): Assigns a Channel Operator, if none is in place.

This user will become the Op when the current Op leaves or resigns. /kick (player): Kick specified player.

(Channel Ops only.). /rejoin: Rejoin current channel. (Useful after a desynch.). /resign: Step down as the channel operator. (Channel Ops only.).

How Do I Use The Act5 Command Line Parameter For Macro

/stats (username): Shows the stats of a player. It will always show 0-0-0 for Diablo players, because we are undefeated!. /unban (player): Unban specified player. (Channel Ops only) Friends Commands All these can be used with /friends or /f for faster typing. They work in chat channels or in game. A handy shortcut is to use the number of someone on your friends, after the% key, instead of typing their name. For instance, /f%7 will send a message to the 7th person on your friends list.

Or /f p%5 will promote the fifth person on your user list (to the 4th spot, unless you specify a number). /f: Shows help about these commands. /f list: (or /f l) Shows all of your friends and their current status. /f add (accountname): (or /f a) Adds the account name to your friends list. Maximum friends = 25. /f add (username): (or /f a) Adds the account name to your friends list.

Maximum friends = 25. /f add (charactername): (or /f a) Adds the account name to your friends list. Maximum friends = 25. /friends remove (accountname): (or /f r) Removes that account from your friends list.

/friends msg (message): (alias: /f m) - Sends the message to everyone on your friends list. (Use sparingly to avoid getting squelched.). /friends promote (accountname) (or /f p) Moves that friend up one slot (or to the inputted number) in your friends list.

/friends demote (accountname) (or /f d) Moves that friend down one slot (or to the inputted number) in your friends list. Ignore Commands Ways to control the messages you see. /options ignorepublic (or /o igpub) - Ignore messages in public chat channels from anyone who isn't in your friends list. /options unignorepublic (or /o unigpub) - Re-allows messages in public chat channels from anyone who isn't in your friends list.

/options ignoreprivate (or /o igpriv) - While in private channels you will not receive messages from anyone who isn't on your friends list. /options unignoreprivate (alias: /o unigpriv) - While in private channels you will not receive messages from anyone who isn't on your friends list. /options ignorewhispers (or /o igw) - Ignore whispers from anyone who isn't in your friends list.

/options unignorewhispers (or /o unigw) - Re-allows whispers from all users. Status Commands These work in chat channels and games. /away (reason): Displays your away status and the explanation to players who might query you. /dnd (reason) This command blocks all incoming messages and displays the supplied reason to the sender. In-game Commands These only work when typed into the chat box while playing the game.

Many of the Chat Channel commands work in-game too, including all of the various messaging and ignoring controls. A shortcut for repeating commands in game is to hit enter to open the chat box, and then use the up/down arrows to cycle through commands you sent out previously in that game. You can resend the same ones, or backspace to delete portions. /framerate: Displays the same stats as /fps, but also includes some memory allocation information. /fps: Shows ingame framerate. 25 is the maximum display rate for Diablo II.

/nopickup: Stops your character from picking up any items in that game. Useful for speed runs.

/players 1-8: Only in v1.09 and later. Only single player. Simulates more players in the game to increase drops and game difficulty. Can not be set to a lower number than the players in the game. See page for details. /soundchaosdebug: Plays a jumble of every sound in the game.

Type the command again to turn it off. /time: Displays your local time and Battle.net server time. Chat Shortcuts These are basic Windows commands that work in Battle.net chat.

CTRL-X: Cuts the selected text. CTRL-C: Copies the selected text. CTRL-V: Pastes the selected text.

CTRL-A: Select all text. CTRL-N: Pastes the name you have selected.

ALT-N: Pastes the name you have selected. ALT-V: Toggle channel enter/leave notifications. ALT-W: Sends a private message to the selected user. (Also /w or /m.

See above.). TAB: Cycles through the last 10 commands. CTRL-M: Diablo II: Toggles music on Battle.net and the main menus. Target Line Commands These are commands that change some basic functions of the game. They must be in place when the program starts up.

To enable these, go to the shortcut you use to start up Diablo II, right click, select properties, and view the target field. The default installation yields this: 'C: Program Files Diablo II Diablo II.exe' Add any commands after that, with a space between them. For instance: 'C: Program Files Diablo II Diablo II.exe' -w -act5 Here's a short list of the most useful commands. The full list (most of which are without function) can be seen below.

act#: New characters will appear in that act, at the preset level, with unspent skill and stat points.act1: Characters are level 1 in act 1. (Default setting.).act2: Characters are level 16 in act 2.act3: Characters are level 21 in act 3.act4: Characters are level 27 in act 4.act5: Characters are level 33 in act 5.nosave: Never saves the game.ns: Starts the game without sound.seed: Shows the game seed, based on the time of the game creation. Used in some mods and utilities to recreate that exact same game for replay.skiptobnet: Bypasses the introduction screens by starting the game at the Battle.net login screen.w: Runs Diablo II in windowed mode, at whichever resolution you have specified. Full List of Target Line Commands Most of these are oddities left over from the development process. Most of these do not work in later game versions.

Video Options.exp -expansion switch expansion mode.w -window switch window mode.glide -glide use glide video mode.opengl -opengl use opengl video mode.d3d -d3d use direct3d video mode.rave -rave use rave graphics modes,might be Mac only.