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
thanks in advance!
@Patrick model is just the vanilla autocannon, the screenshot is just all the different colors as I am still learning blender. It turns blocks off purely in order for hits to be detectable by script/event controller, and its potential for abuse is limited by the fact that you need practically a head on collision for the laser to not reflect.
Also, why does it turn blocks off? That's a weird mechanic and has high potential for abuse.
@Blank I won't have this one deal damage as it is meant more as a laser pointer/designator, however you can just modify the mod to deal damage, just change the vanilla damage values (in Ammos.sbc) to a nonzero quantity.
I'm not understanding how you expect the laser to interact with the event controller as a detection system. I'd like to.
If you add "block" to your mod listing it might help discoverability.