Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mapedit has not been taken much into account, and can crash; especially with mods. #104

Open
Lemonymous opened this issue Jul 28, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@Lemonymous
Copy link
Contributor

The console command mapedit will bring up a map editor. Maps in the map editor can be tested, which launches a non-standard mission with a pretty bare-bones mission object. This mission object is the same for every mission in the map editor.

If we can find this mission object, and can detect when this mission starts and ends, we could try to make it operate more similar to a standard mission. Or alternatively, maybe make it operate more similar to Test Mech Scenario, since both of these missions share the trait of not have a save game to refer to.

I have spoken briefly with narD, who has made several videos showcasing neat interactions in "narD's Lab" using mapedit. They could confirm that the map editor is not stable when using it with mods.

@Lemonymous
Copy link
Contributor Author

Update:
The mission object used in mapedit is in fact the same one used in Test Mech Scenario: _G["Mission_Test"]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants