severedsolo

ShowKCTWarning is deprecated. The mod now reads KCT's settings file. If you're getting the warning then your settings are wrong. Either disable Facility Construction in KCT, or in Bureuacracy.

Just give me a prod through the usual channels if you need me to update the title if you do any further releases. Otherwise, she's all yours

Take it up with your Planet Pack author. E+ uses the same progression as the stock contracts. It decides this based on the Science Multiplier. So if you're getting the wrong body next then the Science Multiplier for that body is off.

Where Can I Go 2.2 Released Added ability to automatically recalculate for rescaled systems (if we already support that system) - see Original Post on forum for more details

Actually those contracts (the stock progression contracts) are the only ones that will still probably work. The very simplified version of what's happening is that Contract Interceptor listens for the game announcing "I just made a new contract", then goes into that contract and manually changes the values. Stock progression contracts aren't "offered" in the traditional sense so we patch them in the game files instead, so they will continue to work whether Contract Interceptor is running or not. The reason we do it this way is so we can handle mod contracts too (we don't care where the contract is from, we just care about it when it gets offered). What's happening here is that upon returning to the Main Menu something is causing that "I just offered a contract" announcement to be made, and Contract Interceptor is running into a problem. (If I were to take a guess, I'd say its because it's trying to access Bureaucracys settings but as the main mod isn't running right now that causes it to fall over). Once the Interceptor has fallen over, it stops running (and therefore listening for the new contract announcement) which means why subsequent contracts don't get changed. As you observed, any contracts created while Contract Interceptor isn't running get saved with the funds still in tact and will be reloaded with your game. Usually we change the values before the game saved and KSP never knows any different because it saves the changed values. There has never been a need to go back and change values retroactively before because we changed them "at source" which is why once it breaks it stays broken. I will say, all this means "I know what the problem is" not "I'm going to fix it". It is a relatively simple fix, but I really did mean it when I said "this will be the last release of Bureaucracy" and I'd have to set up my KSP/ mod dev environment again. On the other hand I don't like leaving mods "broken" (even if the workaround is quite easy: "don't switch saves halfway through a play session you psychopaths" (/s if that wasn't obvious)). Which is a very long winded way of saying "I might fix it, I might not but it would be an easy fix for someone who wanted to fork Bureaucracy, and as I'm no longer actively modding I would not be hostile to forks like I was before".

BepinEx needs a little tweaking in winecfg before it will work: https://docs.bepinex.dev/articles/advanced/proton_wine.html

The game is not fun right now. It's that simple. It's nothing to do with you guys, I just don't want to mod a game I'm not playing.

There's your issue. Bureaucracy only fires the budget advancement events every 1 in-game day, and that timer is reset on a scene-change - you don't lose out as it does catch up from the last time the event fired. Technically this is working as intended. There are probably things I can do to make that a bit friendlier though, like exposing the polling interval in the settings, or catch up on a scene change. (If memory serves there is a reason it's not doing it on the scene change but I don't remember what it is). Raised #28

Are you by any chance changing scenes before a full in-game day has passed? Same question @Pippin (Also side note: Gaming on Noveau drivers and pushing it with Visual mods? You're very brave!) No, but it might come in future. I prefer KAC myself, so you may find next time I get motivated to play I decide to change it back. No promises obviously.

Nah, I'm pretty much retired from KSP1 modding at this time. I did glance at it and decided I hated the way it was written and wanted to re-write it, but motivation fell away when I stopped playing KSP

I've just pushed the changes to Github. Basically - because the funding allocations are stored as floats - which isn't very UI friendly, I was storing the UI allocation settings separately in an int then updating the managers. The default allocations in UIController were overriding the settings. It was a bit of a stupid/convoluted way to do it anyway (as allocations were being held in two places) - so I changed it to pull the allocations out of the Managers themselves, but round it instead.

Can you put the log in a file rather than pasting it as a quote - it messes up the forum for mobile users and makes it easier for me to search for what I'm looking for in my text editor. You can upload the log to DropBox/Google Drive etc and send me the link.

@Pippin- if you can reproduce then do so and send me a log

Bureaucracy 1.6.1 Released Fix Allocation Settings not persisting between scene changes

Bureaucracy 1.6 Released Bureaucracy will now yield control of the science system back to Kerbalism when not running in a Career game. Fixed an issue where Bureaucracy would incorrectly believe the time to be Y1D1 the first time it is used in a save, even if it was an existing save. Added setting to turn off Messages (SuppressMessages) (bool). Settings version updated to 1.6. Previous version 1.4.0.1 - upgrading from a version of Bureaucracy prior to 1.4.0.1 will result in settings being reset to defaults. Barring any major issues being found this will be the last release of Bureaucracy. I'd like to thank you all for your support over the last 7 years.

I'd rather rip my own eyeballs out with a rusty spoon.

You're using the old file structure. SpaceWarp and all your mods now go in <KSPDir>/BepInEx/plugins. Should look a little something like this (in my example KSP2 ModDev is the root directory of KSP2)

Significant. On the same hardware (i5-9400, RTX 2060 for reference) I'm getting 30FPS (ish) on Windows, and a grand total of 4 on Proton (GE-50 but Experimental is no different)

How the... how has this got 3 years in with nobody pointing this out. It definitely does need fixing - mod should not be running in other modes and that's going to cause issues down the line (at the very least it's performance overhead you don't need). luckily it's a one line fix. Thanks for bringing it up. Fixed in dev, WIll hold off on a release in case anything else comes up first.

Because Discord is terrible for this kind of reporting. If you're not on Discord at the right time, you either miss it or have to wade through hundreds of messages to find it. God forbid you want to go back and review what bugs have been reported later. Forums are pretty good at this, you can review the bug report subforum at your leisure. There's also the issue of search engine indexing. Issues reported on the forum will be indexed by search engines and anyone googling their problem will find it (and hopefully any workarounds people have found).

I'm doing a final pass of mods before I close up shop on KSP1 modding. As a rule I'm restricting this to bugfixes, but I'm making an exception with PAWS because I plan to give it a bigger performance/UI pass. Are these still wanted? (Last orders please!)

Kerbalism and Bureaucracy talk to each other. Kerbalism collects the science and hands the processing over to Bureaucracy. Re refunding parts etc. Bureaucracy will just ignore anything that isn't the contract system giving funds. Also minor point (to everyone): I'm sure y'all figured this out already considering how little I've been here but support for KSP1 mods has been withdrawn. Mods may or may not be ported to KSP2 in the future depending on how development of that game goes. If anyone has any burning bugs they want fixed before I retire from KSP1 modding entirely please call them out. (I plan to be back for KSP2, but see the open letter for my current position). Thank you for your support over the last 7 years, you're all stars.

Very cool but your source link is broken just FYI. Getting a 404

@starfall22 Contract Configurator lists every contract loaded into it, and tells you why that contract hasn't fired. It's a feature. If it bothers you as you say you can switch to the Available tab, but you do get used to it. In order: You don't, No, and No. The pack is designed to take over from the stock Exploration Contracts. It's all about "Firsts". So the contracts fire when there is a "First" to be done, and if you've already done the "First" then we're not interested. Assuming you've been using the stock contracts before now, you haven't missed out on anything. The reward structure of Exploration Plus is setup to mimic the stock contracts. It looks a little higher because we streamline a few steps (like not making you do a rendezvous around every body before you can proceed) but the overall compensation for a body should be the same as you get from stock. In short - if the contract isn't firing, don't sweat it, you haven't lost out. The pack purely uses the in-game progression system to track your progress, you can't be locked out of a mission because you haven't done a previous one (ironically enough that's what the Contract Configurator requirements window is trying to tell you!) Just checked and the contracts are setup with science rewards. If this is happening it would be a Contract Configurator bug and would need to be reported against that mod (with logs etc).

@CoriW - that was a fun read, (and I'm so glad you got to the bottom of it rather than me having to!). If you ever feel like sending me a PR on Github I can merge your changes if I ever decide to pick up modding again. Thought I'd share a little insight into why it hung (and stopped logging). So when you click the button, as you rightly say, it queries the BudgetEvent to get the completion time of the event and display it in the UI (it doesn't calculate it again, it just pulls the UT timestamp out of the BudgetEvent class as it's already stored there). The thing is, that timestamp is how many (in game) seconds have passed since the game started, not every helpful for a UI. So we call a method in the Utilities class that converts a UT timestamp to a more helpful string (Yx Dx). That method is a bit crude, it just counts the number of years that need to pass to get within a year of the timestamp, and then when we have less than 1 year left, does the same with days. Works well in (nearly) all situations and doesn't log (because honestly if I logged every time the UI updated, you'd be spammed to hell). So, the UT to Date String method grabs the completionTime from the BudgetEvent, and keeps adding a year at a time until it hits the timestamp. Uh how many years does it take to reach infinity again? And thats why it hung. Bureaucracy got stuck in an infinite loop (literally), never released the main thread, and nothing else was allowed to run. As an aside - I'm not really sure why it decided the completionTime was Infinity rather than 0 - but even if it had picked 0, your game would have frozen the moment you loaded your save (your timestamp of 0 is Y1 D1, and if the timestamp was in the past then you'd be stuck in an infinite loop of budgets firing).