[v1.11] Chest-Control v2.2.2.2

Yes, I'm sure. The chest files saved about 6-10 of the chests out of the 20-30 of them, but it doesn't save all of them.

Forcing a world save with /save doesn't get them to save either.

Edit --

I deleted the two present chest files and did /save and nothing gets saved.

Just for more info, nothing in the log file shows any error as to why its not saving:

Code:

2012-02-10 06:31:20 - Commands: INFO: atom0s executed: /save
2012-02-10 06:31:20 - Utils: INFO: Broadcast: Server map saving, potential lag spike
2012-02-10 06:31:24 - Utils: INFO: Broadcast: World saved.
2012-02-10 06:31:24 - ThreadHelper: INFO: World saved at (C:\Users\Administrator\Documents\My Games\Terraria\Worlds\world1.wld)

The ChestControl log just shows history of the chest items and no errors too.

Edit ---

Here's a pic of the chest setup:


The green ones save properly, the red ones don't save at all other then the items. Which is part of the map. They are missing from the chest txt file.

Quick update, it seems that the plugin does not work with the /save command. It requires the servers actual World Save event to fire to have the chest data save.

Perhaps you could add a /csave command to add chest saving on request? As well as adding it to the /save command.
Or if its a Tshock bug that /save doesn't push the event, I can report that instead.

Is saving effective from the server console without the "/"save ?

Nope, it only seems to save when the servers automatic saving cycle is fired. Forcing a save does not work.

i got a question
when i update to a new version off tshock all the protected chests are not protected anymore
so how do i keep them protected ?

Assuming the API is the same (which it is between 3.7 and 3.8), you just need to go into the 'tshock' folder of the old server, and copy the 'chestcontrol' folder into the 'tshock' folder of the new server package.

Never had this problem, and it shouldn't rely on /save for this plugin to work, since the plugin writes the content to a .txt when content is added/removed to protected chest, or when the protection is added/amended/deleted.

Edit: I tl;dr'd some of this thread....

Edit Edit: A remotely possible cause is that you had the world's chest protection text file open when adding the chests - can't write to open file, and all that.

ah thx man u really helped me out !

The text file is actually only written out on server shutdown. It is in the 'OnSave' function, but it doesn't perform the write to file until the server is shutting down.

I have a version of ChestControl that writes to the tShock database, but it is still going through some tests. No ETA.

OMG! Finaly i found plugin like this! Finaly - no cheating! - no griefing!

I have updated my version of this ChestControl that includes timed refills. It also writes to the tShock database instead of the text file. (It really should write to its own database, I may try to do that in the future.)

Here is the download (2.2.3.3).

Here is my version history:
Update 2.2.3.3: fixed issue with non-refill chests on save
Update 2.2.3.2: save chest info when it is changed
Update 2.2.3.0: log file uses datetimestamp filename
Update 2.2.2.9: Save Refill chests on world exit / save

Can I get the source to that?

https://github.com/HySpeed/Chest-Control

_Jon, it states that everyone can use /cunlock however guests cannot, therefore it would be nice if you either added a permission for that or made it compatible with guests

I'm sorry, but I didn't write that part, so I don't plan on changing it.

What I can recommend, however, is that you can add the permission for unlocking to the guest group in your group configurations. tShock is so flexible that you control even this - what permissions the guest group has.

If you were to go to Commands.cs (https://github.com/Deathmax/Chest-Control/blob/master/Commands.cs) and on line 22 you added "protectchest" before it says UnLockChest do you think it would work?

that would allow everyone to protect chests. If you want that feature, just add 'protectchest' to your 'guest' group's permissions.

Why are you letting guest's protect chest's, that's not very secure, someone else can just create a char with the same name and be able to get into that guest's chests.

When using this I get this upon saving:

Code:

2012-04-29 17:24:38 - ChestControl: ERROR: [SaveChests]: one(242) : System.NullReferenceException: Object reference not set to an instance of an object.
  at ChestControl.Chest.RefillChest()
  at ChestControl.ChestDbManager.SaveChests()

Protection seems to stay active just fine upon saving and restarting. The error only occurs when a chest has no refill enabled it seems.