There is no bug. I've tested it. Must be something on your side.

No. I've just added it. It will be in the next PC update.

Yes that should be reasonably easy to do. See the HasHistory command.

If you replace a 64x64 block texture, you also need to supply a 16x16 LOD texture, there is a post about it somewhere.

var [num] = [rand:2]

If
IsVar [num] [=] [0]
Then
Inventory [player] [add] [reward1] [1]
ElseIf
IsVar [num] [=] [1]
Then
Inventory [player] [add] [reward2] [1]
ElseIf
IsVar [num] [=] [2]
Then
Inventory [player] [add] [reward3] [1]
Else
EndIf


If this is what you mean it just gets a random number between 0-2, and then gives a certain item for each number

A slightly more streamlined version. Since if num is not 0 and not 1 we know it must be 2 so the last ElseIf is unnecessary.

var [num] = [rand:2]
If
IsVar [num] [=] [0]
Then
Inventory [player] [add] [reward1] [1]
ElseIf
IsVar [num] [=] [1]
Then
Inventory [player] [add] [reward2] [1]
Else
Inventory [player] [add] [reward3] [1]
EndIf

Code: [Select]

if (InputManager.IsKeyPressed(tmPlayer.PlayerIndex, Keys.P))
{
     SoundEffect sound = game.AudioManager.LoadSoundEffectFromStream(FileSystem.RootPath + Mod.Path + "357_reload1.wav");
     sound.Play();
}

While this code works, it has some flaws.

It will be loading and playing the sound effect 60 times a second. That will likely be problematic. Better to use InputManager.IsKeyPressedNew or InputManager.IsKeyReleasedNew. This ensures the sound effect is only played once per key press.

Also it is inefficient to load a sound effect from disk every time you want to play it. It will likely cause frame rate stutters. It is better to cache all sound effects by loading them once when the mod is initiailized (see the LockPick example on github).

Also if you plan on using the sound effect rapidly, like say for machine gun fire, then it is better to use the SoundEffectInstance type over the SoundEffect type. It allows more control the playing of several instances of the sound effect better, even if the sound overlaps each other, and gives other control you don't have with SoundEffect.

cmd: Execute all the console commands in a cmd file.

cmd [name] [args]

[name] -- The name of the command file. This will be a *.cmd file residing in the maps save folder on disk. You can create these files using any text editor.
[args] -- Optional arguments that can be passed to the commands inside the command file.

Example:
cmd crates -- This will run all the console commands in the crates.cmd file found in the maps save folder.
crates -- This will also run all the console commands in the crates.cmd file found in the maps save folder.

Note: cmd is only necessary if the name of the .cmd file conflicts with an existing console command name. For crates, because there is no crates console command, you can just type crates without the preceding cmd, and the crates.cmd file will be executed.

Argument substitution is possible with cmd files, similar to MSDOS batch files. If the command in the cmd file uses %n (where n is a number starting from 1) as an argument, then the corresponding argument passed with the cmd command will be substituted for the %n argument in the cmd file.

Example:
If we have a cmd file named welcome.cmd with the following commands:
notify %1
notify %2

Then the following are examples of the output:

cmd welcome hello everyone
notify hello
notify everyone

cmd welcome hello john
notify hello
notify john

cmd welcome sup dawg
notify sup
notify dawg

fixed in 27403