If you like the game and can afford to, please donate to support MegaGlest.
I assume that would not be so easy, because you would need different xml types, a work-arround would be to set a variable to 1 in the <globals> tag of megaglest and ask in startup, wether it's set, or not.
Quote from: MuwuM on 9 May 2012, 17:37:28I assume that would not be so easy, because you would need different xml types, a work-arround would be to set a variable to 1 in the <globals> tag of megaglest and ask in startup, wether it's set, or not.That wouldn't work well, though, as it would only stop MG-only scenarios from playing on GAE, but not the other way around. Not sure what you mean by "you would need different xml types".
megaglest = 1
megaglest = megaglest or 0if megaglest == 1 then -- do something for MGelse -- do something for GAEend
Quote from: Omega on 9 May 2012, 18:57:33Quote from: MuwuM on 9 May 2012, 17:37:28I assume that would not be so easy, because you would need different xml types, a work-arround would be to set a variable to 1 in the <globals> tag of megaglest and ask in startup, wether it's set, or not.That wouldn't work well, though, as it would only stop MG-only scenarios from playing on GAE, but not the other way around. Not sure what you mean by "you would need different xml types".in Globals:Code: [Select]megaglest = 1in startup:Code: [Select]megaglest = megaglest or 0if megaglest == 1 then -- do something for MGelse -- do something for GAEend