The following warnings occurred:
Warning [2] Undefined variable $awaitingusers - Line: 33 - File: global.php(779) : eval()'d code PHP 8.1.27 (Linux)
File Line Function
/global.php(779) : eval()'d code 33 errorHandler->error
/global.php 779 eval
/showthread.php 24 require_once
Warning [2] Undefined array key "style" - Line: 837 - File: global.php PHP 8.1.27 (Linux)
File Line Function
/global.php 837 errorHandler->error
/showthread.php 24 require_once
Warning [2] Undefined property: MyLanguage::$lang_select_default - Line: 4950 - File: inc/functions.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions.php 4950 errorHandler->error
/global.php 837 build_theme_select
/showthread.php 24 require_once
Warning [2] Undefined variable $visibleonly - Line: 412 - File: showthread.php PHP 8.1.27 (Linux)
File Line Function
/showthread.php 412 errorHandler->error
Warning [2] Undefined array key 1 - Line: 1394 - File: inc/functions.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions.php 1394 errorHandler->error
/inc/functions.php 1359 fetch_forum_permissions
/inc/functions.php 2862 forum_permissions
/showthread.php 616 build_forum_jump
Warning [2] Undefined array key 1 - Line: 1394 - File: inc/functions.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions.php 1394 errorHandler->error
/inc/functions.php 1359 fetch_forum_permissions
/inc/functions.php 2862 forum_permissions
/showthread.php 616 build_forum_jump
Warning [2] Undefined array key "mybb" - Line: 1907 - File: inc/functions.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions.php 1907 errorHandler->error
/inc/functions_indicators.php 41 my_set_array_cookie
/showthread.php 624 mark_thread_read
Warning [2] Undefined property: MyLanguage::$ratings_update_error - Line: 5 - File: showthread.php(727) : eval()'d code PHP 8.1.27 (Linux)
File Line Function
/showthread.php(727) : eval()'d code 5 errorHandler->error
/showthread.php 727 eval
Warning [2] Undefined array key "additionalgroups" - Line: 6846 - File: inc/functions.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions.php 6846 errorHandler->error
/inc/functions_user.php 734 is_member
/inc/functions_post.php 398 purgespammer_show
/showthread.php 1057 build_postbit
Warning [2] Undefined array key "profilefield" - Line: 6 - File: inc/functions_post.php(466) : eval()'d code PHP 8.1.27 (Linux)
File Line Function
/inc/functions_post.php(466) : eval()'d code 6 errorHandler->error
/inc/functions_post.php 466 eval
/showthread.php 1057 build_postbit
Warning [2] Undefined array key "canonlyreplyownthreads" - Line: 641 - File: inc/functions_post.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions_post.php 641 errorHandler->error
/showthread.php 1057 build_postbit
Warning [2] Undefined array key "showimages" - Line: 699 - File: inc/functions_post.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions_post.php 699 errorHandler->error
/showthread.php 1057 build_postbit
Warning [2] Undefined array key "showvideos" - Line: 704 - File: inc/functions_post.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions_post.php 704 errorHandler->error
/showthread.php 1057 build_postbit
Warning [2] Undefined array key "additionalgroups" - Line: 6846 - File: inc/functions.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions.php 6846 errorHandler->error
/inc/functions_user.php 734 is_member
/inc/functions_post.php 398 purgespammer_show
/showthread.php 1057 build_postbit
Warning [2] Undefined array key "profilefield" - Line: 6 - File: inc/functions_post.php(466) : eval()'d code PHP 8.1.27 (Linux)
File Line Function
/inc/functions_post.php(466) : eval()'d code 6 errorHandler->error
/inc/functions_post.php 466 eval
/showthread.php 1057 build_postbit
Warning [2] Undefined array key "canonlyreplyownthreads" - Line: 641 - File: inc/functions_post.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions_post.php 641 errorHandler->error
/showthread.php 1057 build_postbit
Warning [2] Undefined array key "showimages" - Line: 699 - File: inc/functions_post.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions_post.php 699 errorHandler->error
/showthread.php 1057 build_postbit
Warning [2] Undefined array key "showvideos" - Line: 704 - File: inc/functions_post.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions_post.php 704 errorHandler->error
/showthread.php 1057 build_postbit
Warning [2] Undefined array key "showimages" - Line: 742 - File: inc/functions_post.php PHP 8.1.27 (Linux)
File Line Function
/inc/functions_post.php 742 errorHandler->error
/showthread.php 1057 build_postbit
Warning [2] Undefined array key "invisible" - Line: 1491 - File: showthread.php PHP 8.1.27 (Linux)
File Line Function
/showthread.php 1491 errorHandler->error
Warning [2] Undefined variable $threadnotesbox - Line: 30 - File: showthread.php(1518) : eval()'d code PHP 8.1.27 (Linux)
File Line Function
/showthread.php(1518) : eval()'d code 30 errorHandler->error
/showthread.php 1518 eval




Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
A few suggestions
#1
Hello again! I checked in on version .27, and was delighted to see you incorporated changes based on my earlier feedback about paths. I find the new system a lot more intuitive. Lots of other improvements too!

Since it seemed helpful last time I weighed in, I had a few other suggestions I wanted to throw out there, most of them intended to streamline zoning (which is already improved from the .25 version).

First, it would be great if you could select different size swatches, so you can paint larger or smaller areas. That'd be especially helpful for larger stations.

Secondly, when designing a station, it would be cool if you could copy/paste a component. (Maybe you already can, and I just didn't figure out how.)

Lastly, if you could copy and paste zoning between stations with livable habitats of the same size, that would be cool. I think it's possible the reason you don't already have that possibility is because right now, that's most of the task of building a new colony... Right now, if you copied and pasted all zoning, you'd be pretty much done.

But I want to compare this idea to how you can copy/paste station designs themselves. You can save and load designs. But you can't just take a LEO station design and use it in HEO out of the box. You can keep its structure and spin rate, but you have to change shielding, power, and heat sinks. You keep about 80% of it, and tweak the other 20% to fit the circumstances. It feels less like starting over from scratch, and more like refining something. Building on what came before.

Maybe you should be able to copy a zoning map to a new station, but stations in different orbits have different needs... Like ones further from Earth need more agricultural zoning, for example, due to the difficulty of resupplying food and oxygen. Or ones in the asteroid belt have a special zone for refining metals. Or whatever your research suggests might be an economic need in a particular region. If zoning can be copied, but 20% of it has to be tactically customized to the circumstances and role of the station, then you'd get the same "I'm building something new!" feeling without the "Oh man, I gotta start over from scratch..." feeling.

P.S. - and this is a really small thing that would be probably rather difficult to make happen - but it would be super cool if the police drones obeyed the Coriolis effect. I assume they don't yet, because their flight paths don't look weird. Coriolis usually make stuff look really weird! Disclaimer - I have only had a few emergencies, so I can't be sure you haven't already implemented something similar to my suggestion below, but the drones I saw flying flew mostly along the outside of the cylinder.

The quickest path in a rotating cylinder is rarely going to be a "straight" line along the surface of the cylinder, as that's similar to taking the outside track. They'd fly "up" really high and then "down" again, in what appear to be dramatic parabolic arcs (but are actually straight lines). They would also rarely want to fly along the rotation of the station. Rather, they'd fly against it, even if it looks "closer" to go the other way. Sometimes, they'd fly "straight" "up" to get where they're going, at least in a cylinder. I have no idea how difficult this would be, but it would be super cool if possible to implement, and if your physics are implemented correctly, I'm sure you'd discover further counterintuitive shortest paths to an emergency (or flaws in my own assumptions above).

Love the direction the game is going! Will definitely keep checking out new updates, and might add to this thread if I think of anything else. Heart
Reply
#2
Great ideas! I'm really glad you're enjoying the game, and I appreciate the time you took to write up these ideas!

Thanks,
- Joe

Joe Strout
Lead Developer, High Frontier

Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)