|
|
Post by damooseneo on Aug 30, 2020 23:47:30 GMT
Using the mse command line call to build an installer, I end up with a full package of my game, supporting symbol fonts, and the styles I selected. When I distribute the installer, users cannot install the styles, JUST the game and symbol fonts. If I "move" my style files out of data and run the installer as though I'm a new user of the files I see the same thing; the styles are grayed out, won't install, but the game files WILL.
Any thoughts?
|
|
|
|
Post by damooseneo on Aug 31, 2020 1:42:17 GMT
Bug "found?"
The game has two basic designs; everything else is a slight variation on that. So I have all of my definitions per normal in the "game" file, and a pair of style files for each basic design. Each style has a header, does an "include" of its relevant basic design (call is all lower case, just like the files and directory names), and the rest of the style file is the unique elements or unique positioning. This gives me the ability to quickly update the elements common to the 4 or 5 otherwise unique styles without mucking around with 4-5 separate files to copy & paste the same tweak.
Early on, it (2.0.1) pitched a fit; despite including a dependency for the game file, it complained and wanted a "Game.mse-game" dependency instead of just "game.mse-game" dependency. So I list it, just to make the console happy, and it worked. APPARENTLY the installer sees this as a totally unique dependency? And was refusing to install those styles because the dependency was missing? I commented out the capitalized dependency line and presto-bingo, I can (re)install the given styles. MSE itself (2.1.1) doesn't complain, but when using 2.1.1 to build the installer I get a "Warning: <style> uses files from the package "Game.mse-game" but it does not list a dependency" ...but, in the end, the installer seems to work.
Any idea why its kvetching about a missing dependency that's actually there?
|
|
|
|
Post by damooseneo on Aug 31, 2020 13:13:04 GMT
So, confirmed: its my capitalized game dependency that is screwing with the installer. Generating the installer file and then manually editing out that line allows the styles to install as appropriate.
So NOW the question is: why does MSE throw a warning requesting a case-sensitive "depends on: Game.mse-game XXXX-XX-XX" when "depends on: game.mse-game XXXX-XX-XX" is already present?
|
|
|
|
Post by damooseneo on Sept 2, 2020 15:51:21 GMT
Took a page out of the VS System template and used the opportunity to clean up duplicate/dependent images and made a "game-common.mse-include" folder, include file, and my roster of common/shared items.
Doing this eliminated the complaint about the "Game.mse-game" dependency, so I was able to finally remove that line and reduce complaints in the installer.
Installer new issue: because game.mse-game depends on the "common" folder, the dependency is in place. The installer now kvetches that "package game-common.mse-include not found" when attempting to install. Similar complaints were made about the Game.mse-game from installer testers. Everything goes smoothly if everything is unticked besides the "missing" package and that is installed first; the rest of things are installed like clockwork. But it will not, in one shot, install the full game.
EDIT: Also a weird note; it "randomly" installs ONE of the styles without complaint, even if I don't select to install it...I say "random" because I bet there's a reason but nothing clear.
|
|
|
|
Post by damooseneo on Sept 3, 2020 16:32:29 GMT
Further weirdness:
I have Style A and Style B among my styles. Style B is, for all purposes, a duplicate of Style A but a "double card." Rather than make everything redundant, I wrote Style A, it has all of its files, and wrote Style B to refer back to Style A's source files (images, assets, etc). So Style A has a full set of items for the style, its style file, its image/icon, and Style B is basically the B-style file and the image/icon. The generated installer file DUPLICATES all of the dependencies under Style A, while also listing everything for Style B (which are all listed in its own style file). This seems to have no effect, but this is the only entry duplicating the dependencies.
Manual edits of the Installer file to remove the "game-common.mse-include" dependency from JUST the installer file (its still in the style and game files, etc) still result in the complaint from the installer about the missing item. I can use the installer to install JUST the "game-common.mse-include" file, and that happens just fine, but it also installs one style which is not selected.
I'd really appreciate any insight or experience in compiling this here.
|
|
