An auto-save feature would be fantastic.  Especially coming from the paradigm of MMORPG to single player.  I lost a few hours of work from a crash, which was frustrating, but I did find the save button, so I know better now.  

I will likely remove patents entirely.

Can anyone make a case for keeping them?

After exiting the design studio in Hazeron Starship, processes seem to stop running or rather they never finish, they stay indefinately at 0:00 seconds, even removing the process and readding it doesn't change it.

After saving and then exiting and restaring the game, it works fine again, meaning I have to exit the game every time when I enter the designer. Perhaps it would be nice to be able to load designs into the game through the menu and be able to return to the menu at any time aswell.

Edit: It seems to happen when I leave the atmosphere and then re-enter, aswell. I can talk to citzens and move and drive/fly around, but processes seem stuck. Maybe the game is stuck when trying to load those after re-entering the planetside scene?

Edit 3: it also happens when switching characters (between different systems)

Edit 2: After destroying the buildings and the constructing new ones it works again without restarting the game, if that helps.

A new Hazeron Starship beta has finally been posted to Steam. New keys were sent by email to everyone who requested them.

Here are some noteworthy changes.

World build limits were raised a lot.

Spacecraft and building design size limits were raised.

Diplomacy window now updates properly when you make changes.

Sentient species on habitable worlds was changed. It used to be that almost every habitable world you visited had a sentient species that exactly matched your own. About 5% of worlds got a different sentient species. All habitable worlds had a sentient species.

Now about 15% of the habitable worlds you visit will have a sentient species that matches your own. About 35% of habitable worlds will have a sentient species drawn from the pirate empires. About 50% of habitable worlds will have no sentient species at all, at first. People who depart your city to live in the wilderness will establish the sentient species of worlds that do not have one.

Spacecraft and building blueprint exchanges were simplified. Features that were only relevant to the online game were removed or hidden.

Game startup was simplified and revamped. There is no longer a sense of new vs old DNA. Instead the choice is between human and alien DNA. Comments about unfinished DNA features were removed.

A weird bug was fixed that caused entry into the designer to often put you on a planet somewhere instead, not in a designer.

I am now working on integrating with Steam Workshop, for the sharing of blueprints.

I may also integrate the Steam Achievements features.

At that point I will likely release Hazeron Starship to the public.

Scope: Decay/Abandonment


Issue: A change was made by Haxus to Hazeron Starship previously to remove the penalties of decay/Abandonment. It seems to function but it's not 100% effective. For example, same solar system with multiple planets and cities, some will suffer abandonment/decay while others will not. See picture below for more details. 


Current remedy: None


Steps to reproduce:
1. Don't play for a period of time.
2. Load game
3. Check cities overview and observe



Pictures

Hi everyone. Wow what happened? It's December?

I got my little computer center all set up in town at the beginning of the year with plans to work like crazy on the game. Life overwhelmed me like a tide and Hazeron was gone like so much flotsam. For the past few months my office has been completely inaccessible, filled with furniture from other parts of the house due to renovations. I only regained access to it last week.

Luckily the servers did pretty well during that time. I mostly ignored them. There were a few problems that required restarts but all in all they ran well enough all summer. I missed the uninterrupted power of the computer center. It seemed like every time a big thunder storm blew through town the servers lost power briefly, enough to reboot them.

When I set up the servers in town I paid all of the expenses for the first year. That year is nearing its end. It has become too expensive to operate them. I am going to shut down the servers, likely in January 2023. The rent on the office space is trivial so the servers will remain there, with only the web/email server powered on.

The game servers will be down indefinitely. If the Steam version brings in any significant amount of money I might consider reviving them, just for fun.

My efforts will now focus entirely on making a good complete Hazeron Starship game to release on Steam. The software is about 99% ready for that. I also want to add a little more story content and design more building and ship models. Those things take time. 

I considered adding LAN play capability. It would not be difficult. It will take time to get it right and it isn't needed for the solo game. I decided to save that for a future update.

Some people already have access to Hazeron Starship on Steam. The about box will show Software Engineering, Inc. as the owner. That version will no longer receive any updates due to the change of owner to Hazeron Freehold LLC.

If you would like to continue getting updates to Hazeron Starship, or if you would like to become a beta tester, send email with your Shores of Hazeron account name. If you do not have a Shores of Hazeron account you are not eligible to be a beta tester.

Have a Merry Christmas.

Haxus

Got a weird one, the Space Transport, Spacefighter F1 , Spacefighter F2 will not take throttle controls.
It will however react to thrusters, pitch & yaw , turns etc.

All other vehicles work fine.

Tried remapping, having another user drive it first, .... really the whole checklist , up and down.

Thought that might be interesting.

I recently went through a couple threads talking about inbalances in the warfare system. The main point as I recall it is that big empires have too great an advantage, and can easily wipe out a much smaller empire with little effort and within hours (noobstomping), often before the defending empire's players could react.


This can also happen to more established empires, who can log in regularly and still find that most of their empire has been taken before they were even aware of an assault.


This is hurting the playerbase and the overall fun of the game as many newbies or new empire builders find their efforts destroyed without any sense of control. Many of these players then leave the game, leaving both sides worse off than before (attacker gets no challenge, defender quits).


Current suggestions to fix this have been (and I apologize as I will miss some, but I wanted to list the big ideas I recall):


1- Make war declarations formal with a long timer, giving defenders enough time to prepare (scaled for empire size difference)

2- Increase base defensive structure strength

3- Limit maximum ship size

4- Full protection for a defined time before attacks can take place (similar to point 1)



There has been pushback against all of these suggestions, for, as far as I can tell, the following reasons:


points 1 and 4: Unrealistic (insofar that it feels like a forced mechanic that takes away the immersion and free-feeling that SoH is loved for) and merely delays the inevitable. Offers possibility of strategic retreat and building new colonies though.


Point 2: Brings too much imbalance in favor of defenders in relatively equal empires, resulting in boring stalemates and no reason to attack worlds anymore

Point 3: Another unrealistic limit (big ships is big part of the fun of the game).


My suggestions below will aim to help fix the problems above, and make the warfare system enjoyable for all parties whatever their size while keeping it (relatively) simple and easy to add/code.

I will display my suggestions one by one, explaining them as if they were already actual features, like patch notes (I find this way easier to understand, maybe it's also the case for you :) )


Let me know your thoughts! Thank you.




Suggestion : warfare city status


Defending cities can have one of three status: Besieged, Captured and Assimilated.


An enemy spaceship being within planetary orbit of the world immediately puts all cities on this world is a state of siege, meaning they cannot receive resources from other worlds or cities.


Besieged cities retain all possibility of construction. However, construction is slowed to X% of original speed. Speed decrease is dependent on city loyalty level - the higher the loyalty, the smaller the penalty.


Captured: Once the attackers troops have defeated all defender troops and disabled all of the city's military buildings, the city enters a state of capture. The city will slowly be assimilated. Assimilation time depends on loyalty level (and number of militia citizens, if implemented). Attacking troops will remain in the city and deal with militia until assimilation or total destruction of militia troops. Running out of attacking troops will return the city into the "Assaulted" state. Construction by attacker possible, but slowed strongly down to X% original speed (sugg. 5-10%)



What problem does it fix?

The besieged mechanic is actually in favor of the attackers - this is to prevent sudden buildups of defenses which would be unfair to the attackers. It also simulates the difficulties of building when under attack.

However, the dependence on loyalty makes the penalty smaller for smaller empires, which are able to maintain higher levels of loyalty, making last-minute defenses easier. See next points.




Suggestion : Bring back city loyalty



When captured, a city's loyalty will slowly decrease until it reaches zero. The city will then go from captured state to assimilated empire city.


What problem does it fix? - Read on.


Suggestion: Increase loyalty difficulty with empire size


Citizens of large empires find it harder to relate to the whole empire, making it harder to accumulate loyalty. Worlds develop a loyalty cap based on their distance from the empire capital. Conversely, the smaller the empire, the fiercer the loyalty to it.


Avatars visiting a system temporarily boosts loyalty.


What problem does it fix?

This makes smaller empires harder and longer to assimilate, giving them a small time advantage when fighting bigger empires. It also makes defense of large empires more difficult, putting more pressure on one-man empires and rewards multi-player empires.




Suggestion: Increase spacecraft, building and defense system durability


All ships, shields and buildings are a lot more durable, making their destruction take longer.


What problem does it fix?



Space battles and world assaults will last longer, giving more time for all parties - particularly defenders - to prepare and rally.






Suggestion: New troop system




Troops are calculated numerically just like citizens and cryo passengers. A city's troop count is based on the number of barracks and is limited by the city's current population. Troop % of total population cannot exceed x%.


A ship may load a certain number of troops, depending on the number of berths.


Troop strength is calculated to generate the total power of the sum of troops at any one place, for instance in a city or at a battle.


Troop strength is based on type of weapon, armor and quality of both, per troop. Stronger materials and better quality enhance troop strength.


Troops take a certain fixed time to be trained.


Troops also consume food like citizens do, even onboard a ship. Running out of food will put troops into a state of starvation, making their strength strongly reduced, with some dying over time like citizens do.


(BONUS: As troops get more experience fighting battles, they gain a slight strength bonus)




What problem does it fix?



Cities will naturally have a larger capacity of troops over ships. This gives defending cities an advantage. Since most newbies will have the possibility of creating stronger cities before creating stronger ships, this can help with the balance when facing tough empires.


The food system adds complexity to attacking empires as they have to manage their food levels as well, while defenders always benefit from the home-farms advantage. Currently though, food is easy to get and would only be another ticked box for attackers to stock up millions of units of food onto a ship, which brings me to the next suggestion:





Suggestion: Increase citizen and troop food consumption dramatically


Citizens and troops consume much more food, making the management of farms and food stocks much more important.


Currently, food is hardly ever an issue anywhere for any empire. However, it was a management nightmare for any large historical empire. It should also be so in SoH, particularly to prevent spontaneous attacks that cost nothing but a bit of hydrogen.






Suggestion: New automatically calculated ground battles



Once a city's military defenses are disabled (guns and shields), attacking ships will be given the chance to unload their troops into the city through a simple panel. From then on, ground battles will take place automatically over time.


The attackers' troop count and strength will be pitted against the defender's troop count and strength. Battles will take place over time, with each side taking casualties based on their strength. The larger the troop count, the longer the battles. Attackers and defenders may add more troops at any time, though defending ships incoming towards the world with troops must first break through the city's siege (defeat besieging ships) before they can unload their troops. Defeating an assaulting ship does not defeat the ground troops once deployed.

The status of the battle can easily be viewed within a report - perhaps by mail or some other tab. Reports would come in every few minutes, much like a normal city report. It would detail the forces on each side, the losses and perhaps the supplies if implemented.

Small battles would typically take a couple hours, while taking over a well-defended, established world taking days or even weeks.


(BONUS: To make it more tactical and complex, we could add the mechanic that certain resources are being depleted as the battle goes on - food, ammunition and fuel. Running out of any of these give a fighting penalty to that side. This makes pre-ground warfare, such as colony attacks or long sieges more worth it and brings more fun in terms of tactical play. More text-only elements can also be added to add complexity and diversity to combat, such as SUVs, tanks, dynamite and other weapons that are currently serving no purpose. We'd have to adjust their production cost and time ofc, with perhaps a maintenance fee to ensure that they don't get stacked to infinity. Since this is purely text-based, implementation should be easier than a full-on graphic mechanic).



Attacking parties require an online avatar of the same empire to be within planetary range of the besieged city in order to conduct ground assault. Ground defense does not require an online avatar.


If the defending side's troop strength reaches zero, the city if officially captured. Loyalty will slowly decrease until the city is either returned to assault state or fully assimilated. An online avatar is not required for loyalty decrease, only ground troops to remain present.


(BONUS: Running out of food or ammo during assimilation reduces the assimilation time.)


(BONUS: If weapons and ammo remains, the city enters a state of militia, where a portion of citizens fetch the remaining weapons and carry on fighting. The city will officially be captured, but loyalty decrease will be slowed until militia is fully depleted. Number of ground troops impact militia decrease speed.)




What problem does it fix?


It makes city conquest simpler, more strategic and also last much longer, giving defenders more time to rally and defend. It also makes loyalty a worthwhile feature.


Having to have an online avatar to conduct assaults forces more commitment onto the attacking empire, making spontaneous attacks less appealing.

The constant pressure of having food and ammunition would force attacking players to be in full-management during war time, making each decision to attack weaker empires require much more time and planning. The objective here is that larger empires that simply toss ships with lots of troops at a smaller empire without prior planning may find themselves either winning at a high cost or downright losing if they are completely careless.

With war requiring full attention, it also makes home defense more difficult, giving larger empires an incentive to commit properly to each war they want to carry on.

There would be no formal declaration, no waiting time - simply some semi-realistic mechanics that make attacking an empire a much bigger hassle, making it a lot less worthwhile if the aim is simply to "have fun noobstomping".







Suggestion: Battle bonus for "last world standing"


Cities defending on ground on the only remaining world of an empire will get the "last world standing" bonus while in battle, where troops and citizens, having nowhere else to go, fight to the death for their remaining land.



Cities with "last world standing" have all their citizens go automatically into militia, weapons or not. All population must be defeated for assimilation.



Re-capture of cities with "last world standing" by the defenders automatically brings a large population boost as fleeing citizens return to the city.





What problem does it fix?

This mechanic helps newbies who have their homeworld attacked without having had the chance to build other cities. It slows down assimilation and gives a starting boost upon recapture.




Other bonus ideas that fit with this theme:

- Disable spaceship destruction + towing + dismantling.

Spaceships are no longer directly destroyed when they reach critical HP - rather they become inoperable. All shields are down, all doors open, boarding can take place. Attacking the ship again will destroy it. If another spaceship initiates the "tow" order, the inoperable ship will follow the ship. Inoperable ships can be repaired, refitted or their modules dismantled.

This would give an incentive for smaller empires to attack larger empires' ships so as to capture them. They can be repaired and used or dismantled and their pieces used for research.

This would also give an incentive for smaller empires to ally themselves in order to assault a bigger empire's prize ships and make them their own, or dismantling them to get a huge boost in technology advancement. This would create more fun and excitement for small empires and keep larger empires on edge as their own tech could be used against them.


- Battle signature on star map.

Much like the warp signature, the firing of high-strength explosives would reverberate through deep space, allowing other systems (and empires) nearby to be aware that a battle is going on.

Reason: It would give an incentive to more players to join the fight, particularly underdogs or rivals. Also, if it's a large empire going on a rampage, other empires could know of these assaults and prepare themselves as well.


I would have some more suggestions that are linked to an overhaul of the value of resources, so as to make warfare actually worthwhile besides just the fun of it, such as a much higher scarcity of resources (particularly quality resources), much stronger population limits, more unique resources in the galaxy (like say, particles that boost your warp speed, like nitro) which would make empires fight over control of precious resources and control points.

The objective of the above and this would be not to forcefully get larger empires not to attack smaller ones, but to make such wars just "not worth it", and make each conflict meaningful, strategic, elongated and balanced, so as to maximize the fun for everyone, attacker, defender and noobs alike :)


Let me know your thoughts! Particularly Haxus, as after all, he would be the one implementing any changes (i've tried to summarize the ideas in a way that would make it easier to imagine how they can be applied practically).

Thanks!

Thinking about it more following this thread I came up with another catastrophe idea for new players. I imagine that it would be likely to have a random starting scenario chosen from amongst several. While not mentioned, any and all of these catastrophes would have in-game alerts which keep the player updated as to the progress of the event, perhaps via mail? The concepts below hinge on the ability of planets and stars in Hazeron to be able to change based upon in-game triggers or otherwise according to a script. It would also (possibly?) require atmospheric density to change based upon triggers. None of this may be possible with current game code.

Stellar Evolution A - Maturing Star
The primary star in your solar system is about to cross the threshold into maturity causing it to expand in size and change spectral type becoming larger and while cooler overall, its diameter reaches farther into the solar system and is heating planets closer than the habitable zone as well as causing their atmospheres to become corrosive. Inferno worlds remain the same, inner becomes inferno, habitable becomes inner with corrosive atmosphere. Outer and frigid worlds remain the same. Large (titan/habitable) moons acquire corrosive atmosphere. Gas giant planets are unchanged. The progression of this catastrophe would be gradual enough to allow players to see the event coming and the completion of the event, while quite difficult, would not be insurmountable even for an inexperienced player. The evolution of planet types should move outward from the star, allowing players to witness the catastrophe's progress.

Stellar Evolution B - Flare Star
The primary star in your solar system is unbeknownst to you and your empire, a long-period variable also called a flare star. A new period of stellar instability is beginning and will gradually heat all planets in the solar system causing their habitability type to move toward heat as well as causing their atmospheres to move toward corrosive. Inferno worlds remain the same, inner becomes inferno, habitable becomes inner, outer becomes habitable, frigid becomes outer. The atmospheres of all planets evolve to be corrosive. Previously corrosive atmospheres evolve to become insidious, thus destroying vegetation and animal life and simulating the inability of life to adapt to such a rapid environmental change. Large (titan/habitable) moons evolve to become airless. Gas giant planets are unchanged. The progression of this catastrophe could be as rapid as the asteroid while still giving a player sufficient time on the surface of their failing planet if they are sufficiently prepared due to it not being outright annihilated. The evolution of planet types should move outward from the star, allowing players to witness the catastrophe's progress.

Stellar Evolution C - Cataclysmic Variable Star
Your solar system is at least a binary with the smaller secondary star accreting mass from the larger of the two. Over long periods of time this fresh hydrogen builds up and eventually causes instability leading to a stellar eruption smaller than a nova but larger than a flare. This outburst will turn all planets in the system into their hotter and more inhospitable counterparts while completely destroying inferno and inner worlds - habitable become inferno, outer become inner, frigid become inner. The atmospheres of all remaining planets evolve to be insidious, thus destroying vegetation and animal life and simulating the inability of life to adapt to such a rapid environmental change. Large (titan/habitable) moons evolve to become airless. Gas giant planets are unchanged unless they are closer to the star than habitable in which case they are destroyed. The progression of this catastrophe could be as rapid as the asteroid but is so unforgiving that they could merely watch as their planet fails, becoming utterly uninhabitable without fairly mature spaceship technology. The evolution of planet types should move outward from the star, allowing players to witness the catastrophe's progress. Visual effects used for black holes (potentially reduced in strength) could be repurposed to simulate the cataclysmic flare.

Stellar Evolution D - Nova
Your solar system is at least a binary with the smaller secondary star accreting mass from the larger of the two. The mass is building and will eventually cause a classical nova, a more rapid and destructive form of flare and not considered to be the "space explosion" of typical larger supernovas. The star does not detonate but the force of the nova will reshape the solar system. All planets closer to the star than outer are completely destroyed, moving outward from the star, while frigid planets become inferno worlds. Gas giant planets are destroyed. If the solar system started with no frigid planets, the solar system will have no planets left. Visual effects used for black holes could be used to simulate the nova.

Stellar Evolution E - Supernova
More immediately destructive than the Nova catastrophe, this one begins the same as the nova but the result is that everything in the solar system is destroyed including companion stars. The primary star is replaced with a white dwarf and nothing else remains from the destructive progress of nova, with each planet being destroyed moving outward from the star. Visual effects used for black holes could be used to simulate the supernova. The primary star left behind by the supernova could potentially be a new classification of star: remnant. It could retain the special effects used when orbiting a black hole to reflect its supernova-remnant origin. If possible this event could trigger propagation across the sector commensurate with the speed of light in Hazeron, affecting nearby solar systems within a set radius: planets in these nearby solar systems would have their atmospheres become corrosive. Obviously it would be unreasonable for a supernova to bring detriment to the entire sector so this radius of effect would only be a true hazard in extremely dense sectors of a galaxy.

Stellar Evolution F - Black Hole
This concept could be problematic but would otherwise be very easy to implement as it would only require one trigger: when time runs out all planets are destroyed and the primary star replaced with a black hole. The effects and destructive progress of the primary star becoming a black hole could be similar to that used for the Supernova catastrophe, with each planet being destroyed moving outward from the star.

If any of the above concepts are possible, I imagine many more could be developed such as a rogue planet catastrophe (like the asteroid but its a whole planet or moon or even black hole).