Problème collisions des tnt minecrafts
-
Merci de ta réponse asser rapide,
J’ai enlever tout les plugins et le problème persiste comme je ne sais pas quoi changé dans les fichiers bukkit/cauldron/spigot je les envois ici:BUKKIT:
settings: allow-end: true warn-on-overload: true permissions-file: permissions.yml update-folder: update ping-packet-limit: 100 use-exact-login-location: false plugin-profiling: false connection-throttle: 4000 query-plugins: true deprecated-verbose: default shutdown-message: Server closed spawn-limits: monsters: 70 animals: 15 water-animals: 5 ambient: 15 chunk-gc: enabled: false period-in-ticks: 600 load-threshold: 0 ticks-per: animal-spawns: 400 monster-spawns: 1 autosave: 6000 auto-updater: enabled: false on-broken: - warn-console - warn-ops on-update: - warn-console - warn-ops preferred-channel: rb host: dl.bukkit.org suggest-channels: true aliases: now-in-commands.yml database: username: bukkit isolation: SERIALIZABLE driver: org.sqlite.JDBC password: walrus url: jdbc:sqlite:{DIR}{NAME}.db world-settings: the_end: enabled: true nether: enabled: trueCAULDRON:
logging: entity-collision-checks: false connection: false tick-intervals: false dump-threads-on-warn: false entity-speed-removal: false disabled-warnings: false world-leak-debug: false collision-warn-size: 200 entity-count-warn-size: 0 entity-death: false entity-despawn: false chunk-unload: false entity-spawn: false dump-chunks-on-deadlock: false chunk-load: false detailed-logging: false dump-heap-on-deadlock: false settings: load-chunk-on-forge-tick: false check-entity-max-speeds: false check-entity-bounding-boxes: true load-chunk-on-request: true entity-bounding-box-max-size: 1000 dump-materials: false world-settings: default: flowing-lava-decay: false infinite-water-source: true entity-despawn-immediate: false worldgen-exadeos-WorldGenExadeos: true worldgen-magicalcrops-WorldGenEssence: true worldgen-magicalcrops-WorldGenEssenceEnd: true worldgen-magicalcrops-WorldGenEssenceNether: true worldgen-etfuturum-SurfaceWorldGen: true plugin-settings: default: remap-plugin-file: false custom-class-loader: true debug: false remap-nms-v1_7_R4: true remap-nms-v1_7_R3: true remap-nms-v1_7_R1: true remap-nms-v1_6_R3: true remap-nms-v1_5_R3: true remap-nms-pre: 'false' remap-obc-v1_7_R4: true remap-obc-v1_7_R3: true remap-obc-v1_7_R1: true remap-obc-v1_6_R3: true remap-obc-v1_5_R3: true remap-obc-pre: false global-inheritance: true plugin-inheritance: true remap-reflect-field: true remap-reflect-class: true remap-allow-future: false fake-players: do-login: false debug: thread-contention-monitoring: false config-version: 1 world-environment-settings: normal: keep-world-loaded: true nether: keep-world-loaded: true the_end: keep-world-loaded: falseSPIGOT:
config-version: 5 commands: tab-complete: 0 log: true spam-exclusions: - /skill silent-commandblock-console: false replace-commands: - setblock - summon - testforblock - tellraw stats: disable-saving: false forced-stats: {} settings: netty-threads: 4 sample-count: 12 timeout-time: 60 restart-on-crash: true restart-script: ./start.sh late-bind: false player-shuffle: 0 bungeecord: false save-user-cache-on-stop-only: false attribute: maxHealth: max: 2048.0 movementSpeed: max: 2048.0 attackDamage: max: 2048.0 filter-creative-items: true user-cache-size: 1000 int-cache-limit: 1024 moved-wrongly-threshold: 0.0625 moved-too-quickly-multiplier: 10.0 debug: false messages: restart: Server is restarting whitelist: You are not whitelisted on this server! unknown-command: Unknown command. Type "/help" for help. server-full: The server is full! outdated-client: Outdated client! Please use {0} outdated-server: Outdated server! I'm still on {0} world-settings: default: verbose: true item-despawn-rate: 6000 merge-radius: item: 2.5 exp: 3.0 enable-zombie-pigmen-portal-spawns: true zombie-aggressive-towards-villager: true arrow-despawn-rate: 1200 chunks-per-tick: 650 clear-tick-list: false view-distance: 10 mob-spawn-range: 4 anti-xray: enabled: true engine-mode: 1 hide-blocks: - 14 - 15 - 16 - 21 - 48 - 49 - 54 - 56 - 73 - 74 - 82 - 129 - 130 replace-blocks: - 1 - 5 nerf-spawner-mobs: false growth: cactus-modifier: 100 cane-modifier: 100 melon-modifier: 100 mushroom-modifier: 100 pumpkin-modifier: 100 sapling-modifier: 100 wheat-modifier: 100 netherwart-modifier: 100 entity-activation-range: animals: 32 monsters: 32 misc: 16 ticks-per: hopper-transfer: 8 hopper-check: 8 random-light-updates: false save-structure-info: true max-bulk-chunks: 5 max-entity-collisions: 8 entity-tracking-range: players: 48 animals: 48 monsters: 48 misc: 32 other: 64 hopper-amount: 1 dragon-death-sound-radius: 0 seed-village: 10387312 seed-feature: 14357617 hunger: walk-exhaustion: 0.2 sprint-exhaustion: 0.8 combat-exhaustion: 0.3 regen-exhaustion: 3.0 max-tnt-per-tick: 100 max-tick-time: tile: 50 entity: 50 wither-spawn-sound-radius: 0 hanging-tick-frequency: 100 -
La seule config que je vois en rapport avec les tnt c’est celle-ci :
max-tnt-per-tick: 100
Essaies de monter à 1000.
Mais je ne suis pas sûr que ça changera quelque chose. -
Non ce n’est pas sa,
Mais dans le fichier cauldron il y a :entity-collision-checks: false
-
Essaies de passer sur true ?
-
Dès que je met sur true et que je redem mon serv bah il se change en false tout seul
-
Il changer la valeur pendant que le serveur est éteint.
-
Le problème est que je n’ai pas les privilèges pour faire sa
-
??? comment ça ?
-
Je ne peut pas changer la valeur numérique du fichier dans les droits d’accès au fichier
-
Voilà ce que j’ai trouvé sur le forum bukkit anglais
"found my problem. Completely took out all my plugins, problem persisted. replaced the dev build “craftbukkit-1.7.10-R0.1.jar” with “craftbukkit-1.7.9-3092.jar” and cannons worked. Now to start putting plugins back in and hope the problem doesn’t come back some other way lol "
Comment changer le dev build de craftbukkit dans cauldron ?
-
Tu ne peux pas.
-
Peut être prendre une version plus ancienne de Cauldron, ou alors peut être que Thermos n’utilise pas les builds devs, à voir…
-
Problème résolu je suis passé sous Thermos.
Merci quand même de vôtre attention
