Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tron359]

Hey,
I'm sorry to necro this post,
based on your last reply, have you been able to build your project into a shareable state?

[Sarissofoi]

I second it.

[xenoargh]

It's been working for months now, like a lot of other things I have on my hard drive.

[tron359]

Oh that's awesome,
will you be uploading the working version to the forums?

I understand you develop these tools in your free time, and that you have no obligations to us.

Thanks

[xenoargh]

Pretty soon, yes.

[Sarissofoi]

Pretty soon, yes.

That is nice....
Wait a moment... its human pretty soon or Alex pretty soon?

[xenoargh]

Human "pretty soon", as in, "I'm 100% sure it's working, but I'm testing some other stuff that I want to release at the same time".

[Harmful Mechanic]

Does EZ Faction still do a bunch of screwy stuff that doesn't play nice with other mods in settings, or have you fixed that in the new version.?

[xenoargh]

If you mean this stuff:

Code

"commRelayMessageSpeed":10, # light years per day, for messages going through hyperspace
"maxRelayRangeInHyperspace":100, # light years, range for a comm relay that's located in hyperspace
"commRelayRangeAroundSystem":20, # light years, range in hyperspace around an in-system relay where messages will be picked up
"maxTransponderRequiredRangeAroundMarketSystem":20, # light years

Yes.  It doesn't touch Bounties any more.  Which of those things is a serious problem, from your POV?

[Harmful Mechanic]

Really all of it, since other mods rely on vanilla settings. Is there a reason why you changed them?

(I don't think it's necessarily a bad idea to change vanilla settings, but this seems like a weird mod to do it in, and you should note in the OP that you're doing that.)

[xenoargh]

The main things were:

1.  The communication-speed (commRelayMessageSpeed) issues with Market updates (in particular, Missions / Bounties being severely out of sync, to the point that you'd get a Mission on the Intel screen, go there and discover it was long-gone).
2.  Communication range (commRelayRangeAroundSystem) being arbitarily short meant that Colonies might not get Missions at all, because they weren't "connected" to the Core.  In non-Nexerelin gameplay with just one added Faction, this is actually a real issue; the Core's the source of most Missions.

Basically, though, things break, when Markets are arbitrarily too far away from the Core, but we're still using 100% Vanilla systems under the hood.  I don't think Vanilla should have a concept of "hyperspace message speeds" or "hyperspace message ranges" in it at all; this is needless complexity in what should be a straightforward mechanic, imo.

The other two settings were more for convenience than anything else; I was originally going to allow for Hyperspace-based Factions.  I don't have that supported currently, so I'll remove them.

[Alex]

Just to clarify a couple of points:

commRelayMessageSpeed is unused.

commRelayRangeAroundSystem does not affect colonies getting missions, it's just how far the player can be from the system - while in hyperspace - and receive updates about stuff available in that system.

[xenoargh]

Ah, so all of that stuff's irrelevant now?  Cool.  I'll nuke all that and test to make sure none of the wheels fall off.

[Harmful Mechanic]

Yeah, it just struck me as weird, since I have a mod in progress with a home system well out from the core and I haven't run into any of those issues.

[xenoargh]

Sorry, gotta remember that this was started up, like, 2+ years ago and at least two major versions back, originally.  Comm Speed was still a thing and the 20LY radius meant that Colonies further-away than that simply weren't getting Intel updates, which wasn't Fun.

Anyhow, that's nuked and gone and it appears to be OK in testing thus far.