Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
im not asking much just some scripting
It's been a while so I don't remember the specifics. However, I don't think this version of Tyr is smart enough to trigger an alert when there is a damaged block and another block is damaged. Do you mean that, or do you mean that even if a damaged block is repaired and a new block is damaged, Tyr doesn't fire the alarm?
I found a problem. The only way to reset Tyr is by recompiling (checking) the code.
Details: If I grind a block after initial load of the world, Tyr detects it and triggers the assigned timer block. After repairing the block and rebooting tyr, I ground that block again along with another one. Tyr registered the destroyed blocks on the status display, but doesn't trigger the timer block. Rebooting didn't change the result. It was only after recompiling the code that Tyr will trigger the timer block.
I do like how the off block stack is pushed down by any damaged block reports. I was going to suggest moving the off blocks to another LCD, but this seems to work well.