Geradon Posted February 22, 2017 Share Posted February 22, 2017 NAME: Game Crash for all players (observer map)SEVERITY: 2 (because it's only observer map)LOCATION: Loading ScreenREPRODUCIBILITY: just once, but for all playersDESCRIPTION: BF crashed with error message below while we (3 players) started an observer map.SCREENSHOT: see belowADDITIONAL INFORMATION: - Quote Link to comment Share on other sites More sharing options...
MephistoRoss Posted February 22, 2017 Share Posted February 22, 2017 Seems like this is a bug in the lua script of the custom map. So I am not sure what you want the devs to do with this? Quote Link to comment Share on other sites More sharing options...
Geradon Posted February 23, 2017 Author Share Posted February 23, 2017 dunno. I don't know shit about this stuff. I reported it in case it's something important for the devs^^ If not just delete it. Quote Link to comment Share on other sites More sharing options...
Ladadoos Posted February 23, 2017 Share Posted February 23, 2017 (edited) 8 hours ago, MephistoRoss said: Seems like this is a bug in the lua script of the custom map. So I am not sure what you want the devs to do with this? I did take a look at the one and only lua script required to run this map and saw nothing which should lead to an error. What's more strange is that, according to Geradon, this only happened one time. If it's a 'true' script error it should crash all the time (assuming the lua file doesn't change its own script ), not just randomly. Edited February 23, 2017 by Ladadoos Quote Link to comment Share on other sites More sharing options...
fiki574 Posted February 23, 2017 Share Posted February 23, 2017 If it continues to happen, i can fix it with the tool. It even says the line where the error is. Quote Link to comment Share on other sites More sharing options...
Ladadoos Posted February 23, 2017 Share Posted February 23, 2017 (edited) 54 minutes ago, fiki574 said: If it continues to happen, i can fix it with the tool. It even says the line where the error is. 1. OnOneTimeEvent 2. { 3. Conditions = 4. { 5. PlayerHasGameLost {Player = "pl_Player1"}; 6. }, 7. 8. Actions = 9. { 10. PlayerGameOver { Player = "pl_Player2", TargetTag = "spectator2"}, 11. PlayerGameOver { Player = "pl_Player3", TargetTag = "spectator3"}, 12. }; 13. }; 14. 15. OnOneTimeEvent 16. { 17. Conditions = 18. { 19. PlayerHasGameLost { Player = "pl_Player4"}, 20. }, 21. 22. Actions = 23. { 24. PlayerGameOver { Player = "pl_Player5", TargetTag = "spectator5"}, 25. PlayerGameOver { Player = "pl_Player6", TargetTag = "spectator6"}, 26. }; 27. }; 28. 29. State {StateName = "INIT"} This is the script literally copied from the file, I changed nothing besides the line number on the left for convenience sake. Besides what I said earlier about it being strange that it doesn't always crash if it's a script error, I don't see anything in/near line 18 that could give this crash. Edited February 23, 2017 by Ladadoos Quote Link to comment Share on other sites More sharing options...
fiki574 Posted February 23, 2017 Share Posted February 23, 2017 (edited) Well weird cuz only difference is: 3. Conditions = 4. { 5. PlayerHasGameLost {Player = "pl_Player1"}; 6. }, 17. Conditions = 18. { 19. PlayerHasGameLost { Player = "pl_Player4"}, 20. }, As u can see, there's ";" in first case, and "," in second but that really shouldn't cause problems. You can try changing the "," to ";" so it looks like this: 17. Conditions = 18. { 19. PlayerHasGameLost { Player = "pl_Player4"}; 20. }, Edited February 23, 2017 by fiki574 Quote Link to comment Share on other sites More sharing options...
Ladadoos Posted February 23, 2017 Share Posted February 23, 2017 1 minute ago, fiki574 said: Well weird cuz only difference is: As u can see, there's ";" in first case, and "," in second but that really shouldn't cause problems. You can try changing the "," to ";" so it looks like this: Well, I've written quite a bit of script always using ' , ' at the end instead of ' ; ' and never had issues.That being said though, the only difference I notice that might cause it compared to how I write it is that I write Conditions = { PlayerHasGameLost ({Player = "pl_Player1"}), }, instead of Conditions = { PlayerHasGameLost {Player = "pl_Player1"}, }, Although this also shouldn't cause it because else this script would never work It sometimes working and sometimes not (according to Geradon) is basically why I think it must be something else, but no idea what. Maybe some client stuff. Quote Link to comment Share on other sites More sharing options...
fiki574 Posted February 23, 2017 Share Posted February 23, 2017 Well then probably client behaving retarded as usual. Quote Link to comment Share on other sites More sharing options...
Recommended Posts