Actually, that\'s quite a good point... Hrm, I might just whack it together in an hour or two - it won\'t look that pretty, but then I\'ve only wasted an hour and a half instead of days

Gah - I\'m just a sucker for trying to make things structured... heh

There are a LOT of posts in these forums, and it\'s REALLY hard to find some things that have already been mentioned - which leads to the usual \"you\'re stupid for asking a question again\" thing that is pretty much the one thing that annoys me on forums in general.

So, a suggestion is to have someone / some people in charge  of getting decisions finalised and summarised. There are various ways this could be done...

1. Have \'sub-boards\' (I\'m mainly thinking of WishList here), entitled \'Closed Discussions\'. When a discussion reaches it\'s end, either when the devs have decided \'yes - we want that\', or when the fans have said they would like it (even if the devs haven\'t approved it yet - it\'s just a recommendation put forth to the devs), the topic(s) relating to that discussion are deleted and a new thread is added to the closed sub-board giving an overview of the points, and the final outcome.

2. Have a completely seperate webpage detailing problems/wish list discussions that have been closed. It would act as a knowledge base for people with problems, and a recommendations-document for the dev team (like a design doc, but not finalised).


I\'m willing to make a \'test idea\' for 2 if people are interested. This project seems to be spiraling outwards and upwards, and I would love to be able to see the future of the project by looking through just one place, and not gleaming little bits from here and there. I would be willing to go back through some old forum topics and make a structured page for the dev team, that would effectively be the bugTracker, but without the technical info, and obviously not mixed in with too many comments (it would be post-discussion items that have been decided upon or closed).

Thoughts? Comments? A better suggestion?

Yeah - maybe I used an incorrect terminology. I\'m probably still not going to put it right - but I think that any good game needs to at least rely upon logic / \'realism\' in the sense of what you can do.

Sure, it\'s fantasy - but the world obviously relies upon things like gravity and physics - but in order to suspend your disbelief - you at least need a reason. It doesn\'t really matter how good that reason is, but if something doesn\'t act like it should in reality - we need to be told this is the case, or else we just think that it\'s something that\'s been forgotten / misprogrammed.

Anyhow - The more weapons the merrier, as it provides more variety in the game. I would say to make it a pretty unwieldly weapon, so that it\'s definitely not something you would choose to fight with, but something that poor characters can use that\'s better than fists!

Unless of course - he was referring to 1 Giga-bits of data

...you\'re supposed to not fight monsters with a pick axe...

But in Real-Life you could. Sure, it\'s not the best weighted item to use as a weapon, but it packs a pretty decent armour-piercing punch, so I don\'t really see why it\'s not usable as a weapon...

See: http://www.planeshift3d.com/wbboard/thread.php?threadid=14937&boardid=17

It\'s interesting to see that this problem only seems to appear on Laptops. It *could* be something to do with the Radeon Mobility graphics cards - I know that the mobility drivers are often behind the Catalyst drivers. Perhaps I could tempt you to try the \'OmegaDrivers\' - which will allow you to install the most uptodate ATI drivers even on a Mobility card.

Otherwise, the only other thing I could think of is checking the size of your paging file. If you\'ve only got 256MB of ram, I would make sure you have at least 768MB of paging-file space to ensure there is enough RAM available at runtime.

Personally, I think it\'s likely to be a driver thing - but don\'t quote me on that

You can find the Omega Drivers at: http://www.omegadrivers.net/

Wow - it looks quite impressive, and I look forward to trying it out when I return home from my time away.

It would be really nice to see a variable GUI system in which you could either choose a GUI, or have one defined for your race (as mentioned above).

However, I wouldn\'t classify it as massively important - it would be nice. I think I would vote for \'choose your GUI\', because then you wouldn\'t NEED to have one for each race, and you wouldn\'t be put off playing a race just because it\'s related GUI isn\'t that great.

You can always send patches to me. But you should probably ask me a bit before hand if what you are working on would be acceptable ( unless it\'s just a bug fix ).

Of course - I just generally like to play, trying to add new things, or hunt down bugs that seem hard to fix (beats doing crosswords). Just nice to know if my playing spits out something nice [sic] that it would be something I could forward to you guys.

Plus you have to be aware that any code you submit to use will be copyright to Atomic Blue.

Of course - it\'s all G[NU]ood by me! Sorry, It\'s 4am. I\'ll shut-up now and stop forking through the PS code.