67d9a42506
refactor: a lot of Automation foreach loops updated
...
#313
2017-11-19 14:01:30 +01:00
fd14002d98
fix: oasis beasts do not die
2017-11-19 02:52:33 +01:00
07e5f322e2
fix: reinforcements sent back do not hide the reinforcements table
2017-11-19 02:33:07 +01:00
778f42b4f1
refactor: cycle optimizations and cache fixes
...
This one specifically fixes rescured prisoners not being sent back.
Other than this fix, there are some query optimizations included.
#313
2017-11-19 01:37:31 +01:00
4172e30dd2
fix: Gaul traps do not work
2017-11-18 21:58:54 +01:00
fffedc4170
fix: defender troops do not die during attack
2017-11-18 13:11:00 +01:00
dd030859cf
fix: troops did not return to the village when evasion was set
2017-11-18 11:10:58 +01:00
2041ad750e
fix: hero movements got screwed up while doing DB caching stuff...
...
#313
2017-11-17 23:46:01 +01:00
bfc7a2b28a
fix: keeping compatibility with older versions
...
#353
2017-11-17 23:18:40 +01:00
8f979deba9
fix: wrong user ID being selected via getNotice2() & getNotice3()
...
#313
2017-11-17 23:15:12 +01:00
ffeeac3173
fix: database connection does not include port from config
...
#353
2017-11-17 22:48:43 +01:00
fd20e12d34
fix: $values, not $value
...
#313
2017-11-17 22:26:06 +01:00
6d0e95670b
refactor: messages and reports only loaded on pages where needed
...
#313
2017-11-17 21:00:00 +01:00
db87ce88a7
refactor: getUnit() can take multiple IDs at once
...
#313
2017-11-17 20:23:01 +01:00
d17d1f9b32
refactor: last round of database values caching
...
#313
2017-11-17 19:40:34 +01:00
1318f34cba
refactor: Units class-related caching done
...
#313
2017-11-17 15:34:08 +01:00
079c830b94
refactor: Technology class-related caching done
...
#313
2017-11-17 14:36:49 +01:00
51f354542d
fix: village resources display outdated information on page load
2017-11-17 12:36:27 +01:00
d0a882f136
fix: maxcrop & maxstore cannot be 0, nor it should be < lowest threshold
2017-11-16 21:49:22 +01:00
d3ec209ad8
refactor: village-related methods now all optimized
2017-11-15 23:33:07 +01:00
612661c9f0
refactor: units DB values caching
2017-11-15 23:20:14 +01:00
a8b8664e07
fix: Automation::updateStore() shouldn't be called twice
2017-11-15 22:00:18 +01:00
dab768f662
refactor: 1st round of database values caching
2017-11-15 16:01:00 +01:00
e798635ebb
fix: setVillageLevel() tried to execute wrong SQL
...
+ some more methods for later refactor commit
2017-11-13 17:01:36 +01:00
3d44226c92
refactor: more caching where possible
...
This also fixes "Multihunter" being stated as the one attacking
reinforcements in villages during battle (now stores real attacker ID).
2017-11-12 10:36:53 +01:00
603d28f31a
fix: MySQL 5.7 compatibility + undefined variables
2017-11-10 14:07:32 +01:00
dc22a45c8a
fix: time not selected in general stats, making casualties 0 per day
2017-11-09 23:54:55 +01:00
29d638b7f7
refactor: 4th round of sendunitsComplete() optimizations + market fix
...
Sending units more than 1x (with PLUS) didn't work after the first
market refactor.
2017-11-09 21:38:30 +01:00
2ba0500433
fix: this cannot be in production
2017-11-09 14:24:01 +01:00
371c717702
refactor: 3rd round of sendunitsComplete() optimizations
2017-11-09 14:22:15 +01:00
b1b1581f4c
refactor: 2nd round of sendunitsComplete() optimizations
2017-11-09 00:43:10 +01:00
0a541d5bd3
fix: reverting possibility of settlers & chieftain creation side-by-side
...
Turns out we could conquer a village and then settle a new one without
having enough expansion slots. Thus this is a revert to original state,
where we can't train settlers with chieftain in village or chieftain
with settlers in village, if we don't have enough slots.
Closes #324
2017-11-09 00:08:40 +01:00
50f0cae495
refactor: 1st round of sendunitsComplete() optimizations
2017-11-08 23:43:28 +01:00
151553735d
refactor: setMovementProc() to take one or multiple IDs for update
2017-11-08 18:21:30 +01:00
21d6874325
refactor: marketComplete() to use less queries and caching
2017-11-08 18:12:54 +01:00
159de207c9
refactor: get and set multiple fields at once
2017-11-08 17:46:18 +01:00
c638c67624
refactor: preparation to take batches of data in prepared statements
2017-11-08 13:49:58 +01:00
59c7fdd3c0
refactor: Nature no longer sends automated notification, Taskmaster does
2017-11-08 11:02:15 +01:00
312507fe9f
feat: MySQL port into installation options
...
Closes #279
2017-11-07 12:30:32 +01:00
9db31ff311
fix: wrong forum link field
2017-11-05 16:03:51 +01:00
ee017adb40
refactor: most of broad SELECTs updated
...
Closes #301
2017-11-05 14:35:19 +01:00
f485f69e0a
fix: clear all remaining village troops when conquering a village
...
Closes #269
2017-11-05 00:08:22 +01:00
a822504706
fix: counting queries optimization
...
Closes #300
2017-11-04 15:41:35 +01:00
36bfb2b8f7
fix: alliance deletion check
2017-11-04 10:32:30 +01:00
3f612d6e36
fix: alliance cannot be created
...
This only happens on newer MySQL versions where column type vs inserted
type are being checked (so we cannot insert empty string into an int
column, even if that column has a default value).
Fixes #249
2017-11-04 09:26:45 +01:00
fea7b0937f
fix: could not train more settlers if we have 1 settler already trained
2017-11-03 22:04:15 +01:00
23eed5da53
fix: unable to train settlers if chieftan is present
...
It is debatable whether or not to allow this, since chieftan would be of
no use once we have 3 settlers and settle a new village. However, if we
accidentally created a chieftan, we can't train settlers until we send
the chieftan to his death.
I think this move could be a predule to a later game mechanics, where
chieftan could fight (talk, actually) against chieftan, if one is
present in village, so taking a village over isn't so easy.
2017-11-03 17:23:29 +01:00
bfaf97f998
fix: AND instead of second WHERE
2017-11-03 00:01:20 +01:00
90f8982245
fix: hero dying and revival doesn't work correctly with multiple heroes
2017-11-02 23:59:03 +01:00
585edfc356
fix: this error report should not be here
2017-11-02 13:27:38 +01:00
Martin Ambrus