Fractal Softworks Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Starsector 0.97a is out! (02/02/24); New blog post: Codex Overhaul (05/11/24)

Pages: 1 ... 101 102 [103] 104 105 ... 402

Author Topic: [0.97a] Nexerelin v0.11.2 "Concert of Persea" (update 2024-05-18)  (Read 3096429 times)

DanielRacer

  • Ensign
  • *
  • Posts: 1
  • "You gotta be faster than that son, speed is life"
    • View Profile
Re: [0.8.1a] Nexerelin v0.8.2 "Pillage, then Burn" (update 2017-09-16)
« Reply #1530 on: September 16, 2017, 02:20:39 PM »

Hiya Histidine. Through my incredible skill of breaking things I have already found a bug involving the newest version and Interstellar Imperium. It seems that this update does not play well with Siege Fleets. After engaging and defeating a siege fleet and going into the salvage menu, pressing confirm and continue causes a crash to desktop. Here is the error:
Code
java.lang.NullPointerException
    at exerelin.campaign.events.RevengeanceManagerEvent.addFactionPoints(RevengeanceManagerEvent.java:109)
    at exerelin.campaign.events.RevengeanceManagerEvent.reportBattle(RevengeanceManagerEvent.java:277)
    at exerelin.campaign.StatsTracker.reportBattleFinished(StatsTracker.java:120)
    at com.fs.starfarer.campaign.CampaignEngine.reportBattleFinished(Unknown Source)
    at com.fs.starfarer.api.impl.campaign.FleetEncounterContext.applyAfterBattleEffectsIfThereWasABattle(FleetEncounterContext.java:739)
    at com.fs.starfarer.api.impl.campaign.FleetInteractionDialogPluginImpl$4.coreUIDismissed(FleetInteractionDialogPluginImpl.java:1317)
    at com.fs.starfarer.ui.newui.newsuper$2.coreUIDismissed(Unknown Source)
    at com.fs.starfarer.ui.newui.if.dismiss(Unknown Source)
    at com.fs.starfarer.coreui.g.actionPerformed(Unknown Source)
    at com.fs.starfarer.ui.j.super(Unknown Source)
    at com.fs.starfarer.ui.I.processInput(Unknown Source)
    at com.fs.starfarer.ui.V.o00000(Unknown Source)
    at com.fs.starfarer.BaseGameState.traverse(Unknown Source)
    at com.fs.state.AppDriver.begin(Unknown Source)
    at com.fs.starfarer.combat.CombatMain.main(Unknown Source)
    at com.fs.starfarer.StarfarerLauncher$1.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
« Last Edit: September 16, 2017, 04:36:16 PM by DanielRacer »
Logged

Histidine

  • Admiral
  • *****
  • Posts: 4726
    • View Profile
    • GitHub profile
Re: [0.8.1a] Nexerelin v0.8.2b "Pillage, then Burn" (hotfix 2017-09-17)
« Reply #1531 on: September 16, 2017, 07:34:31 PM »

The things that escape test runs...

Anyway, here is a patch that should fix it (release post updated accordingly). I'll upload the full archive once I get confirmation (or at least no negation) that the fix works EDIT: changed my mind, did it now.
« Last Edit: September 16, 2017, 07:40:31 PM by Histidine »
Logged

King Alfonzo

  • Admiral
  • *****
  • Posts: 683
  • -- D O C T O R --
    • View Profile
Re: [0.8.1a] Nexerelin v0.8.2b "Pillage, then Burn" (hotfix 2017-09-17)
« Reply #1532 on: September 16, 2017, 08:08:44 PM »

Problem Resolved.

Histidine

  • Admiral
  • *****
  • Posts: 4726
    • View Profile
    • GitHub profile
Re: [0.8.1a] Nexerelin v0.8.2c "Pillage, then Burn" (hotfix2 2017-09-17)
« Reply #1533 on: September 16, 2017, 11:04:29 PM »

*sigh*


Changelog
Code
v0.8.2c
* Fix otherwise friendly response fleets attacking player
Logged

Protonus

  • Captain
  • ****
  • Posts: 444
  • AAAAAAAAAAAA
    • View Profile
Re: [0.8.1a] Nexerelin v0.8.2c "Pillage, then Burn" (hotfix2 2017-09-17)
« Reply #1534 on: September 17, 2017, 02:46:27 AM »

Forgive me if I'm being rude. But I do believe you forgot something... Red. ;D

Edit: It's also a link.
« Last Edit: September 17, 2017, 06:40:38 AM by Protonus »
Logged

The cookies are a weird one, okay.

Mr. Nobody

  • Commander
  • ***
  • Posts: 236
    • View Profile
Re: [0.8.1a] Nexerelin v0.8.2 "Pillage, then Burn" (update 2017-09-16)
« Reply #1535 on: September 17, 2017, 05:14:49 AM »

Logged
On the left half of the Bell curve

cjuicy

  • Captain
  • ****
  • Posts: 353
  • Figuring out how the hell to wear heels (She/it)
    • View Profile
Re: [0.8.1a] Nexerelin v0.8.2 "Pillage, then Burn" (update 2017-09-16)
« Reply #1536 on: September 18, 2017, 07:43:08 AM »

Raids and stuff
Yar har fiddle dee dee
Do what you want 'cause a pirate is free!
Logged
It's been a long time, but I still love ya!

- Pfp done by Sleepyfish!

Histidine

  • Admiral
  • *****
  • Posts: 4726
    • View Profile
    • GitHub profile
Logged

Anysy

  • Commander
  • ***
  • Posts: 225
    • View Profile
Re: [0.8.1a] Nexerelin v0.8.2c "Pillage, then Burn" (hotfix2 2017-09-17)
« Reply #1538 on: September 20, 2017, 03:57:46 PM »

So I am encountering an error wiht markets being created that cannot be directly interacted with. The only factions mod I have installed is the Steelclads set, so I am basically looking to confirm it is either this or that causing the issue at hand.

https://puu.sh/xEMDi/774c4455d5.png
https://puu.sh/xEMJs/482e90cfb2.png

What I am seeing is this - A space port that shows up on maps, but is not intractable (it also does not show up in sector info, but it does generate patrol and trade fleets). I am not entirely sure how to parse this campaign file, but I am seeing lines that look something like this:
Spoiler
<CCEnt z="51058" fL="STATIONS">
<loc z="51059">2293.675|-769.24805</loc>
<vel z="51060">0.0|0.0</vel>
<j0>{"f6":10.804474,"f0":"Brand Base","f3":"orbital_station_default","f2":[255,232,232,255],"f4":"brand_base"}</j0>
<ow ref="1989"></ow>
<orbit cl="COrbtPD" z="51061" r="344.0" op="33.122406" ca="10.804474">
<e cl="CCEnt" ref="51058"></e>
<f cl="Plnt" ref="94"></f>
</orbit>
<cL cl="Sstm" ref="60"></cL>
<ls cl="Plnt" defined-in="BaseCampaignEntity" ref="68"></ls>
<me z="51062">
<d z="51063"></d>
</me>
<market cl="Market" z="51064">
<id>brand_base</id>
<name>Brand Base</name>
<commodities z="51065">
(it continues a bunch after this, I assume dictating the entire market's contents as of the save, not sure what amounts of this are useful)
[close]
Which seems to be the item at hand .. I just dont know where I would be looking in this to further diagnose this problem. It seems to be saying its of type orbital_station_default? But really beyond this I am pretty far out of my depth when it comes to modding starsector. I imagine its something dumb like that station type doesnt properly have some sort of interaction map object created, but again I am not sure where I would be looking to solve this on my own, so I am asking for help.


edit;; it looks like maybe ive missed a step in installation? lemme confirm its still an issue, I feel like this is a repeated issue not related to that however.
edit2;; Yep this should be properly installed and I am still encountering this sort of station problem. It does however possibly seem unique to RSF outposts, which lends towards it being not nexerelin's fault.
edit3;; Alright so theres some weird lines that look something like this:
Spoiler

   "stations_rsf":{
      "defaultName":"Mini Stations", # used if name=null in addCustomEntity()
      "defaultRadius":0, # used if radius<0 in addCustomEntity()
      "sheet":"graphics/stations/stations_rsf.png",
      "sheetCellSize":64,
      "renderShadow":true,
      "useLightColor":true,
      "showInCampaign":true,
      "showIconOnMap":false,
      "showNameOnMap":false,
      "interactable":false,
      "tags":["sattelites_rfs"],
      "layers":[STATIONS], # what layer(s) to render in. See CampaignEngineLayers.java for possible values
   },
[close]
Which I am not entirely sure how they are supposed to work, mostly just the interactable = false confuses me. I mention these solely because they are brought up in the RSF faction thing, under customstations it links directly to stations_rsf. I have changed that to rsf_orbital which seems to be working appropriately, which does in fact seem to be a steelclads problem. Ill bring it up there.

Sorry to uh clutter up your thread with things
« Last Edit: September 20, 2017, 04:30:54 PM by Lancefighter »
Logged

Regularity

  • Commander
  • ***
  • Posts: 104
    • View Profile
Re: [0.8.1a] Nexerelin v0.8.2c "Pillage, then Burn" (hotfix2 2017-09-17)
« Reply #1539 on: September 21, 2017, 04:46:32 PM »

I'm not that experienced in the mod, so please correct me if this is an issue from vanilla Starsector or DynaSector rather than Nexerelin.

Anyway, when traveling through nebulae, sometimes a fleet of several huge fleets spawns in a circle around your current location. However, the spawn rate seems extremely high given the number of ships and time spent in a nebulae. In one instance, after loitering around a nebula trying to salvage wrecks for a number of days, upwards of 100+ fleets had spawned and were all duking it out with one another.

This all seems a bit detrimental to good gameplay since:
- Several fleets spawn at once, meaning a battle is usually a guaranteed game over rather than any semblance of a realistic challenge
- When fleets from warring factions appear, they often engage one another. Between spawning tons of derelicts and the massive battles themselves, I can only imagine it puts a lot of stress on the game engine's stability
- These spawns don't seem to have any decent cap. Loitering in one location can spawn literally hundreds of ships.

If this isn't a bug, is there some sort of mod setting I can modify to prevent these super-fleet spawns?
Logged

Midnight Kitsune

  • Admiral
  • *****
  • Posts: 2847
  • Your Friendly Forum Friend
    • View Profile
Re: [0.8.1a] Nexerelin v0.8.2c "Pillage, then Burn" (hotfix2 2017-09-17)
« Reply #1540 on: September 21, 2017, 06:53:53 PM »

I'm not that experienced in the mod, so please correct me if this is an issue from vanilla Starsector or DynaSector rather than Nexerelin.

Anyway, when traveling through nebulae, sometimes a fleet of several huge fleets spawns in a circle around your current location. However, the spawn rate seems extremely high given the number of ships and time spent in a nebulae. In one instance, after loitering around a nebula trying to salvage wrecks for a number of days, upwards of 100+ fleets had spawned and were all duking it out with one another.

This all seems a bit detrimental to good gameplay since:
- Several fleets spawn at once, meaning a battle is usually a guaranteed game over rather than any semblance of a realistic challenge
- When fleets from warring factions appear, they often engage one another. Between spawning tons of derelicts and the massive battles themselves, I can only imagine it puts a lot of stress on the game engine's stability
- These spawns don't seem to have any decent cap. Loitering in one location can spawn literally hundreds of ships.

If this isn't a bug, is there some sort of mod setting I can modify to prevent these super-fleet spawns?
Sounds like you are using the Thar Be Dragons mod from Xenoargh. I (and many others) would suggest that you avoid his mods due to how they don't interact well with other mods and or are buggy.
Logged
Help out MesoTroniK, a modder in need

2021 is 2020 won
2022 is 2020 too

Regularity

  • Commander
  • ***
  • Posts: 104
    • View Profile
Re: [0.8.1a] Nexerelin v0.8.2c "Pillage, then Burn" (hotfix2 2017-09-17)
« Reply #1541 on: September 21, 2017, 07:48:47 PM »

Sounds like you are using the Thar Be Dragons mod from Xenoargh. I (and many others) would suggest that you avoid his mods due to how they don't interact well with other mods and or are buggy.

Ooooh, so that's what it was. I do indeed have it installed. Thanks for the help.
Logged

dk1332

  • Commander
  • ***
  • Posts: 197
    • View Profile
Re: [0.8.1a] Nexerelin v0.8.2c "Pillage, then Burn" (hotfix2 2017-09-17)
« Reply #1542 on: September 22, 2017, 03:07:23 AM »

Hate to be that guy, but I got this on the latest patch of Nex

Code
897821 [Thread-4] ERROR com.fs.starfarer.combat.CombatMain  - java.lang.NullPointerException
java.lang.NullPointerException
at com.fs.starfarer.campaign.events.EventProbability.<init>(Unknown Source)
at com.fs.starfarer.campaign.events.CampaignEventManager.getProbability(Unknown Source)
at com.fs.starfarer.campaign.events.CampaignEventManager.startEvent(Unknown Source)
at exerelin.campaign.events.RevengeanceManagerEvent.advanceVengeanceStage(RevengeanceManagerEvent.java:187)
at exerelin.campaign.events.RevengeanceManagerEvent.tryActivateFactionVengeance(RevengeanceManagerEvent.java:145)
at exerelin.campaign.events.RevengeanceManagerEvent.addFactionPoints(RevengeanceManagerEvent.java:126)
at exerelin.campaign.events.RevengeanceManagerEvent.reportBattle(RevengeanceManagerEvent.java:285)
at exerelin.campaign.StatsTracker.reportBattleFinished(StatsTracker.java:120)
at com.fs.starfarer.campaign.CampaignEngine.reportBattleFinished(Unknown Source)
at com.fs.starfarer.api.impl.campaign.FleetEncounterContext.applyAfterBattleEffectsIfThereWasABattle(FleetEncounterContext.java:739)
at com.fs.starfarer.api.impl.campaign.FleetInteractionDialogPluginImpl$4.coreUIDismissed(FleetInteractionDialogPluginImpl.java:1317)
at com.fs.starfarer.ui.newui.newsuper$2.coreUIDismissed(Unknown Source)
at com.fs.starfarer.ui.newui.if.dismiss(Unknown Source)
at com.fs.starfarer.coreui.g.actionPerformed(Unknown Source)
at com.fs.starfarer.ui.j.super(Unknown Source)
at com.fs.starfarer.ui.I.processInput(Unknown Source)
at com.fs.starfarer.ui.V.o00000(Unknown Source)
at com.fs.starfarer.BaseGameState.traverse(Unknown Source)
at com.fs.state.AppDriver.begin(Unknown Source)
at com.fs.starfarer.combat.CombatMain.main(Unknown Source)
at com.fs.starfarer.StarfarerLauncher$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

I think its due to the patch and not the whole one. If so then you can just ignore this while I go and dl the actual 0.8.2c rather than the patch.
Logged

Histidine

  • Admiral
  • *****
  • Posts: 4726
    • View Profile
    • GitHub profile
Re: [0.8.1a] Nexerelin v0.8.2d "Pillage, then Burn" (update 2017-09-30)
« Reply #1543 on: September 30, 2017, 01:18:24 AM »

More fixes and improvements.

Nexerelin v0.8.2d
Download

Changelog
Code
v0.8.2d
* Planetbreaker improvements
    * Use new dialog battle system as well
    * Makes orphans
    * Reputation penalty scales up more with market size
* Invasion/raid tweaks:
    * After in-dialog battle against response fleet, escaped enemies don't replenish respawn fleet pool
    * Config setting for invasion/raid loot mult
    * Raid strength multiplier for loot floored at 0.25
    * Improve raid prediction display
* Add carrier starts
* Diktat only uses Lion's Guard response fleets on HQ markets
* Vengeance fleets go home if they take too many losses
* Mining accident chance 0.4 -> 0.32
* Fixes:
    * Auto-cleanup scavenger fleets Sector-wide when docking at a market
    * Fix in-dialog response/defense fleets not using DynaSector
    * Fix not being able to exit dialog after invasion/raid when no loot exists
    * Fix pirate starting frigate variant
Logged

Ahne

  • Captain
  • ****
  • Posts: 321
    • View Profile
Re: [0.8.1a] Nexerelin v0.8.2d "Pillage, then Burn" (update 2017-09-30)
« Reply #1544 on: September 30, 2017, 08:10:56 AM »

Great, will try it out soon.
Logged
Pages: 1 ... 101 102 [103] 104 105 ... 402