Resource Center: v3.4 in Off Topic

ID:112150
 
Apr 17 2011, 6:23 pm
STATUS REPORT
Total Unique Users: 1518
Total New Users Since Last Version: 89
Total User Visits Since Last Version: 218

Total Bonuses Given: 61100
Total Bonuses Given Since Last Version: 2675

Total Asset Submissions: 163
Total Approved Asset Submissions: 95
Total Asset Submissions Since Last Version: 3

Total User Earnings: $203
Total User Earnings Since Last Version: $9
Total PopLava Earnings Since Last Version: $0

Total Withdraw Amount: $33
Total Withdraw Amount Since Last Version: $0

Total Contributors: 55

Last Week:
Waiting to see if the server made it through the week and it has. The crashing bug was most likely due to some corrupt .sav file data. Purging it seems to have fixed the issue.

There are some outstanding issues reported which I will address tonight.


This Week:
- Investigate and fix withdraw system
- Investigate corrupt accounts (I have complete transaction history so its just a matter of reviewing)
- Re-enable the clock code.
- Review all new submissions
- Add total amount of Silver in play to weekly report
- Add Rank counts to weekly report
- Pick up where I left off on the PM feature work.

Connect: Resource Center
More: Info
#1 Apr 17 2011, 8:00 pm
...Can I say "Gratz" now? =)
#2 Apr 17 2011, 10:26 pm
You wouldn't happen to have a copy of the old savefiles that might have been corrupt, would you? I think it would be interesting to weed through those with my savefile reader and can find one that might've been corrupt.
#3 Apr 17 2011, 10:30 pm
[DONE]- Investigate and fix withdraw system
[WIP]- Investigate corrupt accounts (I have complete transaction history so its just a matter of reviewing)
[DONE]- Re-enable the clock code.
[DONE]- Review all new submissions
[DONE]- Add total amount of Silver in play to weekly report
[DONE]- Add Rank counts to weekly report
[WIP]- Pick up where I left off on the PM feature work.

I've reviewed all assets. During the crashes, a number of asset submissions were lost. If your asset wasn't approved, please submit it as a new asset and then send me the old asset ID so I can clean it out.

@Audeuro: I appreciate the interest but I won't be distributing the .sav file.
#4 Apr 17 2011, 10:32 pm
PopLava wrote:
@Audeuro: I appreciate the interest but I won't be distributing the .sav file.

That's cool- I was only going to try to help you find the cause of your bug.
#5 Apr 17 2011, 10:32 pm
Oh, and here are those new stats.

Total User Silver: 185260

Rankings:
Master Sergeant: 1
Recruit: 1065
Private: 58
#6 Apr 17 2011, 10:34 pm
Audeuro wrote:
PopLava wrote:
@Audeuro: I appreciate the interest but I won't be distributing the .sav file.

That's cool- I was only going to try to help you find the cause of your bug.


and I appreciate it. If the crash comes back (which is possible), I may take you up on your offer if its still good.
#7 Apr 17 2011, 10:46 pm
PopLava wrote:
and I appreciate it. If the crash comes back (which is possible), I may take you up on your offer if its still good.

Unfortunately I'm not really going to have the time at any other point due to the end of the semester rapidly approaching. I had extended the offer in the first place because I could've verified right then and there that something there might have been an indirect or direct result of the crashes you were experiencing, and I'm not quite sure why you were actually even skeptical. If you're storing sensitive data like that in a savefile, you should probably be re-thinking your design. Savefiles are extremely insecure.