Project "SuperNova.WS" Release 30

[Gorlum]

Disclaimer
==========
WARNING! The project is in alpha stage! Currently, he is not designed for
production-use! Code is provided "as-is". You use at your own risk! The author
is not liable for material, moral, karmic, spiritual, and any other damages
caused you to use, non-, the very existence of this code or any other way.

WARNING! Although heart failure is a clone oGeym, it is not OFFLAYK! Ie many
aspects of the game differ from the official oGeyma as well as from the RR.
Slider changed, that would fit my understanding of an interesting game. Take
With this in mind when deciding - to install this engine yourself or not.

WARNING! Status of "Supernova" - the alpha version. Practically, this means
that the next update can completely change a certain aspect of the game.

Approximate engine development plan contained in the file /docs/changelog.todo

Code licensed under the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
License itself is in the file docs/license.txt distribution.


Advance notice of the need for training
=======================================
These instructions assume the ability to customize and use third-party Web
hosting, familiarity with MySQL and PHP, access to the tools MySQL
administration and hosting. If you do not have the experience of independent
set of sites - this distribution you will not want

WARNING! I can not test all possible combinations and versions of MySQL & PHP &
XCache & Web Servers! This means that for some combinations and environment
settings engine can not work. It is this requires skills setting up and
configuring web servers.


Requirements
==========
MySQL 5.x - STRICT_TRANS_TABLES mode must be disabled
PHP> = 5.2.h
Web-server
XCache> = 1.2.h - optional, but very, very desirable. Without XCache not
will work some chips and increase significantly the load
to MySQL.

The engine is being developed under Windows + Apache Friends XAMPP Lite (Basis
Package) version 1.7.3 (included only Apache + PHP + XCache and MySQL).
Production is spinning under CentOS + lighttpd + XCache. On localhost engine
always operates in the mode display_errors = 1


Location Engine
===================
The engine can run from anywhere on the site, including subdirectories. Ie it
may be installed at the following addresses

You must be registered to see links

You must be registered to see links

You must be registered to see links

and so on.


Permissions of the Web server
=========================
In general, the engine can run from the web server with access rights "only to
reading. "However, for the correct operation of individual subsystems account
Web server must be allowed to write in separate files/folders. Below list of
subsystems and associated files/folders
[*] Cache subsystem template - directory /cache. Without these templates every
time will be rendered anew
[*] For the subsystem warning about attempts to hack the web server account
should be allowed to write to the disk file/badqrys.txt. Without this
"Bad" requests will not be saved


Custom modifications
============================
If you use your own skin, template, or localization, does not change
BUILT-IN NOW! Subsequent changes in the repository can overwrite your
add! Make a copy of a skin/template/location under a different name and have
with a copy to have fun. Change the skin/template/default location can be at
configuration page server.


Installation, configuration database
=========================
WARNING! Mode STRICT_TRANS_TABLES (variable sql_mode) must be disabled!

WARNING! All tables are stored in CH InnoDB! By default, MySQL does not
Configured for normal operation with the bases InnoDB! Default settings will suffice MySQL
to work up to 50 users online. If you are planning more
simultaneous players, then you need to configure MySQL to suit your
server.
As an example, cite your MySQL server configuration (2GB memory, server
allocated solely to heart failure and supportive forum)

innodb_additional_mem_pool_size 20971520
innodb_buffer_pool_size 536870912
innodb_flush_log_at_trx_commit 0
innodb_flush_method O_DIRECT
innodb_log_buffer_size 8388608

Especially pay attention to the variable innodb_flush_log_at_trx_commit!

It is also to facilitate disaster recovery, it is recommended to keep each
InnoDB table in a separate file. To do this, add a configuration file
Directive

innodb_file_per_table


Installing, configuring a Web server
==================================
CH is designed for use keshera op-codes xCache. Although the engine can
work without it, this mode is not regular. No keshera op-codes
Some features of the engine will be blocked, as well as increase the load
to MySQL.
Like any kesher op-codes, xCache require special configuration Web server.
How to configure a web server to work with xCache can be found on the Internet
(

You must be registered to see links

) and on the home page xCache (

You must be registered to see links

)


The installation, base
============================
1. Create a database "supernova" UTF-8
2. Create a MySQL user "supernova_user" and give it all right to
base "supernova"
3. Load the database file/docs/supernova.sql
4. Copy the file/docs/config.php.sample the root of the supernova and
rename it to config.php
5. In the file/config.php on line
"Pass" => "MYSQL_PASSWORD",// ??Password to access the MySQL server.
MYSQL_PASSWORD to replace the password database
6. In the file/config.php on line
"Secretword" => "SUPERNOVA",// ??keyword to create Cookies
SUPERNOVA replace any sequence of characters
7. Load distribution of the supernova in the root directory of the Web server
8. Go into the game with admin rights. The default admin account:
Username: 'admin' (without the quotes)
Password: 'admin' (without the quotes)
9. MUST change the administrator password on the page/options.php
10. Set up the game on the page/admin/settings.php
11. Supernova is ready to launch!

WARNING! Scrap with team members (auth_level> 0) do not fall out! It's not a bug, it's
made specifically to enhance the security of the server! For the game, and
Administration need to use different accounts!


Installation, an advanced version
================================
Settings for database access are in the file /config.php
Game Settings are in the table <db_prefix> config. Appointment Settings
intuitive names of variables
Just some game settings are stored in file/includes/constants.php
All changes - at your own risk
WARNING! If you have changed the table prefix ('sn_' by default), then the same
need to change the names of the tables before pouring the file/docs/supernova.sql!

Multiple universes for a single server
------------------------------------
CH supports multiple universes on a single server. Different universes
must have distinct prefixes within the same space of variables
xCache


Short educational program on the GIT
====================================
Create a local copy of the supernova in the current directory (do not forget to
point end!)
git clone git://github.com/supernova-ws/SuperNova.git .
In the current directory will be the latest copy of the supernova from the branch master.
Now you want to copy the contents to the root server. In general,
encouraged to do so once on the server - to avoid problems with
copy (this was already the case). But not all hosting companies are allowed to run
program locally, so you can first make a copy on your local drive.
In fact, have nothing else However, if you do modifications
engine useful to you sleduyushaya team. Roll back all changes made to
Local copy:
git reset -=hard


Upgrading to the latest version
==============================
0. WARNING! UPDATING TO MAKE A BACKUP DATABASE AND FILE ENGINE THAT would be
possible to roll back if the update fails!
1. Log in to the game through an account with administrator privileges
2. WARNING! Before you upgrade a server MUST be stopped. Done this way: under
the Administrator in the left menu appears select "Administrator" - click on
it. In the admin menu, select "Settings," put check "Turn off the game",
press "Save" button at the bottom of the page. Only then can perform the
update - otherwise the result may be far from expected.
3. If you have template caching enabled, you must delete all the files in
directory/cache
4. Now update the files to the engine
4.1. If you put the game out of GIT-repository, the server at the root
directory, run game
git pull
4.2. In any other case - to upload an updated version of the engine
5. Wait for the NEW version of the engine is on the server! An attempt to update
in the process of copying files or downloading them from the repository can GIT
lead to unpredictable results
6. Switch to the browser in which you are logged in as administrator and
select "Browse." Wait for the page - this time
updates the database
7. And finally, after all this is a game you can again turn
(Admin -> Options, uncheck "Turn off the game" and keep
changes).

Upgrade from RR
------------
Automatic upgrade from bases in the development of RR. Partially upgrade done
automatically launch the file update.php

In heart failure with respect to RR changed location banner. Earlier reference was
/Scripts/createbanner.php
New Links
/Banner.php

Use the tools the web server (mod_rewrite) to redirect requests. In
Specifically, the rule for lighttpd is as follows:

# Redirects old-style banners to new one
server.modules + = ("mod_rewrite")
url.rewrite-once = (
"^/Scripts/createbanner.php (.*)" =>"/banner.php $ 1 "
)

If you have problems with updating ...
---------------------------------------
It is impossible to predict all possible combinations of settings, PHP, MySQL and
Web server. CH focuses on the "default settings". Therefore, in some
cases, possible failures in the upgrade procedure. An algorithm for automatic
Pack is designed for a single run. However, in some
configurations during the upgrade, errors occur. Some of them -
critical, and some can fix restarting procedure (with or without
editing database). Run the update again be using
select "Force update" menu "Utilities" page of the Administrator. Please
pay attention! Using the forced update may lead to
damage to the database (if the update itself over the previously successful)!
Forced update should be used only if
standard update procedure was not successful! If it did not help -
should go to Diagnostiek fault

Fault diagnosis engine
=================================
The latest and most current version of the engine (with the most recent and relevant bugs)
can be downloaded at this link:

You must be registered to see links

Click on «Download. Zip» and download archives trunk. At what exactly should go on
link above and click the button there. Go direct link to the download
- Does not work.
To pay attention to the file name is not necessary.
! WARNING! Diagnosis should be performed on a separate database and separate copy
engine! DO NOT LIVE IN diagnosis SERVER!

The standard sequence of steps in the diagnosis of this:
1. Set in an empty database clean dump a database from an archive. Problems in this
stage, say the following:
1. The most likely - an error in setting up the MySQL server
2. Errors in the dump database. Perhaps you are in a time of renewal dump.
"Moment" here relative concept - it can take several days
2. Put on a clean server and a clean database, obtained at the last step, the engine
from the archive. Try to run. Problems at this stage, say the following:
1. Errors in the configuration engine. Check the file/config.php
2. Errors in the HTTP-server settings (especially if the first run
engine)
3 Errors in avtoapdeytere
4. The engine is in the process of writing, but you got to "moment" commit
3. Replace the clean database dump of your working database (do not forget if you want to AGAIN
change the configuration - prefix tables there, logins/passwords, etc.).
Problems at this stage, say the following:
1. Errors in the configuration engine. Check the file/config.php
2. Errors in avtoapdeytere
3. Errors in the database itself. Then a deal themselves, or pay for my work
4. If there are no problems - then something is not specifically as a live server. Here we have
have to understand more - either by themselves or pay for my work

Before each stage ALWAYS need to restart the web server and MySQL - otherwise
can be used by the old settings from the previous version.
Only a true and accurate diagnostic procedure to follow will help to effectively
identify problems in the SN on each individual server.

References
======
The main project site:

You must be registered to see links

Forums
------
Forum Project:

You must be registered to see links

Support Forum:

You must be registered to see links

Forum for bug reports:

You must be registered to see links

Supernova on github
--------------------
Project page:

You must be registered to see links

Download Engine:

You must be registered to see links

Repository: git://github.com/supernova-ws/SuperNova.git

Supernova on sourceforge
--------------------
Project page:

You must be registered to see links

Download Engine:

You must be registered to see links

Repository: git://supernova-ws.git.sourceforge.net/gitroot/supernova-ws/supernova-ws


Donations
==============
You can help by sending a WebMoney to purse:
WMZ (WM-USD) Z409323360409
WMR (WM-RUB) R961266352219
WMU (WM-UAH) U726314912308

If you use WebMoney to buy various electronic products, you
can a) buy the usual electronic goods at a good price b) help the project.

You must be registered to see links

- recharge cell, Skype, WoW - the game and the TC and other
electrical goods for WM. Each purchase made from this link will bring
I a small commission.

Remember! Nothing strengthens the belief in the usefulness to work as a donation!


Updated: 2011-06-03 22:38 V28.1a10

 

[agua]

The Nova project is very old, they released a few very functional and playable versions in the last few years, you can say is a new core bla bla bla but what the people is looking for or want is a functional and playable script with minimal bugs. Alpha release now years later makes no sense is roll back to stone age.

 

[Gorlum]

Did I understand your point of view right - after Tetris was made there is no place for other games? After xNova was made - there is no place for other engines?

I'm absolutly sure - you didn't even looked at SN engine. And I'm absolutly sure you didn't look at source code of xNova itself. Does players wants numerous SQL-injections? Does players wants numerous XSS vulnerability? Does players wants constant bugs with loosing resources/fleets due to poor transaction-unsafe interaction between php and mysql parts of xNova? Does players wants poor fleet-manager engine? Sure! Use xNova original engine!

You didn't even look - and you already didn't like it. It's tells nothing about SN. It's tell about you.

 

[agua]

Did I understand your point of view right - after Tetris was made there is no place for other games? After xNova was made - there is no place for other engines?

I'm absolutly sure - you didn't even looked at SN engine. And I'm absolutly sure you didn't look at source code of xNova itself. Does players wants numerous SQL-injections? Does players wants numerous XSS vulnerability? Does players wants constant bugs with loosing resources/fleets due to poor transaction-unsafe interaction between php and mysql parts of xNova? Does players wants poor fleet-manager engine? Sure! Use xNova original engine!

You didn't even look - and you already didn't like it. It's tells nothing about SN. It's tell about you.

Ogame is a very old fart game, a game really like and I been involved like member of a cancelled Russian develop project and i left for a busy life, besides is going down in players population and why work in new alpha if the basic game never was cleared from bugs and 100% functional or finished, still a lot to do in the main core script xnova and others.
release a buggerless script and the people will love you.

 

[agua]

Yes probably some bugs are corrected like you said in your lat post but English is the main forum language.

 

[Gorlum]

Ok. So there is a content of previous post with some adaptation.
"Just read changelog (if you understand Russian). You even didn't bother to read this file! Otherwise you'll see how many bugs was fixed"
Now some addition.

"Disclaimer" is almost equivalent to MS Windows "Disclaimer". It's only a little insurance that no one can fill any kind of claim to me nor moral, nor financial. Do all windows-users read MS license agreement from start to end? No. Does it stop most part of readed from using windows? No. Does it this agreement protects MS from claims? Yes. So - you should think about this disclaimer in same manner. Shortly it can be formulated like "USE ON YOUR ON RISK! NO EXPLIED AND IMPLED WARRANTY ON THIS ENGINE!" No less, but no more too.

"Alpha Stage" of my project only means that I refuse to accept claims like "YOU CHANGE GAME MECHANIC!!!". Quality of my release at least "release candidate". They tested on live servers with small but active community. Almost all found bugs are fixed in day or two. My engine works on about 10+ official servers (those, who didn't change copyright notice) and about 20+ unofficial (yes, I can use Google and find my servers with it)

My engine is almost flawless - compared to other xNova engines. Latest xNova release have SLQi resistance close to none. Just glancing through code of xnova-lagacies_2009.3 I found several potints for SQLi - then I stopped looking. Same thing for xNova redesigned (however may be I have outdated version).

Moreover - SN really can't be count as xNova engine. Only like "xNova-based" - with all respect to original xNova creators and contributers. About 80% of PHP code are rewrited. Almost all HTML code stripped from PHP files to templates. phpBB3 template engine added, granted very high level of template customization and caching.

On first glance there are some "issues" on my engine. I should declare - almost all of them is not a bug. It's a feature. I didn't want to duplicate oGame (but I use some mechanic from it when I find it appropriate). I didn't want just to fix xNova. I want to create my own "right game" - how I see it. This is what all disclaimer about. Not about code quality. Not about stability. Only about that I will change game mechanic as I see fit until BETA stage. My releases are pretty stable. Yes, sometimes it happens that problem arise. But noone is perfect. I make this engine in my spare time - with almost none payment at all. I run my live universes on server-grade system bought from my own money. And I was able to negotiate with largest country-wide home-internet provider to put my server on their hosting. There is no profit for me yet. So I see that I have all rights to put my effort on enchancing SN engine as I see it fit to my understanding of "good game".

However I opened for new ideas. Pretty much of current features was proposed by players/server admins. Moreover - I can customize engine for you for a reasonable fee (yes. this is ADVERTISING!!!).

Also I'm searching for native english-speaking user that would like to adjust google-translation of English files to literature English (as you should now see - English is not my native language). This is pretty critical 'cause English would be used as base for translation for other languages.

Currently I'm working about 2 years on SN project (did I mention that I working on project on my spare time supplying it with my personal funds?). I hope to work it to the point when I can honestly name it BETA or even RELEASE (see above about "alpha" stage of project). I'm perfectionist at nature. Almost any "release" of ogame-like engines that I see will be marked as "Alpha" by me - if I was releaser. So you shouldn't fear "Alpha" stage of my project. You should fear others that mark their projects as "release" with numerous bugs and security breaches.

 

[cyberghoser1]

Esthetic Fix for release 30d4, add in language/en/admin.mo

'adm_lm_planet_edit' => 'Edit planet',

Great project, actually looking the code its very good, keep up the good work man!

 

[Gorlum]

Fix will be in next release, thanks

BTW do you like to make a Greece localization?

 

[cyberghoser1]

Fix will be in next release, thanks

BTW do you like to make a Greece localization?

Yeah i do not mind, i will start tonight translating both player/admin section and proivde you my translates

also you should look at your mysql connection in php, in some webservers the queries are made either too slow or too fast thus resulting in getting fatal error like:

FATAL ERROR: coult not write to database "logs" Contact an adminitrator MYSQL has gone away.

This happens only in one of my hosters, not all

 

[Gorlum]

You should look at your InnoDB settings. SN uses InnoDB which didn't configurated well by default.

 

[cyberghoser1]

You should look at your InnoDB settings. SN uses InnoDB which didn't configurated well by default.

Yeah i am aware of that, now for the greek translation i came across some problems, my database i set to utf8_bin as it should for greek but i have to save the .mo files in ANSI because if i do it in utf8 i get weird chars, but in ANSI i get russian, i already altered the language.mo file so far no success but i will find it.

 

[Gorlum]

Darn! You also should change codepage... It's planned to move SN to UTF8 but it was no rush... until now. For now you can look across code and change CP1251 with appropriate codepage. It will do the trick for now. If you like I can quickly made in-depth changes for you now - if you wait for couple of minutes.

 

[cyberghoser1]

Darn! You also should change codepage... It's planned to move SN to UTF8 but it was no rush... until now. For now you can look across code and change CP1251 with appropriate codepage. It will do the trick for now. If you like I can quickly made in-depth changes for you now - if you wait for couple of minutes.

Yeah that would help a lot thanks

 

[Gorlum]

Ouuu-kay... Made some modifications in a rush. Trunk on GitHub contains LANGUAGE.MO-dependent localization. You can try it now. Report any error you encounter

 

[cyberghoser1]

Ok i will right away

 

[Gorlum]

Ah, small mistake made in a rush. If you encounter error "Unknown charset" just pull new revision from GIT.

---------- Post added at 12:36 AM ---------- Previous post was at 12:16 AM ----------

hello, are you sure its located at GIT ? because there i see versions V29 etc not 30d4 like in google.

In Google I didn't put my code in Google... LOL!
Yep, I'm pretty sure. GitHub names downloadable files with last tag entered. For my project current last GitHub tag is V29.
As you can clearly see by this link

You must be registered to see links

it's a couple minutes ago last commit was made. If you wish to download full version use this link

You must be registered to see links

- it will download freshest copy of SN regard of name

---------- Post added at 12:43 AM ---------- Previous post was at 12:36 AM ----------

BTW can you please link me SN in Google - just for cause?

 

[cyberghoser1]

Yeah in meantime i already downloaded it from git,i will tell you about translation very soon.

 

[Gorlum]

Please confirm ASAP that you able to start translation - i.e. your pages in Greek renders correct in browser. I'd like that SN was translated to as many languages as possible - so I want to be sure no free time of my preciouss contributers was lost due to inability to start translation. So I'd like to be sure that nothing can stop you from translation. From other side - SN is my "home project" and I need go tomorrow... ups... already "today" to work for a money

 

[cyberghoser1]

I will ASAP i am re-installing from the begining in appserv to have a fresh copy.

 

[Gorlum]

To make SN recognize your translation you should perform those steps:
1. Copy desired translation folder (for ex. "en") in /language under different name (I presume it would be "gr")
2. Edit /language/gr/language.mo file. Change LANG_NAME_ISO2 to 'gr' - it's essential to made localization work.
3. Change LANG_ENCODING to your codepage. It should be compatible with mysql codepage list. I presume in your case it should be "greek"
4. Change LANG_NAME_NATIVE to your language name ('greek' in Greek
5. Change LANG_NAME_ENGLISH to 'Greek"
6. Switch your language in user settings to Greek
7. Optionally change server default language to Greek too
8. Now you ready to start localization - if I didn't make any serious mistake in a rush

Your current DB output may be a bit gibberish due to rush nature of localization. So any info on Greek that stores in DB may look... erm... awfull. Ignore it for a while - I will make SN full UTF-8 compatible. You can start localization right now - I will painlesly convert your ANSI-Greek files to UTF-8 lately.