Skip to main content

Instead of testing for a gamemode NBT tag, why don't you use the gamemode selector instead?

/testforexecute if entity @a[gamemode=adventure]

If you want to mark players, you can use a /scoreboard command with the selectors set to @a[gamemode=adventure].


Before 1.13, it is /testfor @a[m=2], but as of 1.13, m was renamed to gamemode, /testfor was renamed to /execute if entity, and the argument is now the name of the mode.

Props to @ppperry for notifying me of this.

Instead of testing for a gamemode NBT tag, why don't you use the gamemode selector instead?

/testfor @a[gamemode=adventure]

If you want to mark players, you can use a /scoreboard command with the selectors set to @a[gamemode=adventure].


Before 1.13, it is @a[m=2], but as of 1.13, m was renamed to gamemode and the argument is now the name of the mode.

Props to @ppperry for notifying me of this.

Instead of testing for a gamemode NBT tag, why don't you use the gamemode selector instead?

/execute if entity @a[gamemode=adventure]

If you want to mark players, you can use a /scoreboard command with the selectors set to @a[gamemode=adventure].


Before 1.13, it is /testfor @a[m=2], but as of 1.13, m was renamed to gamemode, /testfor was renamed to /execute if entity, and the argument is now the name of the mode.

Props to @ppperry for notifying me of this.

edited body
Source Link
aytimothy
  • 17.8k
  • 17
  • 83
  • 140

Instead of testing for a gamemode NBT tag, why don't you use the gamemode selector instead?

/testfor @a[gamemode=adventure]

If you want to mark players, you can use a /scoreboard command with the selectors set to @a[gamemode=adventure].


Before 1.13, it is @a[m=3]@a[m=2], but as of 1.13, m was renamed to gamemode and the argument is now the name of the mode.

Props to @ppperry for notifying me of this.

Instead of testing for a gamemode NBT tag, why don't you use the gamemode selector instead?

/testfor @a[gamemode=adventure]

If you want to mark players, you can use a /scoreboard command with the selectors set to @a[gamemode=adventure].


Before 1.13, it is @a[m=3], but as of 1.13, m was renamed to gamemode and the argument is now the name of the mode.

Props to @ppperry for notifying me of this.

Instead of testing for a gamemode NBT tag, why don't you use the gamemode selector instead?

/testfor @a[gamemode=adventure]

If you want to mark players, you can use a /scoreboard command with the selectors set to @a[gamemode=adventure].


Before 1.13, it is @a[m=2], but as of 1.13, m was renamed to gamemode and the argument is now the name of the mode.

Props to @ppperry for notifying me of this.

added 260 characters in body
Source Link
aytimothy
  • 17.8k
  • 17
  • 83
  • 140

Instead of testing for a gamemode NBT tag, why don't you use the gamemode selector instead?

/testfor @a[m=3]@a[gamemode=adventure]

If you want to mark players, you can use a /scoreboard command with the selectors set to @a[gamemode=adventure].


Before 1.13, it is @a[m=3], but as of 1.13, m was renamed to gamemode and the argument is now the name of the mode.

Props to @ppperry for notifying me of this.

Instead of testing for a gamemode NBT tag, why don't you use the gamemode selector instead?

/testfor @a[m=3]

If you want to mark players, you can use a /scoreboard command with the selectors set to @a[m=3].

Instead of testing for a gamemode NBT tag, why don't you use the gamemode selector instead?

/testfor @a[gamemode=adventure]

If you want to mark players, you can use a /scoreboard command with the selectors set to @a[gamemode=adventure].


Before 1.13, it is @a[m=3], but as of 1.13, m was renamed to gamemode and the argument is now the name of the mode.

Props to @ppperry for notifying me of this.

3
Source Link
aytimothy
  • 17.8k
  • 17
  • 83
  • 140
Loading
Source Link
aytimothy
  • 17.8k
  • 17
  • 83
  • 140
Loading