Skip to main content

Browse GamesGame JamsUpload GameDeveloper LogsCommunity
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
ChezJfrey5 years ago(+1)

Ugh!  You are correct about the HUD problem.  The real story is that my recent change to remove all the "home-rolled" array allocations in the game (because the code they wrote themselves to do it was prone to memory violations and other problems, which can cause crashes) and I finally removed ALL of them, throughout the entire engine, well, it looks like I inadvertently caused some problems with the standard library for some of these...and the HUD messages were apparently a little trickier to replace.  Just yesterday someone pointed out that some of the boarding log messages were missing, which got fixed, but now this other piece you bring up that is also related to the same log message problem...anyway, that ammo is fixed now and I just updated.

Thanks for pointing it out.

I will take a look at this looting issue you describe and see what I can do if it is re-sorting after a selection...is that what you're describing?  Pick one to take, then the list re-sorts unexpectedly when you intend to take the next item?

Reply
Husky19935 years ago (1 edit)

That is exactly the problem, only better explained. I pick something up and the list sort of shuffles again. Thanks for reacting so quickly. :)

Reply
ChezJfrey5 years ago(+1)

OK, I see it now.  I suppose I just became accustomed to the default COAS behavior and needed to pay attention.  I also figure the reason for the current behavior was for speed/efficiency as what they are doing is swapping the current item slot you just took from with the last item so that no shifting of items needs to take place.  Shifting everything one slot, or sorting takes a little longer.  But truth be told, we're talking so few items that I don't see a problem with shifting them.  I put this on my list to do and it probably won't take that long to put this in the next ERAS update.  I am not sure I will do it for COAS or GOF, but for sure will do so for ERAS.

Reply
Husky19935 years ago

Well, as long as it is on your radar, I think its ok. No game breaker or something, just midly annoying. Thanks. :)

Reply
ChezJfrey5 years ago(+1)

Upon investigation, it turns out I was mistaken about that behavior was "always" that way.  No, I accidentally introduced it for precisely the efficiency I mentioned, not the original devs.  During an "attribute" deletion, I added the "swap with last element, then delete" behavior because it was quicker and there can be many attributes and deletions where a good deal of benefit could be obtained by changing the "shift every element after a deletion" instead with my "swap deleted element with last and delete the last."  This had the unintended side-effect during the loot screen because it deletes the item as an "attribute" so then it swaps with the last.  I added a feature in the engine to preserve the order in any special cases we desire to preserve order and added that special case to the loot screen; most of the time, we don't care the order of the attributes, so I wanted my efficiency change to remain in effect in all other cases right now.

Update Maelstrom first, then update ERAS, COAS, or any GOF version; I made the fix for all of them since this was actually contrary to original behavior, since it was my engine change that caused the problem, it made sense to fix them all.

Reply
Husky19935 years ago

I will, thanks!

Reply
AboutFAQBlogContact us
Copyright © 2026 itch corp · Directory · Terms · Privacy · Cookies