This project does not seem to handle request data directly as such no vulnerable execution paths were found.
include
, or for example
via PHP's auto-loading mechanism.
These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
|||||||||||
2 | ||||||||||||
3 | /* |
|||||||||||
4 | * rmarchiv.tk |
|||||||||||
5 | * (c) 2016-2017 by Marcel 'ryg' Hering |
|||||||||||
6 | */ |
|||||||||||
7 | ||||||||||||
8 | namespace App\Console\Commands; |
|||||||||||
9 | ||||||||||||
10 | use App\Models\GamesFile; |
|||||||||||
11 | use App\Models\PlayerIndexjson; |
|||||||||||
12 | use Illuminate\Console\Command; |
|||||||||||
13 | ||||||||||||
14 | class PlayerCreateInfo extends Command |
|||||||||||
15 | { |
|||||||||||
16 | /** |
|||||||||||
17 | * The name and signature of the console command. |
|||||||||||
18 | * |
|||||||||||
19 | * @var string |
|||||||||||
20 | */ |
|||||||||||
21 | protected $signature = 'player:createinfo'; |
|||||||||||
22 | ||||||||||||
23 | /** |
|||||||||||
24 | * The console command description. |
|||||||||||
25 | * |
|||||||||||
26 | * @var string |
|||||||||||
27 | */ |
|||||||||||
28 | protected $description = 'creates index.json data for easyrpg'; |
|||||||||||
29 | ||||||||||||
30 | /** |
|||||||||||
31 | * Create a new command instance. |
|||||||||||
32 | * |
|||||||||||
33 | * @return void |
|||||||||||
0 ignored issues
–
show
|
||||||||||||
34 | */ |
|||||||||||
35 | public function __construct() |
|||||||||||
36 | { |
|||||||||||
37 | parent::__construct(); |
|||||||||||
38 | } |
|||||||||||
39 | ||||||||||||
40 | /** |
|||||||||||
41 | * Execute the console command. |
|||||||||||
42 | * |
|||||||||||
43 | * @return mixed |
|||||||||||
44 | */ |
|||||||||||
45 | public function handle() |
|||||||||||
46 | { |
|||||||||||
47 | $this->info('Lade Gamefiles ohne index.json'); |
|||||||||||
48 | ||||||||||||
49 | $gamefiles = GamesFile::with('game')->get(); |
|||||||||||
50 | ||||||||||||
51 | $counter = 0; |
|||||||||||
0 ignored issues
–
show
Equals sign not aligned with surrounding assignments; expected 3 spaces but found 1 space
This check looks for multiple assignments in successive lines of code. It will report an issue if the operators are not in a straight line. To visualize $a = "a";
$ab = "ab";
$abc = "abc";
will produce issues in the first and second line, while this second example $a = "a";
$ab = "ab";
$abc = "abc";
will produce no issues. ![]() |
||||||||||||
52 | $toindexed = []; |
|||||||||||
53 | ||||||||||||
54 | foreach ($gamefiles as $gamefile) { |
|||||||||||
55 | if ($gamefile->game) { |
|||||||||||
56 | $makerid = $gamefile->game->maker_id; |
|||||||||||
57 | //echo $makerid.' - '.$gamefile->id.PHP_EOL; |
|||||||||||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
50% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
||||||||||||
58 | if ($makerid == 2 or |
|||||||||||
0 ignored issues
–
show
Comprehensibility
Best Practice
introduced
by
Using logical operators such as
or instead of || is generally not recommended.
PHP has two types of connecting operators (logical operators, and boolean operators):
The difference between these is the order in which they are executed. In most cases,
you would want to use a boolean operator like Let’s take a look at a few examples: // Logical operators have lower precedence:
$f = false or true;
// is executed like this:
($f = false) or true;
// Boolean operators have higher precedence:
$f = false || true;
// is executed like this:
$f = (false || true);
Logical Operators are used for Control-FlowOne case where you explicitly want to use logical operators is for control-flow such as this: $x === 5
or die('$x must be 5.');
// Instead of
if ($x !== 5) {
die('$x must be 5.');
}
Since // The following is currently a parse error.
$x === 5
or throw new RuntimeException('$x must be 5.');
These limitations lead to logical operators rarely being of use in current PHP code. ![]() |
||||||||||||
59 | $makerid == 3 or |
|||||||||||
0 ignored issues
–
show
Comprehensibility
Best Practice
introduced
by
Using logical operators such as
or instead of || is generally not recommended.
PHP has two types of connecting operators (logical operators, and boolean operators):
The difference between these is the order in which they are executed. In most cases,
you would want to use a boolean operator like Let’s take a look at a few examples: // Logical operators have lower precedence:
$f = false or true;
// is executed like this:
($f = false) or true;
// Boolean operators have higher precedence:
$f = false || true;
// is executed like this:
$f = (false || true);
Logical Operators are used for Control-FlowOne case where you explicitly want to use logical operators is for control-flow such as this: $x === 5
or die('$x must be 5.');
// Instead of
if ($x !== 5) {
die('$x must be 5.');
}
Since // The following is currently a parse error.
$x === 5
or throw new RuntimeException('$x must be 5.');
These limitations lead to logical operators rarely being of use in current PHP code. ![]() |
||||||||||||
60 | $makerid == 6 or |
|||||||||||
0 ignored issues
–
show
Comprehensibility
Best Practice
introduced
by
Using logical operators such as
or instead of || is generally not recommended.
PHP has two types of connecting operators (logical operators, and boolean operators):
The difference between these is the order in which they are executed. In most cases,
you would want to use a boolean operator like Let’s take a look at a few examples: // Logical operators have lower precedence:
$f = false or true;
// is executed like this:
($f = false) or true;
// Boolean operators have higher precedence:
$f = false || true;
// is executed like this:
$f = (false || true);
Logical Operators are used for Control-FlowOne case where you explicitly want to use logical operators is for control-flow such as this: $x === 5
or die('$x must be 5.');
// Instead of
if ($x !== 5) {
die('$x must be 5.');
}
Since // The following is currently a parse error.
$x === 5
or throw new RuntimeException('$x must be 5.');
These limitations lead to logical operators rarely being of use in current PHP code. ![]() |
||||||||||||
61 | $makerid == 9 or |
|||||||||||
0 ignored issues
–
show
Comprehensibility
Best Practice
introduced
by
Using logical operators such as
or instead of || is generally not recommended.
PHP has two types of connecting operators (logical operators, and boolean operators):
The difference between these is the order in which they are executed. In most cases,
you would want to use a boolean operator like Let’s take a look at a few examples: // Logical operators have lower precedence:
$f = false or true;
// is executed like this:
($f = false) or true;
// Boolean operators have higher precedence:
$f = false || true;
// is executed like this:
$f = (false || true);
Logical Operators are used for Control-FlowOne case where you explicitly want to use logical operators is for control-flow such as this: $x === 5
or die('$x must be 5.');
// Instead of
if ($x !== 5) {
die('$x must be 5.');
}
Since // The following is currently a parse error.
$x === 5
or throw new RuntimeException('$x must be 5.');
These limitations lead to logical operators rarely being of use in current PHP code. ![]() |
||||||||||||
62 | $makerid == 11) { |
|||||||||||
63 | // RPG2k/2k3/MV |
|||||||||||
64 | if ($gamefile->playerIndex()->count() == 0) { |
|||||||||||
65 | $toindexed[] = $gamefile; |
|||||||||||
66 | $this->info('ADD '.$gamefile->game->title); |
|||||||||||
67 | $counter += 1; |
|||||||||||
68 | } |
|||||||||||
69 | } |
|||||||||||
70 | } |
|||||||||||
71 | } |
|||||||||||
72 | ||||||||||||
73 | $this->info('Es wurden '.$counter.' Gamefiles gefunden.'); |
|||||||||||
74 | ||||||||||||
75 | $bar = $this->output->createProgressBar(count($toindexed)); |
|||||||||||
76 | $bar->setFormat(" \033[44;37m %title:-37s% \033[0m\n %current%/%max% %bar% %percent:3s%%\n %remaining:-10s% %memory:37s%"); |
|||||||||||
77 | $bar->setBarCharacter($done = "\033[32m●\033[0m"); |
|||||||||||
0 ignored issues
–
show
Equals sign not aligned with surrounding assignments; expected 10 spaces but found 1 space
This check looks for multiple assignments in successive lines of code. It will report an issue if the operators are not in a straight line. To visualize $a = "a";
$ab = "ab";
$abc = "abc";
will produce issues in the first and second line, while this second example $a = "a";
$ab = "ab";
$abc = "abc";
will produce no issues. ![]() |
||||||||||||
78 | $bar->setEmptyBarCharacter($empty = "\033[31m●\033[0m"); |
|||||||||||
0 ignored issues
–
show
Equals sign not aligned with surrounding assignments; expected 4 spaces but found 1 space
This check looks for multiple assignments in successive lines of code. It will report an issue if the operators are not in a straight line. To visualize $a = "a";
$ab = "ab";
$abc = "abc";
will produce issues in the first and second line, while this second example $a = "a";
$ab = "ab";
$abc = "abc";
will produce no issues. ![]() |
||||||||||||
79 | $bar->setProgressCharacter($progress = "\033[32m➤ \033[0m"); |
|||||||||||
80 | $bar->setMessage('Starte indizierung der Gamefiles', 'title'); |
|||||||||||
81 | $bar->start(); |
|||||||||||
82 | ||||||||||||
83 | $i = 0; |
|||||||||||
0 ignored issues
–
show
$i is not used, you could remove the assignment.
This check looks for variable assignements that are either overwritten by other assignments or where the variable is not used subsequently. $myVar = 'Value';
$higher = false;
if (rand(1, 6) > 3) {
$higher = true;
} else {
$higher = false;
}
Both the ![]() |
||||||||||||
84 | foreach ($toindexed as $toindex) { |
|||||||||||
85 | $bar->setMessage('Entpacken von: '.$toindex->game_id.'/'.$toindex->id, 'title'); |
|||||||||||
86 | \Log::info('Entpacken von '.$toindex->game_id.'/'.$toindex->id); |
|||||||||||
87 | $path = storage_path('app/public/'.$toindex->filename); |
|||||||||||
88 | if ($toindex->extension == 'zip') { |
|||||||||||
89 | $zip = new \ZipArchive(); |
|||||||||||
90 | $zip->open($path); |
|||||||||||
91 | $makerid = $toindex->game->maker_id; |
|||||||||||
92 | if ($makerid == 6) { |
|||||||||||
93 | // RPG Maker MV |
|||||||||||
94 | // Nur Pfad zum "www/" Ordner noetig |
|||||||||||
95 | for ($i = 0; $i < $zip->numFiles; $i++) { |
|||||||||||
96 | $filename = $zip->getNameIndex($i); |
|||||||||||
97 | $this->info('Saved XXX basepath: '.$filename); |
|||||||||||
98 | if (ends_with($filename, 'www/')) { |
|||||||||||
99 | $pl = new PlayerIndexjson(); |
|||||||||||
0 ignored issues
–
show
Equals sign not aligned with surrounding assignments; expected 14 spaces but found 1 space
This check looks for multiple assignments in successive lines of code. It will report an issue if the operators are not in a straight line. To visualize $a = "a";
$ab = "ab";
$abc = "abc";
will produce issues in the first and second line, while this second example $a = "a";
$ab = "ab";
$abc = "abc";
will produce no issues. ![]() |
||||||||||||
100 | $pl->gamefile_id = $toindex->id; |
|||||||||||
101 | $pl->key = 'www'; |
|||||||||||
0 ignored issues
–
show
Equals sign not aligned with surrounding assignments; expected 9 spaces but found 1 space
This check looks for multiple assignments in successive lines of code. It will report an issue if the operators are not in a straight line. To visualize $a = "a";
$ab = "ab";
$abc = "abc";
will produce issues in the first and second line, while this second example $a = "a";
$ab = "ab";
$abc = "abc";
will produce no issues. ![]() |
||||||||||||
102 | $pl->value = $filename; |
|||||||||||
0 ignored issues
–
show
Equals sign not aligned with surrounding assignments; expected 7 spaces but found 1 space
This check looks for multiple assignments in successive lines of code. It will report an issue if the operators are not in a straight line. To visualize $a = "a";
$ab = "ab";
$abc = "abc";
will produce issues in the first and second line, while this second example $a = "a";
$ab = "ab";
$abc = "abc";
will produce no issues. ![]() |
||||||||||||
103 | $pl->filename = $filename; |
|||||||||||
0 ignored issues
–
show
Equals sign not aligned with surrounding assignments; expected 4 spaces but found 1 space
This check looks for multiple assignments in successive lines of code. It will report an issue if the operators are not in a straight line. To visualize $a = "a";
$ab = "ab";
$abc = "abc";
will produce issues in the first and second line, while this second example $a = "a";
$ab = "ab";
$abc = "abc";
will produce no issues. ![]() |
||||||||||||
104 | $pl->save(); |
|||||||||||
105 | ||||||||||||
106 | \Log::info('Saved basepath: '.$filename); |
|||||||||||
107 | break; |
|||||||||||
108 | } |
|||||||||||
109 | } |
|||||||||||
110 | } else { |
|||||||||||
111 | // RPG Maker 2k/2k3 |
|||||||||||
112 | for ($i = 0; $i < $zip->numFiles; $i++) { |
|||||||||||
113 | $filename = $zip->getNameIndex($i); |
|||||||||||
114 | ||||||||||||
115 | if (! ends_with($filename, '/') and ! starts_with($filename, '_MACOSX')) { |
|||||||||||
0 ignored issues
–
show
Comprehensibility
Best Practice
introduced
by
Using logical operators such as
and instead of && is generally not recommended.
PHP has two types of connecting operators (logical operators, and boolean operators):
The difference between these is the order in which they are executed. In most cases,
you would want to use a boolean operator like Let’s take a look at a few examples: // Logical operators have lower precedence:
$f = false or true;
// is executed like this:
($f = false) or true;
// Boolean operators have higher precedence:
$f = false || true;
// is executed like this:
$f = (false || true);
Logical Operators are used for Control-FlowOne case where you explicitly want to use logical operators is for control-flow such as this: $x === 5
or die('$x must be 5.');
// Instead of
if ($x !== 5) {
die('$x must be 5.');
}
Since // The following is currently a parse error.
$x === 5
or throw new RuntimeException('$x must be 5.');
These limitations lead to logical operators rarely being of use in current PHP code. ![]() |
||||||||||||
116 | $imp = $this->search_for_base_path($filename); |
|||||||||||
117 | ||||||||||||
118 | if (! $imp == '') { |
|||||||||||
119 | $pl = new PlayerIndexjson(); |
|||||||||||
0 ignored issues
–
show
Equals sign not aligned with surrounding assignments; expected 14 spaces but found 1 space
This check looks for multiple assignments in successive lines of code. It will report an issue if the operators are not in a straight line. To visualize $a = "a";
$ab = "ab";
$abc = "abc";
will produce issues in the first and second line, while this second example $a = "a";
$ab = "ab";
$abc = "abc";
will produce no issues. ![]() |
||||||||||||
120 | $pl->gamefile_id = $toindex->id; |
|||||||||||
121 | View Code Duplication | if (! ends_with(strtolower($imp), ['.exe', '.lmu', '.ldb', 'ini', '.dll', 'lmt', 'lsd'])) { |
||||||||||
0 ignored issues
–
show
This code seems to be duplicated across your project.
Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation. You can also find more detailed suggestions in the “Code” section of your repository. ![]() |
||||||||||||
122 | $pl->key = preg_replace('/(\.\w+$)/', '', strtolower($imp)); |
|||||||||||
123 | } else { |
|||||||||||
124 | $pl->key = strtolower($imp); |
|||||||||||
125 | } |
|||||||||||
126 | $pl->value = $imp; |
|||||||||||
0 ignored issues
–
show
Equals sign not aligned with surrounding assignments; expected 4 spaces but found 1 space
This check looks for multiple assignments in successive lines of code. It will report an issue if the operators are not in a straight line. To visualize $a = "a";
$ab = "ab";
$abc = "abc";
will produce issues in the first and second line, while this second example $a = "a";
$ab = "ab";
$abc = "abc";
will produce no issues. ![]() |
||||||||||||
127 | $pl->filename = 'www'; |
|||||||||||
128 | $pl->save(); |
|||||||||||
129 | ||||||||||||
130 | \Log::info('Saved basepath: '.$filename); |
|||||||||||
131 | } else { |
|||||||||||
132 | \Log::info('Empty basepath: '.$filename); |
|||||||||||
133 | } |
|||||||||||
134 | } |
|||||||||||
135 | } |
|||||||||||
136 | } |
|||||||||||
137 | @$zip->close(); |
|||||||||||
0 ignored issues
–
show
It seems like you do not handle an error condition here. This can introduce security issues, and is generally not recommended.
If you suppress an error, we recommend checking for the error condition explicitly: // For example instead of
@mkdir($dir);
// Better use
if (@mkdir($dir) === false) {
throw new \RuntimeException('The directory '.$dir.' could not be created.');
}
![]() |
||||||||||||
138 | } else { |
|||||||||||
139 | continue; |
|||||||||||
140 | } |
|||||||||||
141 | ||||||||||||
142 | //return; |
|||||||||||
143 | $bar->advance(); |
|||||||||||
144 | } |
|||||||||||
145 | ||||||||||||
146 | $bar->finish(); |
|||||||||||
147 | ||||||||||||
148 | $this->info('Fertig.'); |
|||||||||||
149 | } |
|||||||||||
150 | ||||||||||||
151 | View Code Duplication | public function search_for_base_path($filepath) |
||||||||||
0 ignored issues
–
show
The return type could not be reliably inferred; please add a
@return annotation.
Our type inference engine in quite powerful, but sometimes the code does not
provide enough clues to go by. In these cases we request you to add a ![]() This method seems to be duplicated in your project.
Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation. You can also find more detailed suggestions in the “Code” section of your repository. ![]() |
||||||||||||
152 | { |
|||||||||||
153 | $dirarray = [ |
|||||||||||
154 | 'backdrop', |
|||||||||||
155 | 'battle', |
|||||||||||
156 | 'battle2', |
|||||||||||
157 | 'battlecharset', |
|||||||||||
158 | 'battleweapon', |
|||||||||||
159 | 'charset', |
|||||||||||
160 | 'chipset', |
|||||||||||
161 | 'faceset', |
|||||||||||
162 | 'frame', |
|||||||||||
163 | 'gameover', |
|||||||||||
164 | 'monster', |
|||||||||||
165 | 'panorama', |
|||||||||||
166 | 'picture', |
|||||||||||
167 | 'system', |
|||||||||||
168 | 'system2', |
|||||||||||
169 | 'title', |
|||||||||||
170 | 'music', |
|||||||||||
171 | 'sound', |
|||||||||||
172 | ]; |
|||||||||||
173 | ||||||||||||
174 | $rootarray = [ |
|||||||||||
175 | 'harmony.dll', |
|||||||||||
176 | 'rpg_rt.exe', |
|||||||||||
177 | 'rpg_rt.ini', |
|||||||||||
178 | 'rpg_rt.ldb', |
|||||||||||
179 | 'rpg_rt.lmt', |
|||||||||||
180 | 'rpg_rt.dat', |
|||||||||||
181 | ]; |
|||||||||||
182 | ||||||||||||
183 | $mapparray = []; |
|||||||||||
184 | for ($i = 0; $i < 2000; $i++) { |
|||||||||||
185 | $mapparray[] = 'map'.sprintf('%04d', $i).'.lmu'; |
|||||||||||
186 | } |
|||||||||||
187 | ||||||||||||
188 | $filearray = array_merge($rootarray, $mapparray); |
|||||||||||
189 | ||||||||||||
190 | $searcharray = array_merge($dirarray, $filearray); |
|||||||||||
191 | ||||||||||||
192 | if (starts_with(strtolower($filepath), $searcharray)) { |
|||||||||||
193 | $imp = str_replace('/', '\\/', $filepath); |
|||||||||||
194 | } else { |
|||||||||||
195 | if (str_contains(strtolower($filepath), $searcharray)) { |
|||||||||||
196 | $exp = explode('/', $filepath); |
|||||||||||
197 | $res = array_shift($exp); |
|||||||||||
0 ignored issues
–
show
$res is not used, you could remove the assignment.
This check looks for variable assignements that are either overwritten by other assignments or where the variable is not used subsequently. $myVar = 'Value';
$higher = false;
if (rand(1, 6) > 3) {
$higher = true;
} else {
$higher = false;
}
Both the ![]() |
||||||||||||
198 | $imp = implode('/', $exp); |
|||||||||||
199 | $imp = $this->search_for_base_path($imp); |
|||||||||||
200 | } else { |
|||||||||||
201 | $imp = ''; |
|||||||||||
202 | } |
|||||||||||
203 | } |
|||||||||||
204 | ||||||||||||
205 | if ($imp != '') { |
|||||||||||
206 | if (array_search(strtolower($imp), $filearray)) { |
|||||||||||
207 | $imp = '.\\/'.$imp; |
|||||||||||
208 | } |
|||||||||||
209 | } |
|||||||||||
210 | ||||||||||||
211 | return $imp; |
|||||||||||
212 | } |
|||||||||||
213 | } |
|||||||||||
214 |
Adding a
@return
annotation to a constructor is not recommended, since a constructor does not have a meaningful return value.Please refer to the PHP core documentation on constructors.