Clasificare (dupa modul de farmare): farmezi, nu farmezi

Farmezi - Esti un jucator care castiga resurse din farmat.

Intai de toate nu cred ca esti incepator . Cauta-ti colaboratori, prin vecini, pe care sa te bazezi cand vei avea nevoie sa faci defensiva (pentru ca nu cred ca vei juca doar defensiv). Resursele ti le cresti (prioritar lanurile de grau, ca vei fura putin) in paralel cu infrastructura pe care o consideri necesara (cazarma, academie, grajd, resedinta erou, vila, atelier etc).

Nu farmezi – nu farmezi nimic din unul din motivele precizate, in articolul Inceputul, sau esti un jucator pasnic care se dezvolta prin forte proprii. Incearca sa ridici prioritar campurile de resurse (nu neglija hrana!) din infrastructura ridica hambar, granar, targ si primarie treptat si sa nu investesti in trupe, la inceput. De asemenea incearca sa iti construiesti vila si sa pregatesti extinderea. Pentru a evita macelul trupelor tale trimite-le intariri la un jucator, cu care vorbesti in prealabil, si le ti acolo pana strangi suficiente sa te aperi singur sau cu ajutorul unui jucator sau doi, aliati.

Alta  clasificare, dupa tipul de joc: defensiv, ofensiv, ofensiv si defensiv

Ofensiv: te bazezi pe armata ofensiva si mai mult pe defensiva de la altii decat a ta (daca iti faci). Trebuie sa ai oameni de incredere care sa te ajute cu defensiva. Vei avea nevoie de o capitala pe un croper (15 lanuri de grau) si bonus ofensiv minim 75%, sau semicroper (9 lanuri de grau) cu bonus minim 100%. Eroul ti-l upgradezi pentru bonus ofensiv, prioritar, si pentru refacere viata (cateva puncte).

Defensiv: armata defensiva este prioritara. Capitala o poti face pe un croper sau semicroper care poate avea si bonus de hrana 25%. Eroul (il faci dintr-o unitate defensiva) ti-l upgradezi pentru bonus defensiv, prioritar, si eventual pentru refacere viata (cateva puncte). Trimiti eroul intariri peste tot pe unde trimiti si trupele intariri pentru un atac – DACA TI SE TRIMITE ACASA DOAR EROUL, fara a fi intrebat in prealabil, ITI RETRAGI TRUPELE.

Ofensiv si defensiv: ceva intre cele 2 tipuri – ofensiv si defensiv.

A treia clasificare pe care o voi prezenta aici este cea dupa modul de utilizare a facilitatii gold: gold, non-gold

Gold: folosesti aurul. Prioritar activeaza bonusul pentru resurse, iar plusul, bonusurile pentru defensiva/ofensiva, constructie instant, npc (redistribuire resurse) dupa preferinte si necesitati.

Non-gold: ridica resursele prioritar. Cand esti ai productie 200-300 pe sat poti incepe sa faci in paralel trupe (trebuie sa mentii o productie de hrana rezonabila – incat sa nu te tina pe loc lipsa de hrana).

Modul in care incepi un server este destul de important pentru modul in care te dezvolti pe viitor.

Intai de toate trebuie sa iti alegi unul din cele 3 triburi: daci, romani, barbari – fiecare avand avantaje si dezavantaje. Barbarii au cel mai mare avantaj (parerea mea) cel putin pe inceput de server si nu numai (as zice).
Indiferent de tribul cu care joci este foarte important sa observi ce vecini ai:

• daca ai barbari activi pe langa tine care farmeaza masiv, iar tu esti in “zona” lor de influenta, ai urmatoarele optiuni: colaborezi cu ei sa te lase in pace sau “scapi” de ei. In acest caz, in special pentru daci si romani, dar si pentru tine ca barbar (mai putin activ decat cel cu care te “bati pe teritoriu”), va fi greu sa farmezi ceva (sa furi resurse de la ati jucatori). Barbarii au avantajul de a fura pana la 30% din beciuri – tu ca roman sau dac va trebui sa farmezi inaintea barbarului daca vrei sa “prinzi” ceva (poti fura doar ce nu este ascuns in beci);

• fiind un jucator activ (nu conteaza tribul) care farmeaza si ai vecini pe care ii ataci si nu le furi resurse niciodata (sau iei putine resurse putine ocazional) ar fi bine sa ii apropii de tine prin aducerea lor in alianta sau printr-o intelegere directa, in special daca acei jucatori sunt daci sau romani pentru ca pe viitor te vor putea ajuta cu defensiva.

• daca se fura resurse de la tine fa-ti beciuri si cauta sitteri (loctiitori, poti avea maxim 2) de incredere printre vecinii aliati, cu care sa te ajuti reciproc, astfel incat sa nu se mai fure resurse de la tine. Dupa ce demonstrezi celui care incearca sa te farmeze ca nu va putea lua nimic de la tine discuta cu acel jucator (daca ai si tu de castigat) sa colaborati pentru a te putea si tu dezvolta. Beciuri construieste maxim 2-3 (mai multe deja inseamna investitie inutila prea mare). Daca esti dac si ai temnita nu reface celulele decat daca ai suficiente trupe defensive si cel care te ataca are relativ putine trupe ofensive – ori i le prinzi pe toate in celule ori va veni dupa ele cam cu tot ce are si atunci trebuie sa nu i se mai intoarca acasa nimic din ce te ataca sau foarte putine – altfel investesti degeaba resurse in aceasta cladire.

zuzulica World Wonder s5.travian.ro

pragma autonomous transaction;

begin
  insert into myTable
    (test_value)
  values
    ('what I want to insert');
  commit;
exception
  when others then
    rollback;
end;

A block like this can be nested in other blocks that require a complex transaction control.

I recommend you to read Autonomous Transactions: a Poor Mis-Understood Feature for an advanced discusion on this topic.

DML transaction start at the first SQL command that follows commit or rollback and end on the next commit or rollback.

To mark an intermediate point in the transaction you have to use savepoint.

Syntax:

commit [trans];
savepoint savepoint_name;
rollback [trans];
rollback [trans] to [savepoint] savepoint_name;

Observations:
- trans is for compliance with ANSI standards
- keys between [ ] are optional

For this problem is a very simple solution: I use page-break, a css (cascade style sheet) property.

This property should be applied on a html object.

The page-break property sets the page-breaking behaviour before (in this case I use page-break-before property) or after (in this case I use page-break-after property) an html object.

In next table I will present posible values for the page-break-before and page-break-after properties:

Examples:

1. I want to break page, if necessary, before any table in page – I use property on a css file that I “include” in my web page:

table {
page-break-before: auto
}

2. I want to break, each time, page after a specific paragraph in page (I use for this page-break-after property inline, in web page):

<html>
...
<p style="page-break-after: always">
Text that I want to display in this paragraph.
</p>
...
<html>

everyday programming tip

A sequence is an Oracle object used to generate a number sequence and has next syntax:

create sequence sequence_name
   minvalue value
   maxvalue value
   start with
   increment by value
   cache value;

The sequence parameters are:
minvalue –> minimum (and start) value generated
maxvalue –> maximum (and start) value generated. The maxvalue option has a default value (999999999999999999999999999) so you may omit it when you create a sequence.
start with –> start value generated
increment by –> incrementation step used to generate numbers
cache –> specifies how many sequence values will be stored in memory for faster acces. An alternative is to use the nocache option –> practice recommend it because if system crashes and you have a sequence with cache option you will loose values stored in memory – they will appear as “used” even they aren’t.

For example I have table users with fields user_id, first_name, last_name and I use next sequence to populate field id:

create sequence users_seq
   minvalue 1
   start with 1
   increment by 1
   nocache;

When I will insert values in may table I will use next syntax:

insert into users
   (user_id, first_name, last_name)
values
   (users_seq.nextval, first_name, last_name);

Most of the languages have a block structure approach. This means that each control construct, conditional or repetitive such as IF and WHILE and not only, has its own terminator keyword (END IF, END WHILE etc.), after case. So each logical block of code has an explicit beginning and an associated ending statement (the way beginning and ending are reperesented depends on the programming language).

My recommendation is to follow the next generic rules:
- use indentation. Indent with 2-3 blank spaces (not tab).

if <condition> then
   instruction 1;
   instruction 2;
   .
   .
   instruction n;
else
   instruction 1;
   instruction 2;
   .
   .
   instruction n;
end if;

- block separation. Include a blank line before each block/section.

if <condition> then
   instructions;
end if;

while <condition>
   instructions;
loop;

- comments. Don’t ignore comments because they are very important. They might help you (if you review the code later) or somebody else to understand what you have done there. At least comment what your function, section, block does.
- appropriate names. Choose appropriate names for your programs, functions, variables etc. For example a function name like “averageIncome” tells me more than “asdf”. When you compose a name from more words use upper letter for the beginning of each word (except the first one) – example: myVariable, newClientOrder. Usually a good name can replace a comment.
- write using lowercase. From my point of view it’s easier to read and write lowecase codes.
SQL sample:

SELECT *
FROM MYTABLE
WHERE FIELD=1

lowercase version:

select *
from myTable
where field = 1


- use naming convention. I use prefixes for identificators: “v_” (variables), “c_” (constants), etc.

My advice is not to copy a “coding style” but to understand how to write a code and create your own style that suits you better and inherits a code style or more if you have to follow some standards (sometimes this is required). Try to create a code style that does not depend on programming language.

Well a web page is a text file which contains valid HTML (Hyper Text MarkUp Language) code. Usually file has html or htm extension (simple and static pages), but there are cases when a web page (html code) is generated using a server scripting language such as PHP, ASP etc (these are dynamic pages and require advanced knowledge and usually are used together with a database server like MySql, Oracle, DB2 etc.).