CakeSorbus Posted September 6, 2020 Posted September 6, 2020 (edited) Hi folks, I found a bug in the scripting engine that isn't listed in Grimes List yet. It relates to the handling of the events S_EVENT_MARK ADDED (event.id 25) S_EVENT_MARK CHANGE (event.id 26) S_EVENT_MARK REMOVE (event.id 27) in the multiplayer environment. Here's the event page on Hoggit: https://wiki.hoggitworld.com/view/Category:Events I've noticed that the field event.initiator always get populated with the unit that the server host is currently sitting in, no matter which player actually created, changed or removed a mark. I have attached the test mission I have used to test this bug after I first stumbled upon it. In it I run a simple script that returns some fields of the event table as .outText. This bug is pretty annoying to me because i have written a script that provides Zeus-like functionality to DCS and uses map markers as its input method. Without a way to know who created a marker I have no way to effectively limit the access to the Zeus functions, or return status messages only to the player that sent a command. :(Testmission.miz Edited September 11, 2020 by Cake/Sorbus
HC_Official Posted November 14, 2020 Posted November 14, 2020 on dedicated server sadly , you cannot get the initiator at all which is a bummer :-( No more pre-orders Click here for tutorials for using Virpil Hardware and Software Click here for Virpil Flight equipment dimensions and pictures. .
Catweedle Posted November 14, 2020 Posted November 14, 2020 It's not going to solve the initiator-problem, and it's certainly not the most effective or secure method, but: you could "password" the mark-commands with something like -spawn sam_site1 #password123.
CakeSorbus Posted November 16, 2020 Author Posted November 16, 2020 Hey guys, thanks for keeping this thread alive! :) @Catweedle Yes, that would work in regards to restricting access, thanks!
chromium Posted January 29, 2023 Posted January 29, 2023 It seems the bug is still there Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.
Recommended Posts