[X3LU] Mayhem 3.21b
Moderators: Moderators for English X Forum, Scripting / Modding Moderators
****, I'm stupid.
Your invasion is on-progress but it will take more time, as I forgot to reduce the time elsewhere in the code... i.e: you're back at 24 hour waves.
Meanwhile, grab this. That will fix the timer for the next waves.
Your invasion is on-progress but it will take more time, as I forgot to reduce the time elsewhere in the code... i.e: you're back at 24 hour waves.
Meanwhile, grab this. That will fix the timer for the next waves.
Thanks a lot, but can you tell when it's coming? I ran SETA for several ingame hours (until 2-4:30) and still didn't get the 240 minute warning.
I.E is it 24 hours after the first wave (so around 2-7:30) or is it 48 hours after reaching threat 2 (2-20:20) ?
EDIT: I get it now. Reset function is called after invasion ends and if there is no targets. I must have rolled high and it's coming about 26 hours after the first wave.
I wonder, do you have a documented version of your project or did it grow organically and now it's a mess? (happens to everyone, i am sure).
I.E is it 24 hours after the first wave (so around 2-7:30) or is it 48 hours after reaching threat 2 (2-20:20) ?
EDIT: I get it now. Reset function is called after invasion ends and if there is no targets. I must have rolled high and it's coming about 26 hours after the first wave.
I wonder, do you have a documented version of your project or did it grow organically and now it's a mess? (happens to everyone, i am sure).
Mod projects (amateur software projects in general, but plenty of commercial software projects too) don't generally follow engineering practices like design, documentation, unit testing, code review, consistent coding style, etc. To go through all that requires a lot of time to learn about them, to get good at them and to apply them, and likely that's at the bottom of priorities for people that do this as a hobby, especially since that time could be used to add more features to the mod. As modding users we should be happy and thankful the mod authors are able to give us all these great mods made in their spare time that they could have used for so many other things.
All that said, the capacity to perform clean software development also largely depends on the tools available for the job, a programming language like MSCI for example would require very strict rules of conduct/coding style to be able to develop clean, scalable projects, the language itself provides few facilities to do so. In other words, just take a look at Egosoft's own scripts (wrote by people that made the game, the language and are being payed to write code), many times it's worse/more of a mess than LU code in my experience.
All that said, the capacity to perform clean software development also largely depends on the tools available for the job, a programming language like MSCI for example would require very strict rules of conduct/coding style to be able to develop clean, scalable projects, the language itself provides few facilities to do so. In other words, just take a look at Egosoft's own scripts (wrote by people that made the game, the language and are being payed to write code), many times it's worse/more of a mess than LU code in my experience.
X3LU 1.5.2/1.7.0 Youtube series with: IEX 1.5b + LUVi, SIaF r7 (previously also used Phanon Plus 4.02, Revelation Plus 1.04, Diverse Game Starts - LU Edition)
[ external image ]
[ external image ]
-
- Posts: 127
- Joined: Sun, 8. Jan 17, 15:04
-
- Posts: 127
- Joined: Sun, 8. Jan 17, 15:04
@Jorbarbe I see that you started patching process again, just want to remind about this bug, about MLCC not sending ships which hull damage is less then 10% to repair dock.
-
- Posts: 127
- Joined: Sun, 8. Jan 17, 15:04
Fond it on page 187, but did not understand why he asked for it:)
I found which files were changed and where to fix it back in script editor by myself, so I dont pretend that to be fixed in patch.
I found which files were changed and where to fix it back in script editor by myself, so I dont pretend that to be fixed in patch.
In my previous run, if you don't have enough money for maintenance, then the ships are dinged 1%. The MLCC then would not send them when you call MLCC ships (and the MLCC would not send them for repair either).Darkternal wrote:Fond it on page 187, but did not understand why he asked for it:)
I found which files were changed and where to fix it back in script editor by myself, so I dont pretend that to be fixed in patch.
So Joubarbe makes it so that the MLCC will only send the ships for repair if the damage is 10% or higher.
The problem you complain about is that the MLCC would NOT automatically send damaged ships for repair.
They are 2 different problems.
Last edited by VincentTH on Sat, 24. Feb 18, 16:10, edited 1 time in total.
-
- Posts: 127
- Joined: Sun, 8. Jan 17, 15:04
-
- Posts: 127
- Joined: Sun, 8. Jan 17, 15:04
May be I know english bad, but as for me - you wrote about same problem with different words. I does not complain about MLCC does not send ship damaged less 10% to repair (I cannot understand why, but so be it if it is so needed). But if it is done so then I think it would be correct if it will give those damaged ships to run commands. Now it is situation where player should manual send all the dock to repair, because those "1%" damaged ships are difficult to find, and none repaired they are unused ballast.VincentTH wrote:So Joubarbe makes it so that the MLCC will only send the ships for repair if the damage is 10% or higher.
The problem you complain about is that the MLCC would NOT automatically send damaged ships for repair.
Well, isn't it the same exact thing?! Now that I messed up the value, it's only sending ship to repair at <90%.VincentTH wrote:Yes, MLCC does send ships for repair. I don't remember exactly the % threshold, however.Joubarbe wrote:Is MLCC supposed to automatically send them for repair? I don't remember having touched anything else about the MLCC (apart from unrelated menu stuff).
EDIT: It's going back to normal. != 100%. I should never had touched this f*cking MLCC shit.
The 10% or greater damage is used in preference over 1% damage, is because at 10% damage, the speed of the ship start to degrade. Also it is hard to see on the sector map the difference between 100% Hull and 99% Hull, and the user is left to scratch his head as to why the ship is not sent to battle on the MLCC Assist call.Darkternal wrote:May be I know english bad, but as for me - you wrote about same problem with different words. I does not complain about MLCC does not send ship damaged less 10% to repair (I cannot understand why, but so be it if it is so needed). But if it is done so then I think it would be correct if it will give those damaged ships to run commands. Now it is situation where player should manual send all the dock to repair, because those "1%" damaged ships are difficult to find, and none repaired they are unused ballast.VincentTH wrote:So Joubarbe makes it so that the MLCC will only send the ships for repair if the damage is 10% or higher.
The problem you complain about is that the MLCC would NOT automatically send damaged ships for repair.
@Joubarbe,
Sorry about the MLCC mess. I understand your frustration.
Now, this fix does not seem to fix the problem of pirates spawning in the user's sector:
Sorry about the MLCC mess. I understand your frustration.
Now, this fix does not seem to fix the problem of pirates spawning in the user's sector:
The Teladi took out the pirate shipyard in Nopileos Memorial, and now pirates are spawned everywhere in the user's sector.2.3.0 Change log:
FIX: Some ships were still spawning in Player sectors.