I have been typing up a small document to try and list the things I think we will need to make the kinds of multiplayer campaigning that is the core concept everything here revolves around. The idea is that the quicker we can gauge what Armed Assault has and does not have of the things we need, the quicker we can fill out the holes and start making something really interesting...
Basically I want to make a sort of check-list we can run through as soon as someone from here get their hands on Armed Assault, maybe some of it even before we get it that way we can prepare ourselves for what will need to be done without requiring 6 months or more to each individually learn the possibilities of the new game in SoW terms.
If anyone has any ideas about what they will need to make the perfect multiplayer campaigning mission, please let me know and I'll put it on the list...
The obvious things I have so far& ...
The previous versions had issues with the fact this is on a webhost that only allows Medium Trust. without explaining some specifics, most of the features were unavailable. As you can see now, there are comments available for the gallery images. There are some other benefits, but that is one of the big ones.
Still plugging away at the project management app. Man, this is tougher than I thought it would be. I guess this is why I am sticking to Windows Forms instead of doing Web stuff. I am also still getting a handle on the new ASP.NET 2.0 so it is more learning than actual programming I am doing. It'll get done though... you can be sure of that!
I'm getting warmed up for scritping by helping the SWAF guys develop some scripts for a big clan vs clan mission.
They are relatively simple and customized to the mission itself, but just hanging out in the Mission Editing and Scripting forum the last two days has been a good refresher. These scripts should get me back into the development mood quite quickly. I really need to finish this Project Mgmt system ASAP.
Boy, have I been busy..... I'm going to warn you now and say that I WILL be rambling throughout this post.
I am currently on Spring Break this week. While all the other kids are busy drinking and vomiting... I am here working on the Project Management module still. Unfortunately, three days have been taken away from me that I planned on putting some solid work into it. In any case, I still plan on finishing it by mid-April. It has been harder than I thought since this type of programming I am no where near used to doing. I am confident though. Just need to shake the initial culture shock. I am saddened by some missing tools I used to use in prior versions of the language :( I guess I got soft with all the automation of minor tasks.
I've also got yet another project in the works which may be interesting to a few of you (non-OFP related), but I am holding off on that until I finish the stuff for the SOW site. I won't disclose what i ...
It's good to see there is still activity here from the OFP community...
I took a quick look at the number of clicks each download has received since I started this new site.
At the time of this post, the SOW files (Manual, Demo, Tutorial, Nubbin's missions) are all averaging about 20 clicks. Rune's compression and save functions are closing in at 11 clicks and Fox's conversion script is leaving dust trails at 30+ clicks!
Can't say for sure if these are unique visitors but it's better than I would have expected!
Go team!
Well, the end is almost near.
The skin is done, and I like it much more than the previous. I hope you all do as well.
Project Management module is getting off the ground. Most of the initial work is design and I have that pretty much completed. The bulk of the programming will be started next week so I hope to have it up and running shortly thereafter. I won't make any promises, but I am shooting for mid to late April since we are going to need to test it thoroughly first.
If any of you are doing any work with OFP, I strongly encourage you to start posting some info in this journal/blog area. It will help all of us keep in touch in what we are all working on at the moment. I understand many of you are probably not as active anymore, but for those that are... YOU ARE ALLOWED to write stuff here! Same goes for the Gallery... (hmmm... perhaps I should post a "How To" for us developers. I'll&nbs ...
Today I've implemented some improvements to the save function tool package suggested by General Barron and Nubbin77, so it is now at version 1.1.
The changes include an init function to preprocess the functions easily, it has them all in a subdirectory and they have been renamed to have SOW_ tag at the beginning.
I have also finished a final polished suggestion for a new SoW logo today.
And then I need to take a break from all this fun stuff and get myself ready for my exam in a less than a month. So I will most likely not be very active until about april 4th 2006.
I've been working hard on getting some annoying little bugs/nuances corrected and here are some new improvements to the site as of today:
[LOGINS]
After leaving the website, the cookie which retains your login status was deemed old after 60 mins. So browsing to the website after that amount of time had passed asked you to login even if you had "Remember me" checked. I pushed it out to 1 week now. I may go further out if asked, but logging in once a week should be easy enough.
[DEVELOPER GALLERY]
The author of this module has given me some great improvements.
1) Unregistered users (not logged in) should be shown the public image galleries when viewing the page.
2) Registered Users should have same effect as above since they aren't allowed to create albums/upload images.
3) Registered Devs should see their own albums upon first view, but can vie ...