Discovery Gaming Community
[Coding] Autobuy then docking on Fort Leniex does not restock munitions etc. - Printable Version

+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Discovery Development (https://discoverygc.com/forums/forumdisplay.php?fid=7)
+--- Forum: Discovery Mod General Discussion (https://discoverygc.com/forums/forumdisplay.php?fid=37)
+---- Forum: Discovery Mod Bug Reports (https://discoverygc.com/forums/forumdisplay.php?fid=573)
+----- Forum: Fixed or invalid (https://discoverygc.com/forums/forumdisplay.php?fid=574)
+----- Thread: [Coding] Autobuy then docking on Fort Leniex does not restock munitions etc. (/showthread.php?tid=210332)



[Coding] Autobuy then docking on Fort Leniex does not restock munitions etc. - Eternal.Journey - 12-18-2025

Type: Server Config
Bug: Leniex does not respond to autobuy all on, only repairs your ship. Yet, you can still buy the munitions, regens etc from the equipment vendor.

Reproduction Steps:
  • Step 1 /autobuy all on
  • Step 2 dock on Fort Leniex
  • Step 3 Realise only your ship has been repaired, but nothing has been resupplied. Buy munitions and regens manually anyway because they have them in stock.



RE: [Coding] Autobuy then docking on Fort Leniex does not restock munitions etc. - Alex. - 12-23-2025

Fort Leniex vs. Leniex Outpost -> this is sounding *very* similar to https://discoverygc.com/forums/showthread.php?tid=180040


RE: [Coding] Autobuy then docking on Fort Leniex does not restock munitions etc. - Alex. - 12-23-2025

@Aingar has fixed an underlying FLHook core/autobuy bug here relating to trusting the game's Universe::IBase->lSpaceObjID field, which we were using (in core) to populate iObjectID, which was then left as 0 (specifically for these bases with mismatching base vs. solar names - because strid_name infocard on [Base] in universe.ini matching to [Object]'s ids_name is what decides what solarId goes into the Universe::IBase->spaceObjID field) and passed to pub::SpaceObj::GetSolarRep by autobuy.
It should be fixed from next restart.