|
|
Re: Mapping the ProductionQueue and ProductionQueueChange block |
Tue, 28 April 2020 19:59 |
|
ricks03 | | | Messages: 222
Registered: January 2012 Location: NC | |
|
Yeah, I've made a lot of progress since that post.
So what's interesting about the ProductionQueueChange Block, unlike at least many of the other blocks, is that, in the .x file, they don't stack.
In other words, if I:
-Create a ship design
-Change the ship design, edit the ship design
-Edit the ship design
-edit the design again
-edit the design again
I get entries for every change in the DesignChange block
The ProductionQueueChange block doesn't appear to work that way. It's just a list of what's current in the planet production queue. Massively easier to process, because whatever it is, it is. The DesignChange block is multiple entries.
https://www.irelandbybicycle.com
http://totalhost.sinister.net:999
https://github.com/ricks03/TotalHostReport message to a moderator
|
|
|
|
Re: Mapping the ProductionQueue and ProductionQueueChange block |
Wed, 29 April 2020 19:16 |
|
ricks03 | | | Messages: 222
Registered: January 2012 Location: NC | |
|
ricks03 wrote on Tue, 28 April 2020 19:59
The ProductionQueueChange block doesn't appear to work that way. It's just a list of what's current in the planet production queue. Yup, this is wrong.
.x file
BLOCK:9,Offset:18,Bytes:17 DATA DECRYPTED:28 0 84 117 220 1 165 220 166 89 122 197 97 8 0 0 170
BLOCK:29,Offset:37,Bytes:10 DATA DECRYPTED:19 0 1 24 2 0 3 36 2 0
BLOCK:29,Offset:49,Bytes:10 DATA DECRYPTED:19 0 3 0 2 0 1 8 2 0
BLOCK:29,Offset:61,Bytes:2 DATA DECRYPTED:19 0
Darn it.
[Updated on: Wed, 29 April 2020 19:17]
https://www.irelandbybicycle.com
http://totalhost.sinister.net:999
https://github.com/ricks03/TotalHostReport message to a moderator
|
|
|
|