15 replies to this topic

[CoderJohn]

As you may or may not know, anytime you break a computer and replace it, it generates a whole new computerID.

Well here is my suggestions for this:

a.) Keep the computer id for the computer you pick up. (when you move a computer in real life it doesn't lose all its files)

b.) Simply erase the data for that computer and reuse its id before generating a new one. (this makes it easier to know how many ACTIVE computers there are in a server)

My reason is fairly simple, eventually the computer id will get too high. Especially if you are running an old server. Not to mention your real computer holds all that data for every single computer(even ones that have been broken and are no longer available). This is a waste of real computer space and it is pointless to generate a new id when an old one can be used.

[Shnupbups]

*cough* labels *cough*

[Orwell]

 Shnupbups100, on 16 November 2012 - 03:43 PM, said:

*cough* labels *cough*

To elaborate on that: setting labels on a computer will keep its files intact, even after breaking and placing again.
In the CC terminal; to set the label:

label set <label name>

To get the label that's currently set:

label get

[Cranium]

This is not necessary. If you want to keep the ID but get rid of the files, you can just use the lua prompt like this:

for i,v in ipairs(fs.list("/")) do fs.delete(v) end

[Orwell]

 Cranium, on 16 November 2012 - 05:17 PM, said:

This is not necessary. If you want to keep the ID but get rid of the files, you can just use the lua prompt like this:

for i,v in ipairs(fs.list("/")) do fs.delete(v) end

Wouldn't that error while trying to delete the rom directory?

Anyway, a solution on both problems. />

[Cranium]

It would error out, but it's the easiest and fastest way to delete all the files. I use it when I just want to wipe a computer.

[CoderJohn]

No I am saying even if you break a computer, and replace it, the id is lost and a new one is CREATED and the old data is not cleared so you just keep getting more files added to your real computer.

[Sammich Lord]

 Orwell, on 16 November 2012 - 05:46 PM, said:

 Cranium, on 16 November 2012 - 05:17 PM, said:

This is not necessary. If you want to keep the ID but get rid of the files, you can just use the lua prompt like this:

for i,v in ipairs(fs.list("/")) do fs.delete(v) end

Wouldn't that error while trying to delete the rom directory?

Anyway, a solution on both problems. />

To not error:

for k,v in pairs(fs.list("/")) do
  if not fs.isReadOnly(v) then
    fs.delete(v)
  end
end

[Espen]

 CoderJohn, on 16 November 2012 - 06:38 PM, said:

No I am saying even if you break a computer, and replace it, the id is lost and a new one is CREATED and the old data is not cleared so you just keep getting more files added to your real computer.

Well, if you replace a computer with a new one, then that is the expected behaviour.
Whereas when you give it a label (e.g. "set label Jimmy"), pick up that computer and place THIS picked up computer (not place a new one, look at the item-label!), then all your files will still be on that computer and no new directory is created.

If that isn't working for you, then you either aren't placing a labeled computer, or something is wrong with your particular Minecraft setup.

[Leo Verto]

 Espen, on 17 November 2012 - 12:22 AM, said:

 CoderJohn, on 16 November 2012 - 06:38 PM, said:

No I am saying even if you break a computer, and replace it, the id is lost and a new one is CREATED and the old data is not cleared so you just keep getting more files added to your real computer.

Well, if you replace a computer with a new one, then that is the expected behaviour.
Whereas when you give it a label (e.g. "set label Jimmy"), pick up that computer and place THIS picked up computer (not place a new one, look at the item-label!), then all your files will still be on that computer and no new directory is created.

If that isn't working for you, then you either aren't placing a labeled computer, or something is wrong with your particular Minecraft setup.

Or you're still using an outdated version of CC.

[Cloudy]

Starting from the next version, a folder for the ID is only created if something is written to it.

[Leo Verto]

 Cloudy, on 17 November 2012 - 11:26 PM, said:

Starting from the next version, a folder for the ID is only created if something is written to it.

Is that a new feature? It used to create a new folder once you start a new computer.

[Cloudy]

 Leo Verto, on 18 November 2012 - 02:43 AM, said:

 Cloudy, on 17 November 2012 - 11:26 PM, said:

Starting from the next version, a folder for the ID is only created if something is written to it.

Is that a new feature? It used to create a new folder once you start a new computer.

Hence why I said starting from the next version /> though it looks like we don't need to update for MC 1.4.5 as the obfuscation didn't change.

[EntombedJester]

Came here to suggest this because using this program from Turtle programs caused the files to sack up really quick. http://www.computerc...-clear-a-chunk/

[Tiin57]

 EntombedJester, on 18 November 2012 - 07:06 AM, said:

Came here to suggest this because using this program from Turtle programs caused the files to sack up really quick. http://www.computerc...-clear-a-chunk/

Cloudy, one of the CC devs, stated one post above you that the feature would be implemented in the next version of CC. -.-
Can't people read?

[EntombedJester]

Nope i can read just fine thanks. Wasn't saying anything like "OMG is there anyway to fix this!!!" just stated that I came here to suggest something because of what I saw. Nothing more, nothing less. Happy its being fixed.