This page is only for discussing the main page itself.
- For general discussion about NWN2Wiki, please post to the Community Portal talk.
- The administrators are available for wiki help or NWN2 related questions.
All edits made will now receive careful scrutiny by your new staff member. Anything that is considered spam, or intended to be offensive will lead to a year-long ban. You may appeal this to the staff member who banned you, which will, until I find more staff, INVARIABLY be myself. I do not give more than one appeal per offense, and if you make multiple offenses, deliberately, you will earn a lifetime ban. Edits to the main page without staff consent will not be tolerated. No exceptions.
Regards, Karl "13621" Mjolnir
In regards of gamespy removing support... Edit
Howdy fellow members of NWN2 community,
I was wondering if it would be possible to modify the main page to link an external site for it, and before I even bother to give the link I'll express the reason why. Some of you may have already heard that gamespy no longer supports NWN1 or NWN2 meaning we can no longer search the servers through viable methods for a couple of days now.
Of course NWN2 community is quite well known for tech savvy solutions and even now quite a few people are working on solution to open visibility for persistent worlds to all public. Alas the issue is not so simple since nwn2 community is split between number of singular persistent world forums, sites and the likes. I feel we need a centraliced system of linking these solutions to general public view where people that are searching servers actually need it.
And with this comes the site I figured I'd petition to be applied to the main page as I feel it deserves a great attention while we still have a multiplayer community to run it for: http://www.nwnlist.com/
It is not a site made by myself thus I can't collect any credits of it, nor am I aware of the general nametag of the person making it. Also mind you this is still early stages of this problem, but I feel a good quick response to prevent issues is better than let the issue escalate and then try to fix it.
18.104.22.168 12:37, December 8, 2012 (UTC)