yetanothername

Who are you guys and why do we have a treaty with you? Treaty A Mutual Offensive Pact between the Red Star and the Grand Global Alliance The Red Star and the Grand Global Alliance, We are good friends via the NPO in CN, decided to bring there good friendship over into CN:TE and have agreed to the following: ARTICLE I The Leadership of both parties obligate themselves to desist from any act of violence, any aggressive action, and any attack on each other either individually or jointly with other powers. ARTICLE II The Leadership of both parties will consult together whenever, in the opinion of either of them, the security of either of the Parties is threatened by external and/or internal armed attack. Separately and jointly, by self help, the Parties will maintain and develop appropriate means to deter armed attack and will take suitable measures in consultation and agreement to implement this Treaty and to further its purposes. ARTICLE III The present treaty is concluded in perpetuity, with the proviso that both the Leadership of the alliances will become unbound from the terms of this treaty 48 hours after notice of it's termination for cause is given in the form of a public pronouncement from a duly elected or appointed leader of the withdrawing High Contracting Party, to be posted on the main RP board of the Cyber Nations Tournament Edition Forums and the respective forums of the other alliance ARTICLE IV This Treaty shall be ratified by the Red Star and the Grand Global Alliance in accordance with their respective constitutional processes and will come into force when announcements of ratification have been made via public announcement on their respective forums and the Cyber Nations Forums. IN WITNESS WHEREOF the undersigned signatories have signed this Treaty: For the Grand Global Alliance: yetanothername, Emperor maxfiles, Regent rstat1, Vice Regent For Red Star: Severus, Avant-Garde of Red Star Zblueblur0, Magistrate of Internal Affairs Lord of Destruction, Magistrate of Military Affairs Vasily Karasov, Magistrate of Foreign Affairs

Yes, really.

Hi, do you want to sign a treaty?

I'm mocking you mock me. </offtopic> Thank you LJ.

CyberNations Internet Relay Chat Alliance Guide for the Coldfront LLC Network So, you already set up your alliance forums, you have a charter, you have government members who you can trust? Well, do you have an IRC channel? In this mini-guide it is assumed that you already know the absolute basics of IRC, such as how to connect to servers, register your nickname, etc…. This guide will cover registering a channel, setting up your alliance’s IRC network as well as access lists and channel modes. Step 1: Registering your channel If you have not done so, join you’re the channel that you want to be your alliance’s public channel. You need to have channel ops (Channel mode +o and/or a @ by your name and the channel must NOT have the modes “ntr” if the channel does, it means that it has already been registered and you need to pick a different channel) Type this into your client: /msg Chanserv REGISTER #channel password description (Replace #channel, password and description with your own values) [19:51] ChanServ [services@coldfront.net]: Syntax: REGISTER channel password description [19:51] ChanServ [services@coldfront.net]: [19:51] ChanServ [services@coldfront.net]: Registers a channel in the ChanServ database. In order [19:51] ChanServ [services@coldfront.net]: to use this command, you must first be a channel operator [19:51] ChanServ [services@coldfront.net]: on the channel you're trying to register. The password [19:51] ChanServ [services@coldfront.net]: is used with the IDENTIFY command to allow you to [19:51] ChanServ [services@coldfront.net]: make changes to the channel settings at a later time. [19:51] ChanServ [services@coldfront.net]: The last parameter, which must be included, is a [19:51] ChanServ [services@coldfront.net]: general description of the channel's purpose. [19:51] ChanServ [services@coldfront.net]: [19:51] ChanServ [services@coldfront.net]: When you register a channel, you are recorded as the [19:51] ChanServ [services@coldfront.net]: "founder" of the channel. The channel founder is allowed [19:51] ChanServ [services@coldfront.net]: to change all of the channel settings for the channel; [19:51] ChanServ [services@coldfront.net]: ChanServ will also automatically give the founder [19:51] ChanServ [services@coldfront.net]: channel-operator privileges when s/he enters the channel. [19:51] ChanServ [services@coldfront.net]: See the ACCESS command (/msg ChanServ HELP ACCESS) for [19:51] ChanServ [services@coldfront.net]: information on giving a subset of these privileges to [19:51] ChanServ [services@coldfront.net]: other channel users. [19:51] ChanServ [services@coldfront.net]: [19:51] ChanServ [services@coldfront.net]: NOTICE: In order to register a channel, you must have [19:51] ChanServ [services@coldfront.net]: first registered and identified for your nickname. If you [19:51] ChanServ [services@coldfront.net]: haven't, /msg NickServ HELP for information on how to do so. If the registration goes through, you will see the following appear: [19:54] ChanServ [services@coldfront.net]: Channel #mychannel registered under your nickname: yetanothername [19:54] ChanServ [services@coldfront.net]: Your channel password is imnotthatstupid -- remember it for later use. [19:54] ChanServ [services@coldfront.net] has set channel mode +ntr Congratulations, your channel now registered with ChanServ. Repeat for your alliance private and government channels. Naming Tip: Small alliances starting out rarely need more than three channels, a public one, a private one and one for government. Try to have the names related but not random. #alliance, #alliancemembers and #alliancegovt is ok, #alliance, #random and #otherrandom are not ok. Step 2: Deciding on an operator structure If you have not already done so, memorize this table: Name | Letter | Symbol Founder | q | ~ SuperOp | a | &amp; Operator | o | @ Half-Op | h | % Voice | v | + So now that your channels have been registered, you need to come up with a way to determine who gets what position. Usually this is based on your government structure. Some examples are as follows: Founder – Emperor Super-Op – Regent and Other High-Level Government Officials Operator – Low and Mid-Level Government Officials Half-Ops – Alliance Members Voice – Foreign Diplomats of Treatied Alliances Nothing – Everyone Else Founder – One Triumvir Super-Op Other three Triumvir and Other High-Level Government Officials Operator – Low and Mid-Level Government Officials Half-Ops - Foreign Diplomats of Treatied Alliances Voice – Everyone Else The decision is yours, but make it and stick with it! There is nothing worse than making a plan then not following it half-way through. Also, make sure that you can trust who you give op status to! Step 3: Making your access list. Once you have decided on how your access list is structured, it is time to tell the IRC server that list. To use this, you will use 4 commands (There can only be one channel founder). They are as follows: /msg chanserv sop #mychannel add name /msg chanserv aop #mychannel add name /msg chanserv hop #mychannel add name /msg chanserv vop #mychannel add name For SuperOps, Ops, HalfOps and Voice respectively. Step 4: Miscellaneous Channel Commands. If you want chanserv to only let people on the access list join, run this command: /msg chanserv set #mychannel restricted on If you want chanserv to auto-voice everyone who enters, run this command: /msg chanserv levels #mychannel set autovoice 0 If you want for people on the vop+ list to be able to unban themselves, run this command (Recommended for private channels): /msg chanserv levels #mychannel set unban 30 To unban yourself, run this command: /msg chanserv unban #mychannel NOTE: Do NOT mess with the other levels unless you know what you are doing. If you only want the people who are on the access list under hop,aop or sop to have ops, run this command: /msg chanserv set #mychannel secureops on If you want Chanserv to automatically kick someone who enters the channel, run this command using a banmask: /msg chanserv akick #channel add user!ident@hostmask /msg chanserv akick #channel del user!ident@hostmask If you need help, ask Chanserv with a “/msg chanserv help akick” Note: Banmasks will be covered in the next section If you want Chanserv to automatically lock a mode in place, use this command: /msg chanserv set #channel mlock &lt;+modes-modes&gt; Note: Modes will be covered in the next section Step 5: Channel Modes. Mode Description b Bans the given user from the channel c No ANSI color can be sent to the channel C No CTCP's allowed in the channel G Makes channel G rated. Checks for words listed in the Badword Blocks, and replaces them with the words specified M A registered nickname (+r) is required to talk i Invite required k Sets a key needed to join m Moderated channel. Only +v/o/h users may speak N No nick name changes permitted n No messages from outside channels p Makes channel private R Requires a registered nickname to join S Strips all incoming colors s Makes channel secret t Only chanops can set topic Those are the most modes that a channel can have, taken from http://www.coldfront.net/irc_chat/coldfron...s.html#chanmode Several of these modes are mutually exclusive, including s+p and c+S (You can set one but not the other) When you register a channel, chanserv automatically sets mode +ntr This is locked in place and you can not change it. For public channels, I recommend the following on your mlock: +ntrCGR and either +c or +S if you do not want color. For private channels, I recommend the following on your mlock: +sntr and restricted set to “on” Ban Masks: Banning someone is a last resort. Only ban someone if you do not want them on your channel. (Unfortunately some ban masks are easy to get around, others are hard) The simply way to ban someone is to set the mode on the channel: /mode #channel +b user!ident@hostname (Note: Do not set bans in your mlock, use akick for this) Everyone when they log onto the IRC server is assigned a mask, which is the user!ident@hostname above. Several examples of them are: yetanothername!SiyoNqoba@...comcast.net bros!ads@thecastlehall.com NOTE: It is against the CyberNations forum rules to post a user’s hostname For more discussion on banmasks, go to http://irchelp.org/irchelp/changuide.html#security and scroll down to 3C. Banning Step 6: Getting Help. If you need any help, please do not hesitate to contact either bros (#mushroom) or yetanothername (#irchelp) and ask for help. Thanks for reading; -yetanothername

You should also include a guide on how to set up an alliance forum. A template for others to use, because properly setting up a forum is neither fun, or fast (Or straight-forward)

You did, but I stole it.

They are deleted and you have to resign up.

All I would add is halfops are 40, but I like it otherwise.

Could you at least say why? Hey, bros, you should add in a section about setting up alliance IRC channels. I get a lot of requests for help on that one and it would be nice to point them to a guide.

Was not.... That was yetanotherloser, my bother, who we don't talk about....

I added a subdomain, and what ever I did it never did work. When I submited a support ticket, they told me that the DNS was pointing to the wrong IP (It was one off in the fourth octet) and that even it it was pointing to the right IP it wouldn't work because the file premissions were wrong. And good luck with your surgery.

Because every time I've used cPanel it's been buggy and slow. And not to mention it has screwed up my DNS settings several times. Now both the custom-built control panels that I've used from Dreamhost and Verio have been fast and were built to their *exact* specifications so it was nicely integrated (with their services)

If you had read the OP, you would have read that bros hates IF and actively suggusts people move away from it. And you CSS is screwed up in Opera.

I think you misread what I said. What I said was. STAY THE HELL AWAY FROM ANYTHING THAT HAS cPanel.

Server reset at 20 hours would never work, the game's scripts would get too confused.

I'd say so. I've both IF, IP.Board, phpBB and SMF. I'd rank them in this order: IP.Board > SMF > phpBB > IF And on the note of overselling, I havn't had that problem with Dreamhost. I have a friend who runs a popular IP.Board setup over there and they havn't bothered him at all. (He upgraded to their VPS' recently, so that might be what the problem is.) And note: Please for the love of admin/god stay away from any host that does cPanel.

Yes, you can have up to one account on Standard and one account on TE.

SMF 1.1.5 sucks, you really should upgrade to the beta of 2.0, it rocks! (It's what we did over @ gga-te.yetanotherwebsite.net) Also hi \m/. Bye \m/.

Do you have a channel?

I always thought that \m/ would be a good fit for CN:TE. I'd like to see them back.

o.O Ok then. Pink is all yours.

I'd tend to agree, but this is the wrong thread, try the "Bug reports/Suggustions" one

Hi NRO. What color are you on?

I like your logic. (And apperently my humor doesn't go over the internet well...)