polymorphable
polymorphable copied to clipboard
makrohn
Release tarball
Could you make and upload release tarball of the game to provide it as openSUSE package please?
I don't have any idea how to do this, but the best bet for someone would be to use the 0.18 concurrency tag, https://github.com/makrohn/polymorphable/tree/flare0.18_mod_only
It's be dependent on Flare 0.18 Engine, https://github.com/clintbellanger/flare-engine/tree/branch0.18
I'd just call it 0.18 to match the engine version - anything else has little to no meaning.
Both of polymorphable and flare-game provide mods/mods.txt file. Should they conflict each other?
Also I've found some *~ files:
[ 104s] polymorphable.noarch: W: backup-file-in-package /usr/share/games/flare/mods/polymorphable/maps/demo.txt~ [ 104s] polymorphable.noarch: W: backup-file-in-package /usr/share/games/flare/mods/polymorphable/tilesetdefs/tileset_lpc.txt~ [ 104s] polymorphable.noarch: W: backup-file-in-package /usr/share/games/flare/mods/polymorphable/tilesetdefs/lpc_ortho.txt~ [ 104s] polymorphable.noarch: W: backup-file-in-package /usr/share/games/flare/mods/polymorphable/maps/test.txt~
;)
They should not conflict - each will get copied to their own game directory.
I'm not 100% sure of the syntax (I have a weird setup on my VM), but I'd guess that if a user installs the Polymorphable package, and runs "polymorphable" in their terminal or clicks a polymorphable icon, that should actually run the command:
flare --game-data=/path/to/polymorphable/files --game=polymorphable
That way, the executable knows where the mod files are found, as well as which settings to use.
Oh, I just noticed - you should probably install the Polymorphable mods files to /usr/share/games/polymorphable, and use the --game-data option to make sure the executable knows where they are. Then, Poly's mods.txt and Flare's mods.txt won't conflict.
So I shouldn't install Polymorphable to /usr/share/games/flare. OK. Great thanks!
Now I have /usr/share/games/polymorphable/mods/polymorphable, execute flare --game-data=/usr/share/games/polymorphable --game=polymorphable and get "Mod "polymorphable" not found, skipping". The same with flare --game-data=/usr/share/games/polymorphable/mods --game=polymorphable & flare --game-data=/usr/share/games/polymorphable/mods/polymorphable --game=polymorphable… Could you help me please?
The game could be run and played but settings don't appear and the game became unlocalized.
sudo ln -s /usr/share/games/flare/mods/default /usr/share/games/polymorphable/mods/default fixed it. Should Polymorphable require the main flare-game package (or just flare-data with mods/default dir only?) and should such a link be done?
Poly shouldn't require any of flare-game. If it does, that's a bug in how we're currently handling things. You WILL need a copy of the mods/default dir however. There's currently a discussion on how to handle this. Ideally, the default mod would be shipped with flare-engine, not with any of the games.
@pennomi , so should mods/default be shipped with engine package and should a link (copying is worse imho) from it to polymorphable be done?
Notice that the default mod is currently located in the flare engine repo. I'm unsure where it should be installed (we've gone back and forth on that). But it definitely shouldn't be included with any games; it should be packaged with the engine. Maybe one of the guys over there can answer the question of where it should be installed.
@makrohn , here is a temporary link for openSUSE users to install Polymorphable: http://software.opensuse.org/download.html?project=home:DarkSS&package=polymorphable . I am going to submit it to the games repo after next flare-engine release. Thanks!
I just found this issue here. Thanks for packaging polymorphable for distros :)
There were long discussions how to distribute games depending on the flare-engine. Basically flare tries to follow the XDG spec. https://github.com/clintbellanger/flare-engine/wiki/Directories
Also have a look at https://github.com/clintbellanger/flare-game#the-simplest-setup
Now that #46 is pulled, a release tar ball should be easily produced using
git archive --format=tar.gz HEAD > ../poly_release.tar.gz