-
Posts
1,323 -
Joined
-
Last visited
Content Type
Forums
Events
Downloads
Gallery
Mods
News
Store
Posts posted by AL|EN
-
-
IAP was updated to fix annoying inconvenience of .iemod package files having no default Linux permissions. This happens only when 'unzip' command was used for extraction, using graphic file manager of popular Linux distribution like Ubuntu didn't face this issue.
No action are required from modders as new mod release will create .iemod packages without above inconvenience. This is not really necessary but If you really want, you could regenerate .iemod packages of your mods that won't have new release in foreseeable future. Go to your GitHub repository, open "Actions" tab, you will see the list of "workflow runs". Then click on the latest workflow run and at the top-right there will be a button called "Re-run jobs" (if you don't see this button, it means that the workflow was expired and cannot be run again). Click on it and choose "Re-run all jobs" from submenu. Packages for the latest release should be regenerated.
-
Good news: this is fixed, the Ascension iemod package was regenerated. I will regenerate iemod packages for all mods that I have access but the other ones will contain this annoying inconvenience until the next mod release or regeneration of the .iemod package.
Thanks for reporting.
-
Well, for Ubuntu it works when I use graphic file manager. I'm unable to check all other linux desktop editions.
-
@suy It only happens when you use 'unzip' from commandline. All other extraction method are extracting files with proper rights. I will try to compress .iemod using something different but I don't know if this will fix anything on you end.
-
@jastey Try to update weidu version. From the log I see that you are using WeiDU v24600 - it won't work.
-
I've used Russian version of EE and I was able to reproduce this bug. It should be fixed for next release. Thanks for reporting.
-
-
1 hour ago, Guest Henanigan said:
Would this be related to the LANGUAGE issue above?
No because using %MOD_FOLDER% works for HANDLE_CHARSETS function. How about you try to install ull code example: inside linux https://github.com/ALIENQuake/WeiDU-UTF8 on non -EE and see if it can be installed fine? Also, you can use --debug-assign to see the value of %MOD_FOLDER%
-
Ascension 2.0.18
- added support for Project Infinity dynamic install order
- added LabelType = GloballyUnique to support Project Infinity saving mod components
- significant proofreading of polish translation
- minor corrections to the source text
https://lynxlynx.info/ie/modhub.php?InfinityMods/Ascension&pkg=zip
https://lynxlynx.info/ie/modhub.php?InfinityMods/Ascension&pkg=iemodThe minor corrections to the source text was also applied to Portuguese, Russian, Italian, Spanish. Huge thanks to GoForTheEyes for significant proofreading of polish translation.
@jastey As requested, I'm notifying you about new release.
-
Thanks Cam!
-
On 6/28/2021 at 8:32 PM, Taylan said:
@AL|EN maybe you could shortly summarize the fundamental flaws you have in mind? I don't use Discord unfortunately but I'd be very interested to hear your thoughts.
That's you saying "I want to build skyscraper but I won't read any engineering book that has red book cover"? Do you expect me to summarize 6 years of experiences, ideas and thoughts in a six lines? Here are the glimpse:
- auto-update system
- application model
- backup system
- install/uninstall routine
- debugging
- translation system
Let me stop here by saying that you have to start with good foundations, without 20 years of flawed design that is impossible to change because of compatibility with older mods. If you want to know more, the ball is in your court.
On 6/28/2021 at 8:32 PM, Taylan said:As a counter-example, think about how WeiDU started as "dialogue utilities" and can now do everything. That organic growth from a tool focused on one task towards a tool that can do anything is probably the main reason why it became so messy, which is exactly what I'd like to avoid.
So you don't want to repeat WeiDU mistakes, good. Then you have to learn about all things that makes weidu messy so you don't repeat them. This is no established ground so any design flaw should be eradicated with fire at the begging. This will require strong opinions and making difficult choices. Also, if you inherit the part of the name from WeiDU, don't you think that you intrinsically drive your mindset into the wrong road?
On 6/28/2021 at 8:32 PM, Taylan said:One thing I believe I already understand about the players & modders, and you have to correct me if I'm wrong, is that the community contains both people who are very creative but don't have any programming knowledge, and people who are advanced/professional programmers. So that's something I'm keeping in mind. With the "mod types" I mentioned before, I intend to make it as easy as possible to create certain types of mods (ideally with zero code, just some definitions in a simple format), while also offering a rich Python API for programmatically editing any files you want.
Regardless of how many 'tech savy' modders are out there, you should aim to create something that can be used not only for trivial task but also for advanced tasks and allow low-level modification only for extreme cases. All of this with limitations to not allow one line from previous mod to completely damage game resource so all other mods can't be installed.
@subtledoctor "About this, feelings correct you have."
That's pretty much what it's needed in order to not fall into weidu trap. Application model should have two things:
- a single system-wide GUI app that handles everything except actual game data modification like install order routine
- a multiple versioned system-wide app that handles game data modification
A nice foundation for unlimited growth. A man can dream...
-
-
You need to PI for this. Before you jump in into such huge mod list, please get yourself familiar with the application, read FAQ and try to install few mods by you own.
-
When there is a chance for something new I take closer look at the topic with attention and curiosity. A novice can shed new light on old, stiff and unchanged things for years. This gives a chance that at least some aspects of modding can be improved. Even if a lite bit.
Looking at your soundset installer project, I see potential in it. I would suggest focusing on it because it does not require a lot of work, it is independent of other tools and will allow you to make mistakes (you will do them for sure), learn from them, so that you will know how to design bigger things if you ever get on with them.
But let's focus on your PieDU proposal:
The natural course of things is that as a developer, the first thing you do is look at the programming language, code, directory structure and size of files. This makes you set the project on failure from the very beginning. What you should focus on are: players, modders, mod ecosystem. Then, on existing solutions, tools. Then on how everything connects and what can be improved.Your current design inherits all of WeiDU's current fundamental flaws. It's too much to write elaborates here. If you want to chat you can find me on Discord: https://discord.com/invite/yTzjMTb
10 hours ago, Taylan said:To be honest I fear that I'll end up being all talk and little action because my actual job is keeping my quite busy and I have some other hobby projects too, but let's see where it goes.
If you announce at the beginning of the discussion that you will not have time for the project, it does not look serious. You will need a lot of time in order to comeup with something serious.
-
IAP was updated to fix edge case was a mod has multiline comments with "VERSION x". Now multiline comments are also ignored during getting VERSION value.
-
@jmaeqCan we have new release with workaround for weidu bug?
-
27 minutes ago, jastey said:
Why is the above change of commenting preferable?
It isn't preferable for anything other than this case, where mod is using multi-line (/* ... */) comments and at the same time, it has 'Version *' inside that comment Filtering multiline comments would increase tp2 scanning time ~2 times. Someday, it won't be the case.
-
@jastey Actually, as of today, it would be better to make minimal adjustment to the tp2 file and replace:
/* * "Coran's BG Extended Friendship Talks" * Version 4 Combined Tutu/BGT/BGEE installer * Domi Sotto, updated by berelinde * 2015-01-16 * BGEE compatibility update v4 by AstroBryGuy */
to
// "Coran's BG Extended Friendship Talks" // Version 4 Combined Tutu/BGT/BGEE installer // Domi Sotto, updated by berelinde // 2015-01-16 // BGEE compatibility update v4 by AstroBryGuy
Such simple change is not worth new release but when I"m on it, I could send you PR with LABELS and/or UTF8-based HANDLE_CHARSETS. Wana try?
-
@grodrigues You should start with providing whells.debug file and weidu.log
-
I can reproduce, that's indeed a bug. It will be fixed in the next version.
-
2 hours ago, Jack3150 said:
Not sure if this is a bug or something I done wrong on my end but when I try to load EET v13 on Project Infinity, it still shows up as RC12 instead.
That's usual case when tp2 VERSION wasn't updated. It is RC 13. Next version should hopefully have correct tp2 VERSION.
-
As long as minor BG1EE/SoD mods can be installed it is a reasonable idea especially when you consider required maintenance. When you create those patches, make sure to post them because it's always easier to adapt the patch than to create it from scratch.
-
@Hack'n'Slash Sorry but what does 'more of all the options the mod gives' means? Do you mean the names of mod components?
-
@Hack'n'Slash Are you talking about mod conflicts/overlapping or 'Recommended/Tactic/Expert' status?
SR patches
in Spell Revisions
Posted
@Bartimaeus The "UNDEFINED STRING" is happen because of WeiDU 247. Care to apply temporary workaround by changing:
LANGUAGE ~English~ ~english~ ~%MOD_FOLDER%/languages/english/setup.tra~
to
LANGUAGE ~English~ ~english~ ~spell_rev_rev/languages/english/setup.tra~
?