Skip to content
This repository has been archived by the owner on Sep 14, 2022. It is now read-only.

Current plan of attack on merging with ModTek #36

Open
mpstark opened this issue Jan 29, 2019 · 3 comments
Open

Current plan of attack on merging with ModTek #36

mpstark opened this issue Jan 29, 2019 · 3 comments

Comments

@mpstark
Copy link
Contributor

mpstark commented Jan 29, 2019

Via Discord convo with @CptMoore and @m22spencer which solves most of the issues that I had with doing this sort of move.

  • Inject method containing ModTek loading code -- something like this, but tested for OS compatibility
var path = Path.Combine(Application.streamingAssetsPath, "../../Mods/ModTek.dll");
if (File.Exists(path))
    Assembly.LoadFrom(path).GetType("ModTek").GetMethod("Init").Invoke(null, null);
  • Inject method call similar to how we were doing it before, calling said method
  • Migrate LoadDLL directly into ModTek
  • Migrate Injector project into ModTek solution
@mpstark
Copy link
Contributor Author

mpstark commented Jan 29, 2019

Might want to use Application.dataPath instead -- might need to have Mac users move their mods folder to do that, but their mods folder is in dumb place so maybe a good thing.

@janxious
Copy link
Contributor

MacOS mod folder is in exactly the same relative place as windows. Try again.

@CptMoore
Copy link
Member

App.config + privatebinpath for injector?

App.config would be also be useful for RT to define the RTML enums to be patched by default.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants