dork-galaxies/fixesPUBLIC LOG

THE GALAXY, GETTING BETTER

Fixes & restorations.

What we have repaired, reconnected and brought back to the galaxy.

Deployment records reviewed
live galaxyFIXES.log42 entries

Applied changes

Showing all 42 entries

Listed changes are deployed. Restored quest and pilot routes have passed automated checks; full player walkthroughs are still ongoing. Each entry has a What to test guide.

  1. A cleaner handoff during planned restartsPlanned shutdowns now notify character sessions before the final disconnect and save. DG-FIX-001/Player walkthroughs ongoing

    What changed

    The shutdown sequence now sends the normal logout message, gives sessions a bounded chance to detach, and completes logout recovery before the final save. The change is active; the on-screen handoff still needs a player check at a normal planned restart.

    What to test

    1. At the next announced restart, leave a test character online if convenient. No extra restart is needed.
    2. Check whether the client returns to character selection before downtime, then sign back in after the server returns.
    3. Check your last position and recent inventory changes. Report the time and any unexpected disconnect screen.
    Report a problemInclude DG-FIX-001 in your report.
  2. Travel vouchers work when credits are lowEligible vouchers are found throughout your inventory, including its final slot. DG-FIX-002/Player walkthroughs ongoing

    What changed

    Travel terminals now check every inventory entry for a valid voucher before requiring paid-ticket funds. A successful voucher purchase gives the ticket before consuming the voucher; cancellation preserves it.

    What to test

    1. With a valid voucher and less money than the fare, choose an eligible one-way trip and select Use Voucher.
    2. Confirm you receive one correct ticket, the voucher is consumed once, and credits are not charged.
    3. On a separate voucher purchase, select Cancel and confirm the voucher remains. Keep any route restrictions in mind.
    Report a problemInclude DG-FIX-002 in your report.
  3. Galactic Supply buying allowance resets with the galaxyA normal game-server restart begins a fresh buying allowance without erasing purchase history. DG-FIX-003/Player walkthroughs ongoing

    What changed

    Account and galaxy buying counters now follow the game restart period. Restarting the buying worker alone does not reset them. The configured limits are 100,000 credits or 2,000 purchases per account, and 500,000 credits across the galaxy per period.

    What to test

    1. After a normal server restart, list an eligible item you crafted at or below its buying ceiling.
    2. Allow the buying service time to process it, then check your Bazaar sale and payment.
    3. If buying appears stuck, report the item, city, asking price and approximate listing time. Eligibility and remaining budgets still apply.
    Report a problemInclude DG-FIX-003 in your report.
  4. Missing survey-device buying ordersGalactic Supply now recognizes the expanded survey-device and personal-extractor catalog. DG-FIX-004/Player walkthroughs ongoing

    What changed

    The buying catalog now covers all configured survey-device types and five personal extractor types. Craftable survey devices have a 1,500-credit buying ceiling; personal extractors have a 20,000-credit ceiling. The bot pays an eligible listing's asking price, up to that ceiling.

    What to test

    1. List a supported survey device or personal extractor that records you as its crafter.
    2. Keep the asking price within its type ceiling and allow the service time to review the listing.
    3. If it remains unsold, report the exact item name, price, Bazaar city and listing time. A catalog entry does not override account or galaxy budgets.
    Report a problemInclude DG-FIX-004 in your report.
  5. 4K resolution can be selected in the launcherThe display picker includes 3840 × 2160 even when the old setup program leaves it out. DG-FIX-005/Deployed correction

    What changed

    Launcher display settings now offer 4K UHD and common resolutions, with fullscreen, windowed and borderless choices. Fullscreen choices are checked against the primary display's supported modes. This changes the display resolution; it does not add whole-interface scaling.

    What to test

    1. Close the game and its setup program, then open Graphics > Display settings in the latest launcher.
    2. On a supported 4K display, choose 3840 × 2160, apply, and launch the game.
    3. Check that the selected mode takes effect. If a mode fails, report the display, Windows scale, selected mode and launcher version.
    Report a problemInclude DG-FIX-005 in your report.
  6. Password resets no longer fail at the last stepSubmitting a valid new password no longer produces the account-services-unavailable error we traced. DG-FIX-006/Deployed correction

    What changed

    The password-reset and password-change operations were corrected so they can complete the required session cleanup. Single-use reset links and session revocation remain in place.

    What to test

    1. Request a new reset link for your verified email and use the newest message.
    2. Set a new password and confirm the page reports Password updated.
    3. Sign in with the new password. If an error returns, report its wording and time, without sharing your password or reset link.
    Report a problemInclude DG-FIX-006 in your report.
  7. Destroy missions stay close to their offered locationMission arrivals keep the familiar transmission update without sending you kilometres across the map. DG-FIX-007/Deployed correction

    What changed

    The terminal validates the last-known search location before offering the mission. On arrival, the server searches nearby for a safe lair position and updates the waypoint after the lair spawns. Beginner neutral destroy missions also use shorter offer ranges near city exits.

    What to test

    1. Take a fresh beginner destroy mission and note its offered location.
    2. Approach the marker and check that the transmission moves the waypoint only a short local distance.
    3. Complete the objective and confirm the normal reward. Include the planet, city and before/after coordinates if the waypoint jumps far away.
    Report a problemInclude DG-FIX-007 in your report.
  8. Two destroy missions can resolve nearbyArriving at one objective no longer requires its original marker to remain an exact clear spawn point. DG-FIX-008/Deployed correction

    What changed

    The paired-mission regression was corrected. Nearby arrival searches account for lairs already spawned by another mission and find a safe local alternative, instead of deleting a mission just because its single offered coordinate became blocked.

    What to test

    1. Accept two fresh destroy missions from a terminal.
    2. Approach and complete them one at a time, checking that each can update its location and spawn its own objective.
    3. Report a mission that vanishes or becomes unavailable, including the order you approached them and their approximate locations.
    Report a problemInclude DG-FIX-008 in your report.
  9. Starter wildlife is easier to find near citiesPlanet-appropriate starter groups are placed near the mapped edges of 22 starting cities. DG-FIX-009/Player walkthroughs ongoing

    What changed

    The starter-wildlife placement supplies nearby creatures for early training. The current selection includes ordinary passive level-9/10 planetary wildlife in two groups per city, alongside the existing lower-level groups. These use normal creature rewards and harvesting.

    What to test

    1. Walk outside a starting city on Tatooine, Naboo, Corellia, Talus or Rori and explore around its edge.
    2. Look for nearby low-level planetary wildlife, then check combat, XP and harvesting on an appropriate character.
    3. If an area seems empty after allowing time for respawns, report the city and coordinates.
    Report a problemInclude DG-FIX-009 in your report.
  10. City safety no longer suppresses too much wildernessThe overly broad passive-only city belt was replaced with mapped city-boundary checks. DG-FIX-010/Player walkthroughs ongoing

    What changed

    Ambient spawn origins and group footprints are checked against actual city boundaries. Outside those boundaries, the original wilderness pools can again choose their normal creatures. This protects spawn placement; creatures can still move or be drawn toward a city.

    What to test

    1. Explore beyond a mapped city edge and compare nearby starter wildlife with the normal wilderness farther out.
    2. Watch for groups originating inside the city or large areas where normal ambient creatures never return.
    3. Report coordinates and creature names if placement looks wrong. Quest, mission and event spawns use separate rules.
    Report a problemInclude DG-FIX-010 in your report.
  11. Nym's final reward survives a full inventoryA full inventory no longer discards the pending final reward before you can retry. DG-FIX-011/Player walkthroughs ongoing

    What changed

    The final hand-in preserves the reward state when there is no room. After freeing space, you can return and claim the pending reward rather than losing it to the failed delivery.

    What to test

    1. If you reach the final hand-in with a full inventory, check that the quest asks you to make room.
    2. Free a suitable slot and return to the same contact without deleting quest items or resetting the chain.
    3. Confirm the reward is delivered once and the quest finishes correctly.
    Report a problemInclude DG-FIX-011 in your report.
  12. Crimson Phoenix pilot campaignA formerly placeholder campaign now has connected progression through Master Pilot. DG-FIX-012/Player walkthroughs ongoing

    What changed

    The campaign's mission chain, training gates, repeatable duties and rewards have been implemented and deployed. Automated checks passed; full player flights through the campaign are still being checked.

    What to test

    1. Speak with your current squadron trainer when eligible and accept the next assignment.
    2. Fly the mission, follow journal updates, complete its objectives and return for the hand-in.
    3. Check that the reward, training and next mission unlock correctly. Report the trainer, mission title and last completed objective if progression stops.
    Report a problemInclude DG-FIX-012 in your report.
  13. Vortex pilot campaignA formerly placeholder campaign now has connected progression through Master Pilot. DG-FIX-013/Player walkthroughs ongoing

    What changed

    The campaign's mission chain, training gates, repeatable duties and rewards have been implemented and deployed. Automated checks passed; full player flights through the campaign are still being checked.

    What to test

    1. Speak with your current squadron trainer when eligible and accept the next assignment.
    2. Fly the mission, follow journal updates, complete its objectives and return for the hand-in.
    3. Check that the reward, training and next mission unlock correctly. Report the trainer, mission title and last completed objective if progression stops.
    Report a problemInclude DG-FIX-013 in your report.
  14. Black Epsilon pilot campaignA formerly placeholder campaign now has connected progression through Master Pilot. DG-FIX-014/Player walkthroughs ongoing

    What changed

    The campaign's mission chain, training gates, repeatable duties and rewards have been implemented and deployed. Automated checks passed; full player flights through the campaign are still being checked.

    What to test

    1. Speak with your current squadron trainer when eligible and accept the next assignment.
    2. Fly the mission, follow journal updates, complete its objectives and return for the hand-in.
    3. Check that the reward, training and next mission unlock correctly. Report the trainer, mission title and last completed objective if progression stops.
    Report a problemInclude DG-FIX-014 in your report.
  15. Imperial Inquisition pilot campaignA formerly placeholder campaign now has connected progression through Master Pilot. DG-FIX-015/Player walkthroughs ongoing

    What changed

    The campaign's mission chain, training gates, repeatable duties and rewards have been implemented and deployed. Automated checks passed; full player flights through the campaign are still being checked.

    What to test

    1. Speak with your current squadron trainer when eligible and accept the next assignment.
    2. Fly the mission, follow journal updates, complete its objectives and return for the hand-in.
    3. Check that the reward, training and next mission unlock correctly. Report the trainer, mission title and last completed objective if progression stops.
    Report a problemInclude DG-FIX-015 in your report.
  16. Storm pilot campaignA formerly placeholder campaign now has connected progression through Master Pilot. DG-FIX-016/Player walkthroughs ongoing

    What changed

    The campaign's mission chain, training gates, repeatable duties and rewards have been implemented and deployed. Automated checks passed; full player flights through the campaign are still being checked.

    What to test

    1. Speak with your current squadron trainer when eligible and accept the next assignment.
    2. Fly the mission, follow journal updates, complete its objectives and return for the hand-in.
    3. Check that the reward, training and next mission unlock correctly. Report the trainer, mission title and last completed objective if progression stops.
    Report a problemInclude DG-FIX-016 in your report.
  17. Smuggler Alliance pilot campaignThe missing progression after the existing Dravis starter content is connected. DG-FIX-017/Player walkthroughs ongoing

    What changed

    The Smuggler restoration connects 47 remaining journal stages and ten repeatable contracts, retaining the earlier Dravis missions. The route now has implemented progression through Master Pilot.

    What to test

    1. Continue from your current Smuggler Alliance trainer and take the next eligible assignment.
    2. Check mission travel, objective updates, recovery after interruptions and the return conversation.
    3. Confirm that the correct training and next contact become available. Report a broken handoff before changing squadrons.
    Report a problemInclude DG-FIX-017 in your report.
  18. CorSec Admiral handoffsMissing later Admiral choices now connect to the appropriate CorSec assignments. DG-FIX-018/Player walkthroughs ongoing

    What changed

    The later CorSec conversation and mission handoffs have been connected, including the mutually exclusive Admiral choices. Earlier working chapters are retained.

    What to test

    1. Continue your current CorSec route until an Admiral handoff is offered.
    2. Check that the branch you choose gives the correct assignment and journal updates.
    3. Finish the mission and check the next trainer conversation. Do not resign to troubleshoot a missing dialogue option.
    Report a problemInclude DG-FIX-018 in your report.
  19. Royal Security Forces later chaptersMissing later missions and trainer connections have been restored. DG-FIX-019/Player walkthroughs ongoing

    What changed

    The later campaign chapters now connect to the earlier working progression, with the remaining mission and training handoffs implemented through Master Pilot.

    What to test

    1. Continue from your current trainer with the appropriate pilot skills and completed prerequisites.
    2. Check each later assignment's objectives, journal transitions and return conversation.
    3. Confirm progression continues after the hand-in. Include your current skill boxes, trainer and mission title in any report.
    Report a problemInclude DG-FIX-019 in your report.
  20. Havoc Squadron later chaptersMissing later missions and trainer connections have been restored. DG-FIX-020/Player walkthroughs ongoing

    What changed

    The later campaign chapters now connect to the earlier working progression, with the remaining mission and training handoffs implemented through Master Pilot.

    What to test

    1. Continue from your current trainer with the appropriate pilot skills and completed prerequisites.
    2. Check each later assignment's objectives, journal transitions and return conversation.
    3. Confirm progression continues after the hand-in. Include your current skill boxes, trainer and mission title in any report.
    Report a problemInclude DG-FIX-020 in your report.
  21. Dravis starter progressionMissing Smuggler starter mission connections and journal steps have been repaired. DG-FIX-021/Player walkthroughs ongoing

    What changed

    Starter conversations and objectives now connect to the intended early progression instead of stopping at missing handoffs.

    What to test

    1. On an eligible Smuggler starter character, take the assignment offered by Dravis.
    2. Follow each mission objective and check that the journal updates at the right time.
    3. Return for the hand-in and confirm the next assignment or training option becomes available.
    Report a problemInclude DG-FIX-021 in your report.
  22. Darn Droid II transport missionThe missing transport and success handoff are connected to the quest. DG-FIX-022/Player walkthroughs ongoing

    What changed

    The ground conversations and space mission now share the transport and completion bridge needed to continue Darn Droid II.

    What to test

    1. Reach the appropriate Darn Droid II step through its normal contacts.
    2. Launch, complete the assigned transport objective, and watch for the journal update.
    3. Return to the quest contact and confirm the success conversation advances the chain.
    Report a problemInclude DG-FIX-022 in your report.
  23. Recovery-duty conversations and objectivesRikkh and Kaydine recovery-duty entry points now start their intended assignments. DG-FIX-023/Player walkthroughs ongoing

    What changed

    Missing conversation links and recovery-duty entry points have been restored. Follow-up range corrections align recovery objectives with their intended mission flow.

    What to test

    1. Use an eligible character to request the recovery duty from the appropriate contact.
    2. Approach the recovery objective and check that the action is available at a sensible nearby range.
    3. Complete and return for the duty reward. Report the contact, mission and distance if an interaction never becomes available.
    Report a problemInclude DG-FIX-023 in your report.
  24. Dathomir station repair storyThe quest-gated station repair sequence is connected to its objectives and contacts. DG-FIX-024/Player walkthroughs ongoing

    What changed

    The station story's mission progression and gated repair interactions have been restored around the documented objectives and existing assets.

    What to test

    1. Reach the repair assignment through the normal Dathomir station story.
    2. Check the required station interactions and journal updates as you complete the objectives.
    3. Return to the contact and check the hand-in and next conversation. Report a missing action with the mission stage.
    Report a problemInclude DG-FIX-024 in your report.
  25. Station payments include bank creditsStation affordability checks and payment now agree when funds are split between cash and bank. DG-FIX-025/Player walkthroughs ongoing

    What changed

    The station payment flow now checks and charges available cash plus bank funds consistently instead of rejecting a purchase that the combined balance can cover.

    What to test

    1. With enough combined cash and bank funds for an eligible station service, open its normal conversation.
    2. Confirm the service is offered and that the total charge matches its displayed price.
    3. Check both balances afterward and report an incorrect refusal or charge with the service name.
    Report a problemInclude DG-FIX-025 in your report.
  26. Naboo station and Emperor's Retreat access storyA missing station story now connects six journal stages and the access handoff. DG-FIX-026/Player walkthroughs ongoing

    What changed

    The optional Naboo station story has been reconstructed using recorded objectives and existing assets, with the station conversations and Emperor's Retreat access progression connected.

    What to test

    1. Start the story through its normal Naboo station contact when eligible.
    2. Follow the journal through the mission objectives and return conversations.
    3. Check that the final handoff grants the intended access. Include the journal title and last completed step in a report.
    Report a problemInclude DG-FIX-026 in your report.
  27. Seven missing NPC quest chainsArrek Von Sarko, Athok Dinvar, Bab Esrus, Brass Marshoo, Lob Dizz, Palo and Radanthus Mandelatara now have connected quests. DG-FIX-027/Player walkthroughs ongoing

    What changed

    Seven previously empty quest chains now contain 22 stage records. Missing encounters and dialogue were reconstructed around the recorded objectives and available game assets.

    What to test

    1. Speak with one of the listed NPCs on an eligible character and accept the offered task.
    2. Follow the mission objectives, then return to the contact and check the next conversation.
    3. Check rewards and continuation through the chain. Report the NPC name, mission title and the exact step that stops.
    Report a problemInclude DG-FIX-027 in your report.
  28. Rep Been's later missionsDisabled later quest stages have been reconnected to the existing chain. DG-FIX-028/Player walkthroughs ongoing

    What changed

    Later mission records and conversation handoffs now continue the earlier tasks instead of leaving the chain at a disabled stage. Five later stages were restored across these two NPCs.

    What to test

    1. Continue the existing chain with Rep Been until a later mission is offered.
    2. Complete its objective and check that the return conversation recognizes your progress.
    3. Confirm the next stage or final reward becomes available. Report your last successful mission if the chain stops.
    Report a problemInclude DG-FIX-028 in your report.
  29. Rovim Minnoni's later missionsDisabled later quest stages have been reconnected to the existing chain. DG-FIX-029/Player walkthroughs ongoing

    What changed

    Later mission records and conversation handoffs now continue the earlier tasks instead of leaving the chain at a disabled stage. Five later stages were restored across these two NPCs.

    What to test

    1. Continue the existing chain with Rovim Minnoni until a later mission is offered.
    2. Complete its objective and check that the return conversation recognizes your progress.
    3. Confirm the next stage or final reward becomes available. Report your last successful mission if the chain stops.
    Report a problemInclude DG-FIX-029 in your report.
  30. Vordin Sildor's missions can startThe quest registration now points to the existing mission chain correctly. DG-FIX-030/Player walkthroughs ongoing

    What changed

    A registration error that prevented Vordin Sildor's existing missions from spawning was corrected.

    What to test

    1. Speak with Vordin Sildor on a character eligible for the chain.
    2. Accept the mission and check that its target and waypoint appear.
    3. Complete the objective and return for the next conversation or reward.
    Report a problemInclude DG-FIX-030 in your report.
  31. Broken quest conversations and record-keeper linksMissing conversation connections have been repaired for COA contacts and quest record keepers. DG-FIX-031/Player walkthroughs ongoing

    What changed

    Affected conversations now connect to their intended briefings, recovery options and quest progression instead of ending at missing links.

    What to test

    1. Use the relevant quest contact at your current story stage and check the available conversation choices.
    2. For a record keeper, read the offered options before making a progression or replay choice.
    3. Report an empty response or missing handoff with the NPC, conversation option and current quest stage.
    Report a problemInclude DG-FIX-031 in your report.
  32. Tutorial interactions and guidanceMissing tutorial interactions and progression guidance have been connected. DG-FIX-032/Player walkthroughs ongoing

    What changed

    The affected tutorial steps now provide their intended interactions and guidance so new characters can continue through the sequence.

    What to test

    1. With a new tutorial character, follow the normal prompts and speak to each contact in order.
    2. Check the interaction objects, objective updates and directions to the next step.
    3. Report a blocked step with the tutorial contact or object name and the last prompt you received.
    Report a problemInclude DG-FIX-032 in your report.
  33. Gungan temple skirmishThe missing temple activity has been restored as a bounded encounter. DG-FIX-033/Player walkthroughs ongoing

    What changed

    The temple encounter now has its configured participants and progression, with bounded spawning rather than an uncontrolled population loop.

    What to test

    1. Visit the temple encounter through normal exploration or quest progression.
    2. Check whether participants appear, the encounter progresses, and defeated groups clear correctly.
    3. Report empty encounters, repeated stuck waves or unexpected population growth with the location and time.
    Report a problemInclude DG-FIX-033 in your report.
  34. Corvette NPC room placementAffected Corvette NPCs now use corrected room and interior placement. DG-FIX-034/Player walkthroughs ongoing

    What changed

    The encounter placement was adjusted so configured NPCs appear in the intended interior rooms instead of inappropriate or inaccessible positions.

    What to test

    1. During a normal Corvette run, check NPC placement as you move between rooms.
    2. Watch for targets inside walls, outside the playable interior, or unreachable despite being in the same room.
    3. Report the room, NPC name and approximate location, with a screenshot if possible.
    Report a problemInclude DG-FIX-034 in your report.
  35. Three missing Lok population entriesThree historically supported population omissions have been restored. DG-FIX-035/Player walkthroughs ongoing

    What changed

    The confirmed missing Lok population entries were reintroduced using the supporting historical and client records. This is a specific restoration, rather than a claim that every planetary spawn has been audited.

    What to test

    1. Explore Lok and check the restored encounters during normal travel and questing.
    2. Watch for missing groups, duplicate populations or creatures in blocked terrain.
    3. Report the creature or NPC name and exact coordinates so we can check the affected population entry.
    Report a problemInclude DG-FIX-035 in your report.
  36. Safer ship launch and redeed requestsInvalid ship references are rejected cleanly, and launch requests respect the JTL enable setting. DG-FIX-036/Deployed correction

    What changed

    Launch and redeed requests now return safely when their control device has no valid ship. The existing JTL enable setting is also checked in the launch path. These protections adapt publicly shared SWG Infinity fixes to our server base.

    What to test

    1. Launch and land with a valid ship using your normal control device.
    2. Check the normal ship-management and redeed flow when you actually need it.
    3. Report a failed valid operation with the ship type and action. There is no need to create or seek out broken devices.
    Report a problemInclude DG-FIX-036 in your report.
  37. Server dialog responses stay alignedThe server now reads its dialog command type using the same field size it writes. DG-FIX-037/Deployed correction

    What changed

    The SUI message reader and writer now agree on the one-byte command type, avoiding incorrect interpretation of following dialog data. This correction adapts publicly shared SWG Infinity work.

    What to test

    1. Use ordinary server dialogs with buttons, choices or input fields during normal play.
    2. Confirm the selected option reaches the expected action and any entered text is handled correctly.
    3. Report the dialog title, selected button and unexpected result if a response is misread.
    Report a problemInclude DG-FIX-037 in your report.
  38. Fishing cleanup and catch validationFishing stops cleanly on logout or link loss, and invalid catch data is rejected safely. DG-FIX-038/Deployed correction

    What changed

    Fishing sessions now clean up their observers when a character logs out or goes link-dead. Catch rewards are checked for valid species and required length data. These protections adapt publicly shared SWG Infinity fixes.

    What to test

    1. Fish normally and confirm valid catches, lengths and rewards appear as expected.
    2. Log out normally after fishing and check that the session is cleared when you return.
    3. If a normal connection loss occurs, report any stuck fishing action after reconnecting. Do not deliberately disrupt your network.
    Report a problemInclude DG-FIX-038 in your report.
  39. Fishing density follows the bobberThe density check uses the cast location instead of where your character is standing. DG-FIX-039/Player walkthroughs ongoing

    What changed

    Fishing density now evaluates the bobber position. The expression was reviewed and compiled; catch randomness means a small sample cannot prove the underlying density calculation. This correction adapts publicly shared SWG Infinity work.

    What to test

    1. Fish from normal shoreline positions with casts into different nearby areas.
    2. Check that the activity and catch feedback remain consistent with the place you cast.
    3. Report repeatable location problems with both your standing position and approximate bobber location.
    Report a problemInclude DG-FIX-039 in your report.
  40. Lair spawn limits handle small or empty groups safelyEmpty mobile lists and small spawn limits no longer reach the unsafe spawn calculations we identified. DG-FIX-040/Deployed correction

    What changed

    Lair handling now checks empty mobile lists and guards the low-limit calculation. Private-world tests exercised the affected spawn waves. These protections adapt publicly shared SWG Infinity fixes.

    What to test

    1. Fight normal wilderness or destroy-mission lairs and check that their defenders spawn and replenish normally.
    2. Complete the encounter and check that it can finish without becoming stuck.
    3. Report a lair with no usable defenders, repeated unexpected waves or a stalled objective, including its name and location.
    Report a problemInclude DG-FIX-040 in your report.
  41. Jedi trial lookups fail safelyFour affected Jedi Knight trial paths now guard against missing quest definitions. DG-FIX-041/Deployed correction

    What changed

    The trial handlers now check the quest definitions before using them. Missing data no longer reaches the unsafe lookup path, while the normal progression paths remain intact. These protections adapt publicly shared SWG Infinity fixes.

    What to test

    1. Continue your current Jedi trial through its normal shrine and objectives.
    2. Check journal updates, the completion conversation and the next trial handoff.
    3. If progress stops, report the trial and last completed step. Keep your current skills and quest state while staff investigate.
    Report a problemInclude DG-FIX-041 in your report.
  42. Delayed crafting work handles missing tools safelyCrafting callbacks return safely if their crafter or tool is no longer available. DG-FIX-042/Player walkthroughs ongoing

    What changed

    The delayed crafting path now checks its references before continuing. The guard was reviewed and compiled; a synthetic corrupt-crafting runtime test is not claimed. This protection adapts publicly shared SWG Infinity work.

    What to test

    1. Complete a normal crafting session with an appropriate tool.
    2. Check that assembly, experimentation where available, and final item creation still complete normally.
    3. Report a stuck crafting session with the schematic, tool and last successful step. Do not destroy tools or interrupt sessions to provoke a failure.
    Report a problemInclude DG-FIX-042 in your report.

This archive covers our documented repairs and restorations. Some missing encounters and dialogue were reconstructed using recorded objectives and existing assets. Entry counts are log records, not a count of complete quests.

Built on SWGEmu/Core3. The core reliability corrections identified in their entries adapt publicly shared SWG Infinity work, with thanks to the wider SWG community.

Found something that still needs attention? Send us a bug report with the entry reference, your character's quest stage and what happened. Keep passwords and account-recovery links private.