VVVVVV

mpo/VVVVVV

mirror of https://github.com/TerryCavanagh/VVVVVV.git synced 2024-06-28 23:48:30 +02:00

History

Misa 53d725f78a Fix regression: Overzealous emitter dupe fix Commit `4f881b9e26` fixed a duplication bug where enemy movement types 10 and 12 would keep duplicating itself on every frame if it was spawned outside of the rooms they were supposed to be used in the main game. The downside was that this was an overzealous fix and unintentionally broke some cases that were working before. As brought to my attention by Ally, you can no longer place an edentity with a `p1` of 10 or 12 (translating to movement type 10 or 12) in the proper rooms and have it spawn perfectly working entities (that don't clone on themselves every frame), whereas you could in 2.2. This is considered a regression from 2.3. So the problem here is that the reason the two emitter entities were so dangerous outside their respective rooms is because the entity they spawned (`createentity` entry 1) checked if it was in the correct rooms, and if so, it would call `setenemy`, and `setenemy` would set the `behave` attribute (movement type) correctly, and so the new entity would have a different `behave` that wouldn't be the exact same `behave` as the previous one, so it wouldn't be a duplicate emitter entity. The previous `entityclonefix` worked okay for entry 1, because it would only be run if the room checks failed and `setenemy` wasn't called, but it broke a previously-working case for entry 56, because it was always run for entry 56. So the best way to check if we have a dangerous entity is not by seeing if it is still `behave` 10 or 12 at the end of entity creation - because 10 or 12 could be harmless under the right conditions - but by checking if the right conditions were satisfied, and if not, then neutralize the entity. I considered making the emitter entities work everywhere - which would be simpler - but I didn't want to go too far and add a new feature, especially in a minor release.		2024-06-07 14:20:28 -07:00
..
fonts	Add support for GameCube glyphs.	2024-01-18 00:10:20 -05:00
lang	whoops	2024-02-09 13:48:11 +01:00
src	Fix regression: Overzealous emitter dupe fix	2024-06-07 14:20:28 -07:00
VVVVVV-android	Android: Update `README.md` for Maven package	2023-11-14 17:29:34 -08:00
.dockerignore	Run CI on CentOS 7 (#574 )	2021-01-11 00:30:15 -05:00
.gitignore	Optimize recompilation from changing commit hash	2022-08-23 00:00:38 -07:00
CMakeLists.txt	Add MSVC version check	2024-03-29 20:31:00 -07:00
CONTRIBUTORS.txt	CONTRIBUTORS.txt: leo60228 -> leo vriska	2024-05-21 20:57:19 -07:00
Dockerfile	Update to SDL 2.24.0	2022-08-21 16:07:51 -07:00
fixupMac.sh	Remove SDL2_mixer line from fixupMac.sh	2022-03-29 02:27:15 -04:00
icon.ico	Updated .ico	2021-09-03 15:57:16 -04:00
icon.rc	Embedded .ico	2021-08-28 11:21:49 -04:00
README.md	README: Add step for compiling	2024-01-22 00:18:20 -08:00
TRANSLATORS.txt	added Ivan Lopes and Lucas Nunes to credits	2024-02-02 17:37:23 +01:00
version.cmake	Fix %cs showing instead of commit date on Windows (or older git?)	2023-11-13 14:42:48 -08:00

README.md

How to Build

VVVVVV's official desktop versions are built with the following environments:

Windows: Visual Studio 2010
macOS: Xcode CLT, currently targeting 10.9 SDK
GNU/Linux: CentOS 7

The engine depends solely on SDL2 2.24.0+. All other dependencies are statically linked into the engine. The development libraries for Windows can be downloaded from SDL's website, Linux developers can find the dev libraries from their respective repositories, and macOS developers should compile and install from source. (If you're on Ubuntu and your Ubuntu is too old to have this SDL version, then see here for workarounds.)

Since VVVVVV 2.4, git submodules are used for the third party libraries. After cloning, run git submodule update --init to set all of these up. You can also use this command whenever the submodules need to be updated.

Steamworks support is included and the DLL is loaded dynamically, you do not need the SDK headers and there is no special Steam or non-Steam version. The current implementation has been tested with Steamworks SDK v1.46.

To build the Make and Play edition of the game, uncomment #define MAKEANDPLAY in MakeAndPlay.h.

To generate the projects on Windows:

# Put your SDL2 folders somewhere nice!
mkdir build
cd build
cmake -A Win32 -G "Visual Studio 10 2010" .. -DSDL2_INCLUDE_DIRS="C:\SDL2-2.24.0\include" -DSDL2_LIBRARIES="C:\SDL2-2.24.0\lib\x86\SDL2;C:\SDL2-2.24.0\lib\x86\SDL2main"

Then to compile the game, open the solution and click Build.

For more detailed information and troubleshooting, see the Compiling VVVVVV Guide on the Viki.

To generate everywhere else:

mkdir build
cd build
cmake ..

Then to compile the game, type make.

Including data.zip

You'll need the data.zip file from VVVVVV to actually run the game! You can grab it from your copy of the game, or you can just download it for free from the Make and Play page. Put this file next to your executable and the game should run.

This is intended for personal use only - our license doesn't allow you to actually distribute this data.zip file with your own forks without getting permission from us first. See LICENSE.md for more details.