First of all, please understand that my English is rubbish.

My joining here is very recent.
For a while, I focused on uploading mod sources, but I would like to get some help from the modders here.

I've been making mods for quite some time. I started making mods in 2010 and have reached the present, but there are many gaps in the middle.

Where I was, activity has declined significantly since the release of the remastered.
This is because modding is also being done in Remastered, but it is less active compared to 1.16.

I've been working on mods for both 1.16 and Remastered, but I'm currently focusing on 1.16.

From now on, I will ask you a few questions about modding.


1. Excluding GPTP, I would like to know what plugins are currently used for version 1.16 modding. And I would also like to know how to use it.

2. I'm curious about how to apply plugins to remastered modding.

3. How do I use the DatExtend plugin?


I can do the rest of the modding work to some extent except for the plug-in work.
From now on, it seems that there will be many things to ask here.

Answer to question 2: you put the plugin .dll files in the \samase\ subfolder in the mod directory, then add their names to \samase\plugins text file. For example:

Where can I get those dll files? Once I got mtl.dll.

Once I applied the mtl plugin as I said, it says it requires mtl.ini file. I somehow made mtl.ini, but I don't know what to do afterwards.

Thanks for replying once.

MTL.ini should generally be put under \SAMASE\ as well. But it can also be locale-specific (so go under \Locales\FooBar\Assets\Samase\), it works.

If you need the full big list of what can be done with MTL.ini, check here:
https://gist.github.com/neivv/2b2851b91e697595f7936d69c71516da

The plugins should be available on Neiv's github... but I'm not seeing up to date versions there (actually none for MTL), I've been getting them directly from Neiv himself. I'll ask him to fix that.
https://github.com/neivv/aice/releases
https://github.com/neivv/aise/releases (actually this seems almost up-to-date... almost)
https://github.com/neivv/mtl/releases

Post has been edited 1 time(s), last time on Feb 22 2023, 12:23 pm by IlyaSnopchenko.

thank you Once you know the role of each dll. But I still don't know how to use it.

However, in the case of aice.dll, I found out that the usage is the same as icecc, considering that it is in charge of iscript and requires iscript of text files. It also seemed to overwrite the existing iscript.bin.

I found out that aise.dll is a plugin in charge of AI. Does this also require text files like ini, txt?

And I wonder if these three plug-ins, mtl, aise, and aice, are also available in 1.16.

Unfortunately the gptp plugin didn't seem to be available. It seems that the plug-ins available in the remaster are very limited.

In addition to the other three you mention below, you may want to look at IsDbg, which prevents iscript-related crashes and helps with debugging. [/quote]

I'd recommend using Farty's branch of GPTP which integrates DatExt with GPTP. Newer versions of PyMS have the ability to add extended entries to .dat files which can then be used as normal. FireGraft gets a little wonky with extended unit entries, so if you're additing additional units that need buttonsets, I'd recommend using something like Farty's WIP graft compiler (although I don't have a link to it on hand)



I believe all three of these plugins can be used in 1.16.1. Aise primarily allows you to use additional commands in writing AI scripts, you'll need to use it with something like PyAI to modify aiscript.bin. You're correct that GPTP is not available in RM.

Yes, these should work in 1.16. never tried it though.
Together, these three plugins allow to do some quite remarkable things, far beyond that which was ever available in old times. AICE in particular is a powerhouse that allows pretty rad effects to be implemented, going beyond strictly graphics. I am very enthusiastic about it, and there's always something new to do with this plugin. :-)

AISE requires you to use a compatible fork of PYMS->PYAI to edit the aiscript.bin/bwscript.bin files. It fixes some AI issues from unmodded game, and of course adds new commands that significantly expand the Scripting capabilities, and add more opportunities to interface between AI Scripts, triggers and iscript.

Post has been edited 1 time(s), last time on Feb 22 2023, 10:24 pm by IlyaSnopchenko.

Thank you for answer.

As you said, I tested everything.



oh, i used this Recently I've been using DatExtend which has been merged with gptp and I didn't mention this in my initial question.
I used DatExtend before being merged into gptp in 2020 and only units, flingy, sprites, images data extension was successful.

However, as I said, there was a problem when running the plugin-applied mod with FireGraft. The program could not be closed normally. And in this state, it seemed to be initialized with the existing data whenever a new save was made. When running, an error saying that the command length was incorrect came out and it could not be executed. In addition, there was a phenomenon that the button set was not applied, and there was a crash when selecting a Zerg egg and Cocoon placed in the map editor.

This is my experience using the DatExtend plugin in 2020.

A while ago I rediscovered DatExtend and found that it was merged with the gptp plugin and tried it out.
I tried increasing all the data to 65535 in datex.cpp as an experiment, and it built successfully, but I haven't noticed any change since. I'm wondering what to do next.

I also found a serious bug while using this gptp plugin. A crash occurs when Corsair and Valkyrie's Air Splash attack hits. Additionally, some spells such as Dark Swarm, Consume, Stasis Field, and Disruption Web are not used or behave erratically. I also found a bug where if I right-clicked a non-enemy building with my unit, it would be judged to follow it. I didn't touch these parts and found out that this is a bug in gptp itself. Because of this, the problem was difficult to find and could not be resolved.

It's a pity that gptp is not available in the remaster. I wonder if the day will come when gptp can be used in the remaster as well.
Still, it's comforting that some of the features of gptp are available as mtl plugins.


I experimented right away. I knew that I just had to change the dll extension plug-in to the qdp extension, and I immediately tested it and it was definitely usable. However, there were some problems with the AICE plug-in. Some texture frames in the game are displayed as if they are lagging. This is a problem that did not exist when applied to the remastered. Other than that, there were no other issues.
It seems that the solution to this is not well known.


Thanks to everyone who responded. However, there are not many other courses for mtl and aise, so I think I will still need more time.

No idea about AICE and 1.16. As I said, I haven't used any of these plugins there and I'm not intending to work with 1.16 except for updating some of my old campaigns (after I finish my current project, if ever).

Just in case, here's the most recent version of AICE that I have.
The comprehensive guide to its features is found here:
https://github.com/neivv/aice/blob/master/Documentation.md

Attachments:

Oh, as a result of using the latest version of AICE you attached, the problem is gone! thank you! However, I'm afraid that another unexpected bug will appear.

I came back.
Thanks to those who helped.

I have a few questions and something to report.

There is a problem with rally points when using the mtl plugin.
I found a bug where the right-click rally point on the minimap doesn't work.

It seems to be solved by adding the [Rally] part in mtl.ini, but it is only solved in Remastered, and in version 1.16, it is completely impossible to specify a rally point by right-clicking.
Also, if you don't add the [Rally] part in Remastered, you can't use the right-click rally point on the minimap as well.


how to run the latest version of PyMS. To experiment with data expansion, I decided to try the latest version of PyMS.
I don't know how to run it because it's a pyw file format, not an exe file.
However, I found out that I needed a Python program and immediately installed Python (2.7.1.2ver).
Is it correct to run pyw after that? When I run pyw, I get the following error and it doesn't run.

"PIL is missing. consult the source installation section of the documentation"

how do i solve this? I think I need to download PIL, but I don't know how to download it.

Hey Revenant. There are some basic installation instructions in the readme, which can also be viewed online on the official github repository: https://github.com/poiuyqwert/PyMS#installation

If you are still having trouble, you can also join the SEN Discord server, where you can get real time help. On average there is usually more people helping on Discord nowadays, and the real time aspect of Discord is useful for back and forth help.

Good luck!

I found that I need to type "python2.7 -m pip install -r requirements.txt" using command prompt.

For example, "C:\Python27:python2.7 -m pip install -r requirements.txt" Is this correct? Even doing this doesn't work.

Assuming (for the example) that you put PyMS in C:\PyMS\, you could try "C:\Python27\python2.7.exe -m pip install -r C:\PyMS\requirements.txt"

thank you! I finally succeeded!

However, only PyDAT.pyw does not run properly. The rest of the program works fine.

I wonder why PyDAT.pyw is not running.

I will attach a screenshot of the error.

I want to experiment with data expansion, but only PyDAT.pyw doesn't run.



Post has been edited 1 time(s), last time on Mar 20 2023, 1:07 pm by Revenant.

Just wondering... how do you actually install a mod?

Mods are usually packaged as EXE files that you just need to double-click to run.