Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
EX: the number right after settileprotection, is the dungeon id you're affecting. most of the game is 0, but some of the story missions have parts with different id because the devs wanted to be triksy hobbitses (read, they got angry at players using settileprotection to break their dev-imposed idiocy, so they tried new idiocy).
Whatever the debug readout says the id is, you'd use that instead of 0.
Alternatively, what was that damn command,
/entityeval object.smash()
might work, it ignores "unbreakable" as set in the item itself. (ex: ship's fuel-hatches, lockers, SAIL in a vanilla un-modded game)