Jump to content

P4rty_Boy

Member
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

P4rty_Boy's Achievements

  1. Well fair enough, but the point I want to bring is: Each feature you push/ask for is something else being pushed later on or dropped. You cannot have your cake and eat it too. At this stage of the game, I would rather have them work on stuff that is part of the normal game loop, and which could be impoved, rather than stuff thay maybe, will serve again one day. Here is a forum, a channel from the plyers to them, the developers. If you ask them to work on something that will not be used or maybe never be reused, and they listen to you, well we are losing something else that could be fixed instead. Let's try to be a team here & help the dev find our where their time spent working on the game will result in the biggest bang for the buck. And as a player, I did my talent selection, and I don't see the point on improving that interface, until next time they plan a talent reset - which should be, hopefully, never.
  2. Info for those who are switching Lua.... getElementIndustryInfoById() returns information, including a state, which can be interpreted like this: 1= STATUS_STOPPED 2=STATUS_RUNNING 3=STATUS_MISSING_INPUT 4=STATUS_OUTPUT_FULL 5=STATUS_NO_OUTPUT 6=STATUS_PENDING Sometimes industries goes into Server error, and I did not encountered that state yet. Also note that getSchematic() returns a table with tier & id, instead of the equiavlent JSON of level & name
  3. @NQ-WandererHey there! I'm in the middle of my Lua overhaul to work with Mercury. So far so good. Thanks for switching to tables instead of JSON, it makes my code way cleaner. The API additions, the slots for the player, and so on are great additions, thank you! I do have questions about the container updateContent() call, if you could clarify. The doc says, 1 call every 30 seconds. Is it; 1 call every 30 seconds, per container? If that's the case, that would mean that I would be allowed to update instantly, 10 differents containers on a single programming board. If that's not the case, connecting a programming board to 10 differents containers would require 5 minutes to know the content of all of them. Is it; 1 call every 30 seconds, per programming board, which means that I can have 10 containers, with 10 programming boards, and then I can see the content right away? Is it; 1 call every 30 seconds for each player? If I start a programming board looking into a container, and a friend start the same programming board 5 seconds later, will he be able to see the content of the container? Is it; 1 call every 30 seconds per construct? Thanks in advance!
  4. To be honest, spending 88.8M points should not happen. Why ask NQ staff to spend time on an API intended to spend efficently 88M points that will never be used again in the released game? I'd rather have them put time on tools we will use every day and part of the game. Remember we are still in a beta. Just my 2 cents here.
  5. FYI if you do a dumb replacement of receiver.setChannels by receiver.setChannelList, you get a game crash. Took me a while to figure out since I kind of swapped all deprecated functions, and when I started my programming board, I was getting a game crash with no indication why. I just forgot that setChannelList receive an array, and setChannels a string. I'll fill a bug report.
  6. Ideas to reduce LUA requests on the servers: - Add in the core, a construct version number. a Lot of lua code, start by scanning all elements in a construct, then doing its thing. 99% of the time, the construct haven't been modified inbetween 2 executions, so all Luas could just skip the scanning part by comparing the edition number (this number chould only be changed when you edit the construct by adding/removing/renaming an element). - For space station/industrialist, i do need to query containers volume & names and do a correlation with my industries, because the output element count returned by industries is not reliable. This bug has been reported since years now, and still not fixed. So fixing current lua bugs would be a great plus before going in to a new revamp. - Having a fast element & recipe API would also be great - glad to see the direction you guys are taking with the item API. Right now a lot of my lua in term of sizes, are tables with all the elements. - Very happy with the inclusion of the core as a default slot; a lot of my code was complicated for nothing, because it was not possible for me to have a connection for all my prog boards to the core. - A way to query the current FPS, so script can scale down computing/display on already strugging computers.
  7. Please a CTRL-F in the editor!!!! And block-select tabulation
  8. Before rolling out this change, would you consider implementing Tools to help player transit to that update? With this new constraint, we will need to dismantles constructs, and/or merge constructs that were on separate cores - because of older contraints (like the parenting before it was fixed). It is a lot of boring work, for no plus value for the players (other than conforming to Panacea). You can help make that transition less painfull by: - Add tools to disassemble a construct in the current container, instead of removing everything 1 by 1 - Increase the copy-paste volume size if possible - Enable copy-paste of elements - A tool to offset everything in the building zone - A way to align constructs, especially when using blueprints - Would you consider a tool to "upgrade" i.e. replace a core with a larger one? - Would you consider XL cores or cores with different shapes? A lot of our constructs are just tarmacs, ramps, parking space, voxel libraries, etc. They barely contains elements. Because of the small core, a lot of us endup with a box-style base. We used other smaller cores to build outside the base itself, just for aesthetic - and mitigate the box-like base. With more room, we can still keep the same base, but integrate the aestetic extras inside the same core. With all these tools, we could rearrange things around, and reduce the core counts (which is the intended goal). Please notice, that a lot of times, we are stuck with a higher core count because of previous game limitations. Example: We created parking space very far away from each other, with multiple core inbetween because of the bad parenting (that is now fixed - thank you).
  9. This long past due!!!!!!!!! If we need to deconstruct, please at least, make it easier to do!
×
×
  • Create New...